Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Getting fatal error when trying to clone from Bitbucket into SourceTree

I am trying to clone a repository in Bitbucket to my local PC using SourceTree. I have added my SSH key to Bitbucket and set up my private key in SourceTree, and on the remote tab I see the list of available repositories. I click on the clone link next to one of the repositories and it fails, giving this error:

Command: git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks ls-remote
Error: fatal: unable to access '': SSL certificate problem: self signed certificate in certificate chain

I am using the same SSH key pair on another PC and they work fine. Any idea why it is failing?


1 answer

0 votes

Hello @Ron Rabakukk ,

I am not entirely familiar with this topic but I'll do what I can to help, looking into it Bitbucket cloud does not have a self-signed certificate in its chain, and when using self-signed certificates Bitbucket provides the Skip certificate verification option, which allows you to disable certificate verification which is described in more detail in:

The overall recommendation is to NOT disable certificate verification but rather obtain an SSL certificate from a trusted certificate authority.  But overall there should not be any self-signed certs coming from the BitBucket cloud side.

Additionally there is a possibility of one of the git clients or sourcetree on your machine is outdated and maybe doesn’t recognize one of the CAs in the Bitbucket cert chain, that would explain why it works on one machine but not this machine.

Can you verify that you’re running on the latest version of sourcetree which looks to be 4.1.8_244 and also that the system you’re running it on is all up to date on packages\system updates etc.. as well as verify that the machine this works on is the same version as the one it is failing on?


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events