ERR_SSL_VERSION_OR_CIPHER_MISMATCH error when using Crucible over HTTPS

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

Problem

Browsing to Fisheye/Crucible dashboard running over HTTPS shows the following error in the browser:

1 2 3 This site can't provide a secure connection <crucible-url> uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH

ℹ️ This error is seen even after successfully setting up keystore and truststore on Crucible end as per instructions on Fisheye SSL Configuration page.

Diagnosis

Fisheye/Crucible do not support keystores of PKCS12 format. Hence, any PKCS12 format keystore must be converted to JKS format. To verify the keystore format, use:

1 keytool -v -list -keystore <path to keystore file>

You should see something like:

1 2 3 4 5 6 Keystore type: JKS Keystore provider: SUN Your keystore contains 1 entry ... ...

Now, force the keystore format to be PKCS12 and list the entries again:

1 keytool -v -list -keystore <path to keystore file> -storetype pkcs12

If the output is the following, then the keystore is in PKCS12 format:

1 2 3 4 5 6 Keystore type: PKCS12 Keystore provider: SunJSSE Your keystore contains 1 entry ... ...

Cause

Fisheye/Crucible does not support PKCS12 format keystores.

Resolution

Convert the keystore to JKS format:

  • Change the extension of the keystore file to .p12

  • Convert the keystore to JKS format as follows:

1 keytool -importkeystore -srckeystore <path/to/keystore/with/.p12/extension> -destkeystore <new/keystore/file with/.jks/extension>

Updated on April 10, 2025

Still need help?

The Atlassian Community is here for you.