Summary

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.

Environment

Bitbucket Server/Data Center

Diagnosis

Diagnostic Steps

• Ensure an SSH key has been added to the user or the repository

• Check the existing keys on the client by running

  ssh-add -l

• 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

Cause

If it has been confirmed that the correct key is being used, the problem may stem from an unidentified issue with the existing keys.

Solution

• Recreate the keys.