When trying to connect an on-premise JIRA server to Unito, you might get the following error:
JIRA can be quite picky to match the URL you're using in your browser (or for API access), and the URL it's configured to listen to. If you've setup one of the strategies discussed here, you may encounter this error. If you're using an ngrok tunnel, here's a specific guide for ngrok. Otherwise, here's how to address this error:
1) Test your JIRA URL
Try to access the JIRA login page using the URL you've configured for Unito. At the bottom of the page, do you see a warning similar to this one?
That's the warning we'll be getting rid of.
2) Add a connector to JIRA's server.xml
Open the server.xml configuration file for your JIRA application. By default, you'll find it under the conf/ folder of your JIRA installation.
Find the element under the <Service> section. You'll want to add a new element as such:
connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443" acceptCount="100" disableUploadTimeout="true"
proxyName="jira-external.example.com" proxyPort="443" scheme="https" secure="true"/>
The important part is shown in bold. Set the proxyName to the host name you want Unito to connect to.
Note, we used port="8081", but you can choose any other port. Just make sure to set your reverse proxy correctly.
3) Restart JIRA
Restart your JIRA server.
Now, if you access the JIRA URL again, you should no longer see the warning.
4) Connect your JIRA server to Unito
In the Unito app, add a new JIRA connector. When prompted, paste the full URL to your JIRA server. You should then be prompted to login/authorize by your JIRA server. You can now create new syncs with your JIRA server!
If you're still having trouble or would like a more advanced network configuration, please reach out to us and we'll figure out the right setup with you.
You might also want to refer to JIRA's documentation on proxies.