Bamboo Data Center application URL on browser showing as not secure after securing Bamboo using SSL

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

This article covers a scenario where Bamboo application URL was secured using SSL but when accessing the URL on the browser it showed not secure.

(Auto-migrated image: description temporarily unavailable)

Environment

The issue was seen on Bamboo 10.1.1 but the solution will be applicable for any other supported version of Bamboo

Diagnosis

If you are using chrome browser you can open the browser Devtools and open the security tab and access the application URL, the browser Devtools will show the exact error. In the below example it says the certificate which is used is missing the Subject Alternative Name.

But you can use the browser Devtools and security tab to understand if their is some other problem.

Cause

There can be multiple cause for this issue, below the are the few known causes

Cause 1 - Subject Alternative Name

As per the above error message the SAN (Subject Alternative Name) is missing from the certificate which is used.

Look at the below certificate from www.google.com it clearly contains Subject Alternative Name

(Auto-migrated image: description temporarily unavailable)

You can validate this for your certificate in couple of ways.

  1. By using the keytool command

keytool -v -list -keystore certificate_name.jks

ℹ️ Please replace certificate_name.jks with the name of your certificate

2. On the Browser you can check your certificate details by following the steps here

Cause 2 - Hostname mismatch in the subjectAlternativeName extension in the certificate

Hostname in the Web Browser does not match one of the Names in the subjectAlternativeName extension in the certificate. If your Bamboo URL has multiple DNS entries, and the URL you are using to access Bamboo UI is not included in the SAN (Subject Alternative Name) extension in the certificate.

Solution

Solution 1

Please ask the Certificate authority who signed or issued the certificate to include the SAN (Subject Alternative Name) in the certificate and then you can use that certificate to secure Bamboo and the error should be gone.

Solution 2

You need to add all of the DNS entries/URLs into the certificate SAN (Subject Alternative Name) extension to be able to use them with https.

Updated on May 22, 2025

Still need help?

The Atlassian Community is here for you.