Error stating "SSL version range is not valid" while using Selenium

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

Symptoms

Builds are failing during the source checkout stage with the following error:

1 2 Error occurred while running Task 'Checkout Default Repository(1)' of type com.atlassian.bamboo.plugins.vcs:task.vcs.checkout. (java.lang.RuntimeException : com.atlassian.bamboo.repository.RepositoryException: Cannot fetch branch '(unresolved) develop' from 'XXXXXXXXX' to source directory '/media/ephemeral0/build-dir/XXX-XXX-JOB1'. com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote https://XXXX:********@bitbucket.org/XXXXX/main failed with code 128. Working directory was [/media/ephemeral0/build-dir/XXX-XXX-JOB1]., stderr: [fatal: unable to access 'https://XXX:********@bitbucket.org/juralaw/main/': SSL version range is not valid.])

Diagnosis

The EC2 instance in use detected some funky environment variables that were the result of Selenium usage.

Workaround

Double check the LD_LIBRARY_PATH environment variable is unset. If it's not unsetting this variable can clear up the above error.

Updated on April 11, 2025

Still need help?

The Atlassian Community is here for you.