Handshake failed during wrap javax.net.ssl.SSLHandshakeException error seen in Bitbucket

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

After adding SSL configurations to the bitbucket.properties file, the browser displays an SSL error when navigating to the user interface.

Environment

  • Bitbucket 7.6.0

  • Bouncycastle < 1.65

  • JDK 8u272

Diagnosis

When navigating to the application the following is written to the Bitbucket Server logs files:

1 2 2020-11-26 09:24:27,779 DEBUG [https-jsse-nio-8444-exec-5] o.a.tomcat.util.net.SecureNioChannel Handshake failed during wrap javax.net.ssl.SSLHandshakeException: No available authentication scheme

Cause

By default the following property supports all protocols

1 server.ssl.enabled-protocols=all

As such TLSv1.3 is enabled and can lead to this issue.

Solution

Add or change the property so that TLSv1.3 is disabled by setting it to TLSv1.2:

1 server.ssl.enabled-protocols=TLSv1.2

Updated on March 11, 2025

Still need help?

The Atlassian Community is here for you.