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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Admin cannot clone all repos in workspace

I made a colleague admin of a workspace, yet he cannot clone all repositories in that workspace. He could clone one of the repositories, but not another.

He has added an SSH key in the account and to ~/.ssh/config.

Anyone has an idea of what might be the reason and how to solve it?

1 answer

0 votes

Hello and welcome to the community!

Is your colleague able to access from browser the repo he cannot clone?

One possibility is that the User group that your colleague has been added to does not have access to the repo he cannot clone. Sometimes users accidentally remove certain user groups, even admin groups, from the repo's Settings.

To double check, you can go to Repository Settings > User and group access > make sure that the User group you added your colleague to is listed in the Groups section.

If he can view the repo from browser, then it doesn't sound like this is a permissions issue.

In this case, it would be helpful to see the output of the clone command as this could give us an indication of why this issue occurs. Would you be able to share this with us?

Kind regards,

He sent me a screenshot listing all repositories, including the one that he cannot clone.

I see no difference on the **User and group access** pages for that repository and the one he could clone.

Here's the output from when he was trying to clone the repository:

git clone
Cloning into 'geometry'...
fatal: Could not read from remote repository. Please make sure you have the correct access rights
and the repository exists.


One possible reason I can think of is that an incorrect SSH key may be used to clone the repo.

Assuming that the name of the private key he generated for his Bitbucket account is named id_rsa, I would suggest asking him to clone with the following command and see if it works:

GIT_SSH_COMMAND="ssh -i ~/.ssh/id_rsa" git clone

If this also fails, then we would need to see the output of:

ls -lah ~/.ssh

to see if there are more than one SSH keys there, the output of

GIT_SSH_COMMAND="ssh -Tvvv -i ~/.ssh/id_rsa" git clone
GIT_SSH_COMMAND="ssh -Tvvv" git clone

so that we have more verbose output on the clone commands (both with and without specifying the SSH key to be used)

and also the contents of his ~/.ssh/config file, just the entries that are referring to

Kind regards,

We found the reason. He had added his SSH key to one repository instead of to his account. Therefore he could clone that repository but not another.

Like Theodora Boudale likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

3,706 views 10 16
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you