I have problems trying to get the attached files to an issue through HTTPS using a client made in AngularJS+NodeJS+ExpressJS.
This client makes use of the JIRA API so I can get information of projects, issues, even information related to the files attached, but when I try to get the file I get a 502 error or HTTP /1.1 Service Unavailable.
Is this something directly related to the use of HTTPS?, because if I configure mi client to point to JIRA using HTTP then I'm able to open the files attached.
Thanks in advance.
Can you reproduce the issue using curl? It sounds like there is a server or proxy error occurring. Any errors in the JIRA logs when this happens?
Hello Boris, thanks for your answer!
I've used Curl and Wget and I keep getting the same error. No, there are no entries in JIRA log, it seems that is something related to the communication between my client and the JIRA server, but only when I use HTTPS. There are no firewalls on the network and the only proxy configured is the one from JIRA.
I have installed the CA on my Debian and when I try to get the attached file from any ISSUE the same error happens: "502 Bad Gateway" or "HTTP /1.1 Service Unavailable."
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have a proxy between JIRA and the world? Maybe the proxy is handling something wrong?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you execute the curl attempt directly on the JIRA server and bypass the proxy, does the issue re-occur?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.