API Error while trying to fetch data through Alteryx

[Athul Abraham]

I have tried to extract the Global Shares JIRA data for Support Desk Project, But it is failing with below error message
"Error: connect ETIMEDOUT 13.227.213.4:443" 
I have used the endpoint url as "https://globalshares.atlassian.net/" and used the API token for Authentication, but it fails due to the above timedout error. Can you please help to fix this issue. I have used alteryx downlod tool in JPMC to fetch this data.

Really appreciate your help

[Tuncay Senturk _Snapbytes_]

Hi @Athul Abraham 

I am not sure if you've already solved the problem.

It seems to be a network related timeout, not a Jira specific error. The IP 13.227.213.4 is an AWS IP used by Atlassian and your internal network may be blocking outbound access to this Atlassian Cloud server. You can allow outbound https traffic to the globalshares.atlassian.net (you can find Atlassian's full IP ranges here) or you can use a proxy if that's required.

I hope that helps

[Athul Abraham]

Thanks @Tuncay Senturk _Snapbytes_ for the update, We are still encountering the same issue,I believe the issue is occurring due to the internal network blocking to the Atlassian account. Hence can you please provide some suggestion on how to overcome this issue, We are using JPMC network to fetch the Global Shares JIRA. So what would be the best way to handle this? Appreciate your advice on this. Thanks

[Tuncay Senturk _Snapbytes_]

Yes, most possibly the JPMC internal network is blocking access to Atlassian Cloud. I'd suggest raising a request to the network/firewall team to allow outbound access to Jira Cloud. This is the site that you need access

Host: globalshares.atlassian.net
Protocol: HTTPS (port 443)

They will either fix it in the Firewall settings or enforce you to use a proxy.

You can also use a middleware server to be in the middle
JPMC <-> middleware server <-> Atlassian Jira 

but this workaround is difficult to maintain and also you will need to have access from JPMC to this server. So, I strongly recommend fixing this with the security/firewall team.

[Athul Abraham]

Thanks a lot for the support,