I am trying to set up Issue Tracker integration with JIRA. This used to work for us previously when JIRA was on the local network. Then when we moved our JIRA to an Amazon EC2 instance it stopped working.
Now when I test the connection it fails, with one of two outcomes depending on how I enter the JIRA URL in settings:
- if I use http://jira.our-domain.net, there is a long pause of several minutes, and then it shows "Error: Connection timed out"
- if I use https://jira.our-domain.net, it immediately shows "Error: Connection refused"
The user account works if I log in to JIRA directly in a browser, so I know it is not a faulty login. I also confirmed "Accept remote API calls" is turned on in the JIRA options.
Could it be because the new JIRA instance is using a self-signed certificate? Some other problem?