Data Center 5.2
Versions

_diagnostics HTTP Connectivity

_InclusionsLibrary

On this page

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

HTTP Connectivity

  • URL path tested: <URL>/rest/applinks/1.0/applicationlink
  • Valid HTTP success codes: 200, 401
Error(s)Steps to Resolve
  • Invalid URI
  • 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:

    ping jira.atlassian.com

    (info) 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.
  • 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.
Last modified on Sep 13, 2017

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.