| Error(s) | Steps to Resolve |
|---|
| - Is the URL valid?
- Is the display URL same as the base URL configured in the target application?
- Can you connect to the target application URL from the server running the diagnostics?
|
- Unknown Host
- java.net.ConnectException: Connection refused
| - Is the server running the target application reachable?
Check if you can ping the target server from the server that is running the AppLinks diagnostics plugin. For example, when trying to verify if Confluence can access JIRA, execute the following on the Confluence server:  Replace jira.atlassian.com with the display URL of the target instance.
|
- Redirect count from <URL> exceeded maximum of <maximum>.
- Received HTTP <status code> redirect...
- Got HTTP <status code> redirect from <URL> but no redirect location was specified.
| - This indicates there is a problem with the redirection of HTTP requests. Most commonly caused by proxy/load-balancer configurations.
- Is your target application behind a reverse proxy? If so, verify the proxy configuration is per the official recommendation. Below is the recommended configurations for JIRA:
|
- Failed to ping <Application>.
- Received unexpected HTTP <status code> response from <URL> using...
| - Is the target application accessible at the display/application URL?
- Try connecting to the application using the display URL and verify if the application is available and you are able to log in.
|
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.