Git Operations Fail - Permission denied - publickey
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Problem
Having enabled SSH access in Bitbucket Server (and having added SSH keys to the correct user profile in Bitbucket Server) git operations fail with the following message on the console:
[drohan@test_box]$ git pull
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
Diagnosis
Enable debug logging for git to see the command that is failing (NOTE: curl isn't used for the SSH protocol):
export GIT_TRACE_PACKET=1
export GIT_TRACE=1
export GIT_CURL_VERBOSE=1
export GIT_SSH_COMMAND=ssh -vvvvAObs: In case you are running on a Windows machine, replace export with set.
Sample output:
[drohan@test_box]$ git pull
trace: exec: 'git-pull'
trace: run_command: 'git-pull'
trace: built-in: git 'rev-parse' '--git-dir'
trace: built-in: git 'rev-parse' '--is-bare-repository'
trace: built-in: git 'rev-parse' '--show-toplevel'
trace: built-in: git 'ls-files' '-u'
trace: built-in: git 'symbolic-ref' '-q' 'HEAD'
trace: built-in: git 'config' '--bool' 'branch.master.rebase'
trace: built-in: git 'config' '--bool' 'pull.rebase'
trace: built-in: git 'rev-parse' 'q' '-verify' 'HEAD'
trace: built-in: git 'fetch' '--update-head-ok'
trace: run_command: 'ssh' '-p' '7999' 'drohan@kidney' 'git-upload-pack '\''/repo.git'\'''
Permission denied (publickey).
fatal: The remote end hung up unexpectedlyEnable verbose logging for SSH (-v Verbose mode) to identify why the error is happening:
% ssh -p 7999 -vT git@localhost
OpenSSH_5.9p1 Debian-5ubuntu1.4, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to localhost [127.0.0.1] port 7999.
debug1: Connection established.
debug1: identity file /home/josh/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/josh/.ssh/id_rsa-cert type -1
debug1: identity file /home/josh/.ssh/id_dsa type -1
debug1: identity file /home/josh/.ssh/id_dsa-cert type -1
debug1: identity file /home/josh/.ssh/id_ecdsa type -1
debug1: identity file /home/josh/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version SSHD-CORE-0.13.0
debug1: no match: SSHD-CORE-0.13.0
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1.4
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: RSA e8:6d:e4:fd:47:54:fe:12:d7:a1:85:43:fd:e0:cb:c5
debug1: Host '[localhost]:7999' is known and matches the RSA host key.
debug1: Found key in /home/josh/.ssh/known_hosts:2
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/josh/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
Agent admitted failure to sign using the key.
debug1: Trying private key: /home/josh/.ssh/id_dsa
debug1: Trying private key: /home/josh/.ssh/id_ecdsa
debug1: No more authentication methods to try.
Permission denied (publickey).Cause
There are several causes (examples will be added as they become available):
- In the example above, the wrong private keys were being referenced:
/home/josh/.ssh/id_dsaand/home/josh/.ssh/id_ecdsa
Solution
- Verify that identity file you generated is working:
Verify the correct private key is works by explicitly sourcing it:
ssh -p 7999 -i ~/.ssh/id_rsa -vT git@localhost
If the command above is not working, please make sure you add the corresponding public key to Bitbucket server either as an access or personal SSH key. Copy and paste the content of the file below:
cat < ~/.ssh/id_rsa.pubMore details of the procedure below can be found on:
If the test above works, set the correct default SSH key location. The correct location for the source of the private key can be redefined:
% ssh-agent -l % ssh-add ~/.ssh/id_rsa
Additional Information
Also validate if the private key path set on SSH config is correct. Or if the private key wasn't removed or moved to a different folder.
Checking the private key file, from ~/.ssh/config file:
Host bitbucketdc
HostName bitbucketdc
IdentityFile </path/to/your/private_key>In case the private key is missing, we will see an error similar to the one below on the Git client output:
debug1: Trying private key: /.ssh/id_dsa
debug3: no such identity: /.ssh/id_dsa: No such file or directory
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.We should see "no such identify" for all private keys attempts, and in case that is happening, confirm if the private key file still exists or if it's available on a different folder.