Atlassian is not able to send the http request to my remote VM

[NISHANT DESAI]

Hello Community,

While Writing Automation Rule for my project the below error of 403 is showing in Jira

I have tried this API from another machine and it's working fine and I have also whitelisted Atlassian URLs on my remote VM.

Can Anyone Help ?

[Desarrollo Sistemas]

It is a ports restriction from Atlassian squid proxy. The requests sent from Jira Automation only accept this ports: 

80 - 8080 - 443 - 8443 - 8444 - 7990 - 8090 - 8085 - 8060

Source: https://jira.atlassian.com/browse/AUTO-151

[Sunny Ape]

Hello @NISHANT DESAI 

Can you please provide a link to the documentation that describes the use of that Jira Cloud REST API endpoint /api/v1/tickets in your automation rule.

In the rule, where is shows http://***.***.***.*** , can it be assumed you are inserting a raw IP address there? If so, what is the purpose of that instead of using the URL path to your Jira Cloud instance?

[NISHANT DESAI]

Hi  @Sunny Ape ,

Yes I am using raw IP where my project has been hosted.

I need an API call to http://***.***.***.***:port/api/v1/tickets when status is changed

so I am using web request URL but getting above error.

[Sunny Ape]

Hi @NISHANT DESAI 

As per my previous request, where is this REST API endpoint /api/v1/tickets documented? I am not aware of a thing in Jira Cloud called a 'ticket'.

[NISHANT DESAI]

Hi @Sunny Ape ,

Actually /api/v1/tickets this REST API  endpoints are of my spring boot project.

I have to call my spring boot REST API which is /api/v1/tickets whenever status of issue is changed from To Do -> In Progress

/api/v1/tickets is not a part of Jira , this API is part of my spring boot project which i hosted on VM

[Sunny Ape]

Hi @NISHANT DESAI 

It's a shame you didn't mention that critically important bit of information in your question from the start.

Sorry, I don't use Spring, so can't provide any further assistance.

[NISHANT DESAI]

Dear @Sunny Ape ,

With all due respect the real problem here is  Atlassian is not able to locate this URL and is not able to send request on this URL. This doesn't have to do anything with backend technology ( I guess)

[Sam Harding]

Hi there @nish 

Sorry for delay in looking into this.

Looking at the response body, it seems that the issue is not so much not being able to locate the url/server, but that the request is being denied due to not being authorised (hence the 403 response code).

I am not sure what hosting infrastructure you have set up to grant public web access to your hosted VM, but it appears is is proxying via squid web proxy. This may be used by your hosting provider, and may indicate our servers are unauthorized to access your API?

With your successful request from other machines, are there any authorization headers you provide when making the request?

Cheers

Sam