Error message: peer not authenticated when creating Application Link to Cloud

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community



When create a new application link using HTTPS protocol to Cloud instances, it shows that server not reachable

And throw the below errors in the log (Cloud logs or the application log where you are connecting):

2015-08-05 10:39:51.332747500 2015-08-05 10:39:51,324 ajp-nio- ERROR sysadmin 639x23143x1 qfhlbe, /rest/applinks/2.0/applicationlinkForm/manifest.json [] ManifestNotFoundException thrown while retrieving manifest
2015-08-05 10:39:51.332749500 com.atlassian.applinks.spi.manifest.ManifestNotFoundException: peer not authenticated
2015-08-05 10:39:51.332750500 	at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.download1(
2015-08-05 10:39:51.332763500 	at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.access$000(
2015-08-05 10:39:51.332764500 	at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1$1.<init>(
2015-08-05 10:39:51.332764500 	at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(
2015-08-05 10:39:51.332766500 	at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(
2015-08-05 10:39:51.332766500 	at$ComputingValueReference.compute(
2015-08-05 10:39:51.332769500 	at$ComputingSegment.compute(
2015-08-05 10:39:51.332770500 	at$ComputingSegment.getOrCompute(
2015-08-05 10:39:51.332771500 	at
2015-08-05 10:39:51.356043500 Caused by: peer not authenticated
2015-08-05 10:39:51.356044500 	at
2015-08-05 10:39:51.356049500 	at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.verifyHostName(
2015-08-05 10:39:51.356050500 	at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(
2015-08-05 10:39:51.356050500 	at
2015-08-05 10:39:51.356052500 	at org.apache.commons.httpclient.HttpConnection.tunnelCreated(




Diagnostic Steps

  • Check your application's SSL certificate for any issue on the following page
  • Specifically take note of the result under Handshake Simulation on the items below:

    Java 6u45   No SNI 2		TLS 1.0 	TLS_RSA_WITH_RC4_128_MD5 (0x4)   No FS   RC4 	128
    Java 7u25 	Client aborts on SNI unrecognized_name warning 	Fail3
    Java 8u31 	Client aborts on SNI unrecognized_name warning 	Fail3

    Sample of failed handshake that caused the error

  • A good configuration should have the below result shown when testing:


Starting from JAVA 7, JAVA has introduced SNI support which is enabled by default. If the configuration of the server name or server alias is set wrongly of not set. It will fail the handshake between JAVA and the application.

More on SNI.


Apache related configuration is not supported at as outlined in our Atlassian Support Offerings. If you have issue configuring/editing the configuration file, please head towards Answers where our community resides, they might be able to point you towards resolution to your issue.

Check the Apache config file and add the ServerName or ServerAlias as per the code block below:


(info) Replace the rightful domain name for your application

Last modified on Feb 26, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.