The JIRA Server App is giving "cannot check compatibility" errors when connecting from outside our corporate network, but no such problem when inside our network.
Same URL works fine in browser whether inside or outside our network.
We have a reverse proxy in place that allows access to the server from outside, there's no page level filters on there but there are restrictions on ports.
Is the app making any strange requests? e.g. http or a different port?
Hello @JasonH Arvato
Thank you for reaching out.
Indeed, the error you are facing usually happens when you have configured a custom filter to prevent unauthenticated requests to your server.
In fact, the default port used by JIRA app is 8080, so I recommend you double-check if that port is not restricted and confirm if your proxy configuration is configured to allow
<jira-base-url>/server-infoto pass through without authentication, as mentioned in the KB below:
Let me know if this information helps.
We have no proxy or filter that blocks specific URLs. What we do have is a reverse proxy in our DMZ which forwards <baseURL>:80 and <servername>:8080 and <baseURL>:8443 to <servername>:8443.
On the JIRA server we used server.xml setting so that http 8080 traffic is redirected to https 8843.
Due to our DNS config the internal users traffic is resolving directly to the JIRA server, whereas external user the traffic resolving to the reverse proxy in DMZ.
When I try https://<jira-base-url>/server-info from either external or internal network I just get a 404. The strange thing here is that the app can do the compatibility check on the internal network but not from external. So there must be something working internal but not external.
Once the compatibility check has been performed using internal connection then the app works fine externally. Unfortunately some of our users are external and will never be able to get connected via the internal network, so for them the app doesn't work.