Bitbucket Cloud deprecating TLSv1 and TLSv1.1

Issue

  • Builds are failing to clone or update a Bitbucket repository with an error Cannot communicate securely with peer: no common encryption algorithm(s) like:
ERROR: Error fetching remote repo 'origin' 
hudson.plugins.git.GitException: Failed to fetch from https://bitbucket.org/my-org/my-repository.git 
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:888) 
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1155) 
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186) 
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) 
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) 
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) 
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) 
at hudson.security.ACL.impersonate(ACL.java:260) 
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) 
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
at java.lang.Thread.run(Thread.java:748) 
Caused by: hudson.plugins.git.GitException: Command "git fetch --no-tags --progress https://bitbucket.org/my-org/my-repository.git ..." returned status code 128: 
stdout: 
stderr: fatal: unable to access 'https://bitbucket.org/my-org/my-repository.git/': Cannot communicate securely with peer: no common encryption algorithm(s)

Environment

Resolution

On Saturday, 1st December 2018, Bitbucket Cloud disabled access to their service using weak cryptographic ciphers.

The removal of weak ciphers is permanent.

For DEV@cloud users this means that you won’t be able to connect to Bitbucket Cloud over HTTPS on Fedora 17 build agents which are used by default.

To avoid this issue you can either switch to SSH authentication or use our Fedora 25 build agents as described in this article.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.