Unable to clone Git repo

Edited

I cannot clone git repository to my local drive using sourcetree. I have been added to my company git account, and have the same developer rights as other engineers. 

I can view the files in the repository, but when I go to clone I get the following error;

git.png

When I click details I get the following output;

Command: git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks ls-remote git@bitbucket.org:fraserantistaticbristol/lcdc-proteus.git
Output:
Error: fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

If I copy the command and paste it in a terminal window I get the following output;

 $ git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks ls-remote git@bitbucket.org:fraserantistaticbristol/lcdc-proteus.git
7a1011f878c4e333b3de1773a04ff0474dfd0f2e HEAD
7a1011f878c4e333b3de1773a04ff0474dfd0f2e refs/heads/master
43092faac7a28f071f0cf9d0edded6d405ec6b4c refs/tags/RevBDatapackIss1
d471b780e80f8af945982402f24c6a3aee8c7001 refs/tags/Sent_CJ_22_August

So I seem to have access.

Please help. :(

 

Update: I can clone the repo using the built in terminal in sourcetree. by running 

git clone git@bitbucket.org:fraserantistaticbristol/lcdc-proteus.git 

But obviously I need this working in the GUI.

 

2 answers

1 accepted

1 vote
Answer accepted

Update: I have found the answer. I had too many private keys open in pagent. We have lots of test machines in the company that I am able to ssh into. So I wrote a quick batch script to load all the private keys in pagent on system startup. This apparently breaks sourcetree for some reason. I have updated the script to only open the two most regularly used. This has solved my problem.

0 votes
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 15, 2022

G'day Chris! 

The most common issue customers are experiencing related to authentication in SourceTree is due to the deprecation of GIT username/password over HTTPS in favour of App Passwords:
https://bitbucket.org/blog/deprecating-atlassian-account-password-for-git-and-bitbucket-api-activity


We have a blog post however which explains the steps to troubleshoot this issue, please follow all of these accordingly and this should resolve the issue:
https://community.atlassian.com/t5/Sourcetree-articles/Bug-Fix-Sourcetree-for-Windows-authentication-error-when/ba-p/1965968

 

Cheers!

- Ben (Bitbucket Cloud Support)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events