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

git@bitbucket.org: Permission denied (publickey) in windows

Yunus Burhani December 1, 2023

It used to work and all of a sudden stop working. I have changed my keys couple of times as well but nothing is working. I have created a config file as well.

I ran this command

ssh -t -vvv git@bitbucket.org


here is the dump from it

OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug1: Reading configuration data C:\\Users\\yburhani/.ssh/config
debug1: C:\\Users\\yburhani/.ssh/config line 1: Applying options for bitbucket.org
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolving "bitbucket.org" port 22
debug2: ssh_connect_direct
debug1: Connecting to bitbucket.org [104.192.141.1] port 22.
debug1: Connection established.
debug1: identity file C:\\Users\\yburhani/.ssh/id_ed25519 type 3
debug3: Failed to open file:C:/Users/yburhani/.ssh/id_ed25519-cert error:2
debug3: Failed to open file:C:/Users/yburhani/.ssh/id_ed25519-cert.pub error:2
debug1: identity file C:\\Users\\yburhani/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1
debug1: Remote protocol version 2.0, remote software version conker_f748387242 a59322c98fd9
debug1: no match: conker_f748387242 a59322c98fd9
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to bitbucket.org:22 as 'git'
debug3: hostkeys_foreach: reading file "C:\\Users\\yburhani/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\yburhani/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from bitbucket.org
debug3: Failed to open file:C:/Users/yburhani/.ssh/known_hosts2 error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2
debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,ext-info-s
debug2: host key algorithms: ssh-ed25519,ecdsa-sha2-nistp256,ssh-rsa,rsa-sha2-256,rsa-sha2-512
debug2: ciphers ctos: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,chacha20-poly1305@openssh.com
debug2: ciphers stoc: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,chacha20-poly1305@openssh.com
debug2: MACs ctos: hmac-sha2-256-etm@openssh.com,hmac-sha2-256,hmac-sha1,hmac-sha1-96
debug2: MACs stoc: hmac-sha2-256-etm@openssh.com,hmac-sha2-256,hmac-sha1,hmac-sha1-96
debug2: compression ctos: none
debug2: compression stoc: none
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:FC73VB6C4OQLSCrjEayhMp9UMxS97caD/Yyi2bhW/J0
debug3: hostkeys_foreach: reading file "C:\\Users\\yburhani/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\yburhani/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from bitbucket.org
debug3: Failed to open file:C:/Users/yburhani/.ssh/known_hosts2 error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2
debug3: hostkeys_foreach: reading file "C:\\Users\\yburhani/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\yburhani/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from 104.192.141.1
debug3: Failed to open file:C:/Users/yburhani/.ssh/known_hosts2 error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2
debug1: Host 'bitbucket.org' is known and matches the ECDSA host key.
debug1: Found key in C:\\Users\\yburhani/.ssh/known_hosts:1
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: C:\\Users\\yburhani/.ssh/id_ed25519 ED25519 SHA256:8IOnwOoeVAarUNQulKJJY0JQM/B9XxJ2uys1hlEVsjc explicit agent
debug2: pubkey_prepare: done
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-rsa,ecdsa-sha2-nistp256,ecdsa-sha2-nistp521,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp384,ssh-dss-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: C:\\Users\\yburhani/.ssh/id_ed25519 ED25519 SHA256:8IOnwOoeVAarUNQulKJJY0JQM/B9XxJ2uys1hlEVsjc explicit agent
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
git@bitbucket.org: Permission denied (publickey).

1 answer

0 votes
Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 4, 2023

G'day, @Yunus Burhani 

Based on the debug log you've shared, It seems that SSH is unable to locate the private key on your local machine:

debug1: Reading configuration data C:\\Users\\yburhani/.ssh/config
debug1: C:\\Users\\yburhani/.ssh/config line 1: Applying options for bitbucket.org
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolving "bitbucket.org" port 22
debug2: ssh_connect_direct
debug1: Connecting to bitbucket.org [104.192.141.1] port 22.
debug1: Connection established.
debug1: identity file C:\\Users\\yburhani/.ssh/id_ed25519 type 3
debug3: Failed to open file:C:/Users/yburhani/.ssh/id_ed25519-cert error:2
debug3: Failed to open file:C:/Users/yburhani/.ssh/id_ed25519-cert.pub error:2

If the SSH key does exist, please review your SSH config again and ensure that it's pointing to the correct key:

Host bitbucket.org
AddKeysToAgent yes
IdentityFile C:\\Users\\yburhani/.ssh/{key-name}

The above example assumes that the ssh key is generated at "C:\\Users\\yburhani/.ssh/". If it's in a different location, please update them.

Let me know how it goes.

Regards,
Syahrul

Yunus Burhani December 8, 2023

I have this file in the correct place

debug1: identity file C:\\Users\\yburhani/.ssh/id_ed25519

I do not have these files as it should not be using certs

 

debug3: Failed to open file:C:/Users/yburhani/.ssh/id_ed25519-cert error:2
debug3: Failed to open file:C:/Users/yburhani/.ssh/id_ed25519-cert.pub error:2

 

I changed my config file to give full path

 IdentityFile C:\\Users\\yburhani/.ssh/id_ed25519

 

It used to be

 IdentityFile ~/.ssh/id_ed25519 

 

Still did not work

Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 10, 2023

Hi @Yunus Burhani 

Could you please confirm if the SSH key generated earlier is the one you are using and if the public key has been added to your Bitbucket account? Ensuring that all steps outlined in our guide have been properly followed is important. Please see below for the guide:

https://support.atlassian.com/bitbucket-cloud/docs/set-up-personal-ssh-keys-on-windows/

Regards,
Syahrul

Yunus Burhani December 14, 2023

I figured it out. My git was updated recently and lost the connection to ssh.

Thanks for all your help.

Like Syahrul likes this

Suggest an answer

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

Atlassian Community Events