Received fatal alert: handshake_failure

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.

Please note that Atlassian Support does not provide troubleshooting for SSL certificates as describe by our support offering here:

Atlassian products interface with a variety of technologies. Front-end solutions like Web Servers (eg Apache HTTP Server), load balancers, single sign-on solutions (SSO), SSL certificates and LDAP repositories add functionality that is often critical to functioning of our products.

Atlassian will endeavour to provide documentation for integration with these 3rd party applications but does not provide support for 3rd party applications. We are unable to provide support when a failure in a 3rd party application occurs.


You have already imported the target server's certificate into Confluence's keystore, as described in Connecting to LDAP or Jira applications or Other Services via SSL.

The following appears in the atlassian-confluence.log:

org.springframework.ldap.CommunicationException: server:636; nested 
exception is javax.naming.CommunicationException: server:636 [Root exception is Received fatal alert: handshake_failure]


The CA's intermediate certificates are not imported into Confluence's keystore. For example: (GlobalSign), or this: (for GoDaddy, refer to the section under "Installing Your SSL in Tomcat").


  • Follow your CA's instructions to import the intermediate certs into Confluence's keystore. You may need to contact your CA's support for further assistance, as this is beyond the scope of Atlassian Support


This page covers how to resolve SSL handshake issues caused because the intermediate keystores have not been installed into Confluence's keystore.

Last modified on Oct 16, 2018

Was this helpful?

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