Git clone fails when cloning via SSH
Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms.
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
Git clones fail when using SSH even if an Access key has been added to the repository or an SSH key has been added to the user's profile.
$ git clone ssh://git@<bitbucket URL>:<bitbucket port>/<project key>/<repository slug>.git
Cloning into '<repository slug>'...
Repository not found
The requested repository does not exist, or you do not have permission to access it.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Bitbucket Server/Data Center
- Ensure an SSH key has been added to the user or the repository
Check the existing keys on the client by running
Attempt to clone a change to the repository with the Git client debug on:
# Example on Linux GIT_SSH_COMMAND="ssh -vvv" git clone ssh://git@<bitbucket URL>:<bitbucket port>/<project key>/<repository slug>.git
The log will show which key has been used for the authentication and which ones have been tried. The line to check will look like the following:
debug1: Offering RSA public key: /Users/<username>/.ssh/id_rsa
If it has been confirmed that the correct key is being used, the problem may stem from an unidentified issue with the existing keys.