Create Sign up Log in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
Unable to clone repository even with SSH key correctly generated and added
Hi !
I recently created a new account in Bitbucket and a new repository, using my personal email, for a small pet project. I log in using Google Authentication, even though it should not affect this issue.
After setting up the new repository, I generated a new SSH in my Windows 10 machine, added it to the authorized SSH keys in Bitkucket's personal settings area, and I made sure ssh-agent was running in my machine and had the new key added to it.
Still, when trying to clone the repository I still get a forbidden error.
"Cloning into 'my-repo-main'...
Forbidden
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists."
I tried running the console as Administrator, I checked that the key was in fact correctly generated and added to Bitbucket as per the instructions, but still no solution.
I also tried checking the connection to bitbucket, which seems to use the correct key and succeed in authenticating:
(...)
debug3: sign_and_send_pubkey: signing using rsa-sha2-512
debug3: send packet: type 50
debug3: receive packet: type 52
debug1: Authentication succeeded (publickey).
Authenticated to bitbucket.org ([104.192.141.1]:22).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Entering interactive session.
debug1: pledge: network
debug3: receive packet: type 91
debug2: channel_input_open_confirmation: channel 0: callback start
debug2: fd 3 setting TCP_NODELAY
debug2: client_session2_setup: id 0
debug2: channel 0: request shell confirm 1
debug3: send packet: type 98
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 2097152 rmax 32768
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
debug3: receive packet: type 98
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug3: receive packet: type 96
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug3: receive packet: type 97
debug2: channel 0: rcvd close
debug2: channel 0: chan_shutdown_read (i0 o1 sock -1 wfd 4 efd 6 [write])
debug2: channel 0: input open -> closed
debug3: channel 0: will not send data after close
authenticated via ssh key.
You can use git to connect to Bitbucket. Shell access is disabled
(...)
Still, when I try to clone the repo, I still get the forbidden error above.
I have created Bitbucket accounts and cloned repositories before, so this is really strange not being able to perform such a simple and basic cloning as I have done dozens of times before. Maybe I am just missing something ? Is there something I may be overlooking?
Thank you for any input or suggestions, greatly appreciated.
2 answers
Norbert Csupka
Atlassian Team
January 3, 2022 edited Atlassian Team members are employees working across the company in a wide variety of roles.
Thank you for contacting Atlassian Community. My name is Norbert and I'm a Bitbucket Cloud Support Engineer, it's nice to meet you! Welcome to the Atlassian Community :)
I would like to ask if you could give us a verbose output from the clone event which is failing with your new SSH key? You can provide the verbose output the following way (please mask or remove all the private information):
GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_CURL_VERBOSE=1 GIT_SSH_COMMAND="ssh -vvv" git clone git@bitbucket.org:workspace/repository
Once we have the verbose output, we will be able to investigate what could be the point of failure.
We're looking forward to hear from you
Best Regards,
Norbert
Atlassian Bitbucket Cloud Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for the delay in replying, I had to move forward and skipped BitBucket altogether at the time.
I believe this issue may actually be related to some local git setting/local environment variable, and my local git may be misconfigured for some reason.
Regardless, I have set the debug environment variables as per your post, and this is the output:
ec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/bin
15:59:43.805992 git.c:455 trace: built-in: git clone git@bitbucket.org:xxxxxxxxxx/gtfs-rt2mapify.git
Cloning into 'gtfs-rt2mapify'...
15:59:43.820995 run-command.c:668 trace: run_command: GIT_PROTOCOL=version=2 '"ssh -vvv"' -G -o SendEnv=GIT_PROTOCOL git@bitbucket.org
15:59:43.851989 run-command.c:668 trace: run_command: unset GIT_DIR; '"ssh -vvv"' git@bitbucket.org 'git-upload-pack '\''xxxxxxxxxx/gtfs-rt2mapify.git'\'''
"ssh -vvv": ssh -vvv: command not found
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
It also seems setting GIT_SSH_COMMAND environment variable in Windows may not be having the necessary effect
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Norbert Csupka
Atlassian Team
January 21, 2022 edited Atlassian Team members are employees working across the company in a wide variety of roles.
Thank you for your reply.
Can you let me know in which app were you trying to do this verbose clone? I'd like to inform you that I also have Windows on my local system, but this command worked for me, while I was using "Git Bash".
Can you try to do this command in Git Bash as well and let me know if it's successful?
Please let me know.
Best Regards,
Norbert
Atlassian Bitbucket Cloud Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Norbert Csupka ,
Thank you for your continued support.
I was using VS Code Terminal (what I have pretty much always used without issues), and just in case I also tried Windows Command Line in Admin mode, and PowerShell console, but I completely forgot the obvious approach of trying with GitBash!
Here's what I noticed:
- Trouble connecting to bitbucket port 22 through IPv6
- For some reason the key file is not accepted
- I have two separate keys for two separate git users, I will check if that could be the issue for some reason, and I will report back
Here's the full ouput:
XXXXX@3770K MINGW64 ~
$ GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_CURL_VERBOSE=1 GIT_SSH_COMMAND="ssh -vvv" git clone git@bitbucket.org:YYYYYY/gtfs-rt2mapify.git
08:50:04.710289 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/bin
08:50:04.711289 git.c:455 trace: built-in: git clone git@bitbucket.org:YYYYYY/gtfs-rt2mapify.git
Cloning into 'gtfs-rt2mapify'...
08:50:04.734289 run-command.c:668 trace: run_command: unset GIT_DIR; GIT_PROTOCOL=version=2 'ssh -vvv' -o SendEnv=GIT_PROTOCOL git@bitbucket.org 'git-upload-pack '\''YYYYYY/gtfs-rt2mapify.git'\'''
OpenSSH_8.8p1, OpenSSL 1.1.1l 24 Aug 2021
debug1: Reading configuration data /etc/ssh/ssh_config
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/c/Users/XXXXX/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/c/Users/XXXXX/.ssh/known_hosts2'
debug2: resolving "bitbucket.org" port 22
debug3: resolve_host: lookup bitbucket.org:22
debug3: ssh_connect_direct: entering
debug1: Connecting to bitbucket.org [2406:da00:ff00::22c5:2ef4] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::22c5:2ef4 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::3403:4be7] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::3403:4be7 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::6b17:d1f5] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::6b17:d1f5 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::22c0:3470] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::22c0:3470 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::22e9:9f55] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::22e9:9f55 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::22cd:e0db] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::22cd:e0db port 22: Connection timed out
debug1: Connecting to bitbucket.org [104.192.141.1] port 22.
debug3: set_sock_tos: set socket 4 IP_TOS 0x48
debug1: Connection established.
debug1: identity file /c/Users/XXXXX/.ssh/id_rsa type 0
debug1: identity file /c/Users/XXXXX/.ssh/id_rsa-cert type -1
debug1: identity file /c/Users/XXXXX/.ssh/id_dsa type -1
debug1: identity file /c/Users/XXXXX/.ssh/id_dsa-cert type -1
debug1: identity file /c/Users/XXXXX/.ssh/id_ecdsa type -1
debug1: identity file /c/Users/XXXXX/.ssh/id_ecdsa-cert type -1
debug1: identity file /c/Users/XXXXX/.ssh/id_ecdsa_sk type -1
debug1: identity file /c/Users/XXXXX/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /c/Users/XXXXX/.ssh/id_ed25519 type -1
debug1: identity file /c/Users/XXXXX/.ssh/id_ed25519-cert type -1
debug1: identity file /c/Users/XXXXX/.ssh/id_ed25519_sk type -1
debug1: identity file /c/Users/XXXXX/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /c/Users/XXXXX/.ssh/id_xmss type -1
debug1: identity file /c/Users/XXXXX/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.8
debug1: Remote protocol version 2.0, remote software version conker_3895844432 50abdfeaecda
debug1: compat_banner: no match: conker_3895844432 50abdfeaecda
debug2: fd 4 setting O_NONBLOCK
debug1: Authenticating to bitbucket.org:22 as 'git'
debug3: record_hostkey: found key type RSA in file /c/Users/XXXXX/.ssh/known_hosts:1
debug3: load_hostkeys_file: loaded 1 keys from bitbucket.org
debug1: load_hostkeys: fopen /c/Users/XXXXX/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug3: order_hostkeyalgs: prefer hostkeyalgs: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256
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,ext-info-c
debug2: host key algorithms: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,aes256-cbc,aes192-cbc
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,aes256-cbc,aes192-cbc
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-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss
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: rsa-sha2-512
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: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-rsa SHA256:zzXQOXSRBEiUtuE8AikJYKwbHaxvSc0ojez9YXaGp1A
debug3: record_hostkey: found key type RSA in file /c/Users/XXXXX/.ssh/known_hosts:1
debug3: load_hostkeys_file: loaded 1 keys from bitbucket.org
debug1: load_hostkeys: fopen /c/Users/XXXXX/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host 'bitbucket.org' is known and matches the RSA host key.
debug1: Found key in /c/Users/XXXXX/.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/XXXXX/.ssh/id_rsa RSA SHA256:+gTeuGPbJMrPrm+Zm8XT6zmTmC2bucP325dyQqSxJDo
debug1: Will attempt key: /c/Users/XXXXX/.ssh/id_dsa
debug1: Will attempt key: /c/Users/XXXXX/.ssh/id_ecdsa
debug1: Will attempt key: /c/Users/XXXXX/.ssh/id_ecdsa_sk
debug1: Will attempt key: /c/Users/XXXXX/.ssh/id_ed25519
debug1: Will attempt key: /c/Users/XXXXX/.ssh/id_ed25519_sk
debug1: Will attempt key: /c/Users/XXXXX/.ssh/id_xmss
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,rsa-sha2-512,ecdsa-sha2-nistp384,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,rsa-sha2-256,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp521,ssh-dss-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-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/XXXXX/.ssh/id_rsa RSA SHA256:+gTeuGPbJMrPrm+Zm8XT6zmTmC2bucP325dyQqSxJDo
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
debug1: Trying private key: /c/Users/XXXXX/.ssh/id_dsa
debug3: no such identity: /c/Users/XXXXX/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /c/Users/XXXXX/.ssh/id_ecdsa
debug3: no such identity: /c/Users/XXXXX/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /c/Users/XXXXX/.ssh/id_ecdsa_sk
debug3: no such identity: /c/Users/XXXXX/.ssh/id_ecdsa_sk: No such file or directory
debug1: Trying private key: /c/Users/XXXXX/.ssh/id_ed25519
debug3: no such identity: /c/Users/XXXXX/.ssh/id_ed25519: No such file or directory
debug1: Trying private key: /c/Users/XXXXX/.ssh/id_ed25519_sk
debug3: no such identity: /c/Users/XXXXX/.ssh/id_ed25519_sk: No such file or directory
debug1: Trying private key: /c/Users/XXXXX/.ssh/id_xmss
debug3: no such identity: /c/Users/XXXXX/.ssh/id_xmss: No such file or directory
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
git@bitbucket.org: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Norbert Csupka first of all, let me thank you once again for your support and quick feedback in helping me with in this issue.
I believe I finally figured it out and, as usual, it's always the simplest things...
- I had two separate key files (one for work, one for private pet projects) in my machine, each assigned to separate bitbucket accounts.
- I had each public key correctly added to their respective bitbucket account.
- I was performing the correct git clone command EXCEPT that in this case I was NOT specifying the account's specific key, so it was using the wrong one (the default one):
- I was actually led to think that it was reading the right key, since the initial command output was:
debug1: Authentication succeeded (publickey).
Authenticated to bitbucket.org ([104.192.141.1]:22).
- Since I was just doing a quick hack at the time, I did not take the time to investigate a little further (I know, my bad)
SOLUTION:
- I tried adding the same key to both work and personal bitbucket just to test if it was taking the wrong key previously, and it succeeded right away.
- It probably will also work if in the git clone command or .ssh/config file I explicitly specify which public key file to use for which bitbucket user (I will check this later)
Regardless, here's the full output if it helps anyone else in the future:
XXXXXX@3770K MINGW64 ~
$ GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_CURL_VERBOSE=1 GIT_SSH_COMMAND="ssh -vvv" git clone git@bitbucket.org:YYYYYY/gtfs-rt2mapify.git
09:12:21.562999 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/bin
09:12:21.564000 git.c:455 trace: built-in: git clone git@bitbucket.org:YYYYYY/gtfs-rt2mapify.git
Cloning into 'gtfs-rt2mapify'...
09:12:21.589075 run-command.c:668 trace: run_command: unset GIT_DIR; GIT_PROTOCOL=version=2 'ssh -vvv' -o SendEnv=GIT_PROTOCOL git@bitbucket.org 'git-upload-pack '\''YYYYYY/gtfs-rt2mapify.git'\'''
OpenSSH_8.8p1, OpenSSL 1.1.1l 24 Aug 2021
debug1: Reading configuration data /etc/ssh/ssh_config
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/c/Users/XXXXXX/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/c/Users/XXXXXX/.ssh/known_hosts2'
debug2: resolving "bitbucket.org" port 22
debug3: resolve_host: lookup bitbucket.org:22
debug3: ssh_connect_direct: entering
debug1: Connecting to bitbucket.org [2406:da00:ff00::3403:4be7] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::3403:4be7 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::22c5:2ef4] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::22c5:2ef4 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::22e9:9f55] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::22e9:9f55 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::22c0:3470] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::22c0:3470 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::22cd:e0db] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::22cd:e0db port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::6b17:d1f5] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::6b17:d1f5 port 22: Connection timed out
debug1: Connecting to bitbucket.org [104.192.141.1] port 22.
debug3: set_sock_tos: set socket 4 IP_TOS 0x48
debug1: Connection established.
debug1: identity file /c/Users/XXXXXX/.ssh/id_rsa type 0
debug1: identity file /c/Users/XXXXXX/.ssh/id_rsa-cert type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_dsa type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_dsa-cert type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ecdsa type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ecdsa-cert type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ecdsa_sk type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ed25519 type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ed25519-cert type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ed25519_sk type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_xmss type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.8
debug1: Remote protocol version 2.0, remote software version conker_3895844432 90c724de96bc
debug1: compat_banner: no match: conker_3895844432 90c724de96bc
debug2: fd 4 setting O_NONBLOCK
debug1: Authenticating to bitbucket.org:22 as 'git'
debug3: record_hostkey: found key type RSA in file /c/Users/XXXXXX/.ssh/known_hosts:1
debug3: load_hostkeys_file: loaded 1 keys from bitbucket.org
debug1: load_hostkeys: fopen /c/Users/XXXXXX/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug3: order_hostkeyalgs: prefer hostkeyalgs: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256
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,ext-info-c
debug2: host key algorithms: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,aes256-cbc,aes192-cbc
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,aes256-cbc,aes192-cbc
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-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss
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: rsa-sha2-512
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: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-rsa SHA256:zzXQOXSRBEiUtuE8AikJYKwbHaxvSc0ojez9YXaGp1A
debug3: record_hostkey: found key type RSA in file /c/Users/XXXXXX/.ssh/known_hosts:1
debug3: load_hostkeys_file: loaded 1 keys from bitbucket.org
debug1: load_hostkeys: fopen /c/Users/XXXXXX/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host 'bitbucket.org' is known and matches the RSA host key.
debug1: Found key in /c/Users/XXXXXX/.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/XXXXXX/.ssh/id_rsa RSA SHA256:+gTeuGPbJMrPrm+Zm8XT6zmTmC2bucP325dyQqSxJDo
debug1: Will attempt key: /c/Users/XXXXXX/.ssh/id_dsa
debug1: Will attempt key: /c/Users/XXXXXX/.ssh/id_ecdsa
debug1: Will attempt key: /c/Users/XXXXXX/.ssh/id_ecdsa_sk
debug1: Will attempt key: /c/Users/XXXXXX/.ssh/id_ed25519
debug1: Will attempt key: /c/Users/XXXXXX/.ssh/id_ed25519_sk
debug1: Will attempt key: /c/Users/XXXXXX/.ssh/id_xmss
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-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp521,ssh-dss-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ecdsa-sha2-nistp384,ssh-rsa-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/XXXXXX/.ssh/id_rsa RSA SHA256:+gTeuGPbJMrPrm+Zm8XT6zmTmC2bucP325dyQqSxJDo
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: /c/Users/XXXXXX/.ssh/id_rsa RSA SHA256:+gTeuGPbJMrPrm+Zm8XT6zmTmC2bucP325dyQqSxJDo
debug3: sign_and_send_pubkey: RSA SHA256:+gTeuGPbJMrPrm+Zm8XT6zmTmC2bucP325dyQqSxJDo
debug3: sign_and_send_pubkey: signing using rsa-sha2-512 SHA256:+gTeuGPbJMrPrm+Zm8XT6zmTmC2bucP325dyQqSxJDo
debug3: send packet: type 50
debug3: receive packet: type 52
Authenticated to bitbucket.org ([104.192.141.1]:22) using "publickey".
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Entering interactive session.
debug1: pledge: filesystem full
debug3: receive packet: type 91
debug2: channel_input_open_confirmation: channel 0: callback start
debug2: fd 4 setting TCP_NODELAY
debug3: set_sock_tos: set socket 4 IP_TOS 0x20
debug2: client_session2_setup: id 0
debug1: Sending environment.
debug3: Ignored env USERDOMAIN
debug3: Ignored env OS
debug3: Ignored env COMMONPROGRAMFILES
debug3: Ignored env PROCESSOR_LEVEL
debug3: Ignored env PSModulePath
debug3: Ignored env CommonProgramW6432
debug3: Ignored env CommonProgramFiles(x86)
debug3: Ignored env _
debug3: Ignored env MSYSTEM_CARCH
debug3: Ignored env DISPLAY
debug3: Ignored env HOSTNAME
debug3: Ignored env PUBLIC
debug3: Ignored env CONFIG_SITE
debug3: Ignored env GIT_TRACE_PACKET
debug3: Ignored env EXEPATH
debug3: Ignored env GIT_TRACE
debug3: Ignored env MSYSTEM_CHOST
debug3: Ignored env USERNAME
debug3: Ignored env ChocolateyInstall
debug3: Ignored env JAVA_HOME
debug3: Ignored env LOGONSERVER
debug3: Ignored env PROCESSOR_ARCHITECTURE
debug1: channel 0: setting env GIT_PROTOCOL = "version=2"
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env LOCALAPPDATA
debug3: Ignored env COMPUTERNAME
debug3: Ignored env !::
debug3: Ignored env SYSTEMDRIVE
debug3: Ignored env USERPROFILE
debug3: Ignored env PATHEXT
debug3: Ignored env SYSTEMROOT
debug3: Ignored env USERDOMAIN_ROAMINGPROFILE
debug3: Ignored env PROCESSOR_IDENTIFIER
debug3: Ignored env MINGW_PACKAGE_PREFIX
debug3: Ignored env OneDriveConsumer
debug3: Ignored env PWD
debug3: Ignored env SSH_ASKPASS
debug3: Ignored env HOME
debug3: Ignored env TMP
debug3: Ignored env LC_CTYPE
debug3: Ignored env TERM_PROGRAM
debug3: Ignored env TERM_PROGRAM_VERSION
debug3: Ignored env MSYSTEM_PREFIX
debug3: Ignored env GIT_SSH_COMMAND
debug3: Ignored env GIT_CURL_VERBOSE
debug3: Ignored env OneDrive
debug3: Ignored env PROCESSOR_REVISION
debug3: Ignored env TMPDIR
debug3: Ignored env NUMBER_OF_PROCESSORS
debug3: Ignored env ProgramW6432
debug3: Ignored env COMSPEC
debug3: Ignored env GIT_EXEC_PATH
debug3: Ignored env APPDATA
debug3: Ignored env TERM
debug3: Ignored env SHELL
debug3: Ignored env WINDIR
debug3: Ignored env MINGW_CHOST
debug3: Ignored env ProgramData
debug3: Ignored env SHLVL
debug3: Ignored env PLINK_PROTOCOL
debug3: Ignored env PROGRAMFILES
debug3: Ignored env ACLOCAL_PATH
debug3: Ignored env MANPATH
debug3: Ignored env ORIGINAL_TEMP
debug3: Ignored env ORIGINAL_TMP
debug3: Ignored env ALLUSERSPROFILE
debug3: Ignored env TEMP
debug3: Ignored env DriverData
debug3: Ignored env MSYSTEM
debug3: Ignored env MINGW_PREFIX
debug3: Ignored env SESSIONNAME
debug3: Ignored env ProgramFiles(x86)
debug3: Ignored env PATH
debug3: Ignored env HOMEDRIVE
debug3: Ignored env ChocolateyLastPathUpdate
debug3: Ignored env PKG_CONFIG_PATH
debug3: Ignored env INFOPATH
debug3: Ignored env HOMEPATH
debug3: Ignored env ORIGINAL_PATH
debug1: Sending command: git-upload-pack 'YYYYYY/gtfs-rt2mapify.git'
debug2: channel 0: request exec confirm 1
debug3: send packet: type 98
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 2097152 rmax 32768
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: exec request accepted on channel 0
09:14:29.063203 pkt-line.c:80 packet: clone< c3dab80029fdc1fbe9e09f2c3b52bd0237b33828 HEAD\0multi_ack thin-pack side-band side-band-64k ofs-delta shallow deepen-since deepen-not deepen-relative no-progress include-tag multi_ack_detailed allow-reachable-sha1-in-want symref=HEAD:refs/heads/master object-format=sha1 agent=git/2.32.0
09:14:29.087403 pkt-line.c:80 packet: clone< c3dab80029fdc1fbe9e09f2c3b52bd0237b33828 refs/heads/master
09:14:29.089392 pkt-line.c:80 packet: clone< 0000
09:14:29.108394 pkt-line.c:80 packet: clone> want c3dab80029fdc1fbe9e09f2c3b52bd0237b33828 multi_ack_detailed side-band-64k thin-pack ofs-delta deepen-since deepen-not agent=git/2.34.1.windows.1
09:14:29.108394 pkt-line.c:80 packet: clone> want c3dab80029fdc1fbe9e09f2c3b52bd0237b33828
09:14:29.108394 pkt-line.c:80 packet: clone> 0000
09:14:29.108394 pkt-line.c:80 packet: clone> done
debug2: channel 0: rcvd adjust 217
09:14:29.235760 pkt-line.c:80 packet: clone< NAK
09:14:29.248741 run-command.c:668 trace: run_command: git index-pack --stdin -v --fix-thin '--keep=fetch-pack 14584 on 3770K' --check-self-contained-and-connected
09:14:29.279736 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
09:14:29.289741 git.c:455 trace: built-in: git index-pack --stdin -v --fix-thin '--keep=fetch-pack 14584 on 3770K' --check-self-contained-and-connected
09:14:29.302107 pkt-line.c:80 packet: sideband< \2Enumerating objects: 4, done.
remote: Enumerating objects: 4, done.
09:14:29.306125 pkt-line.c:80 packet: sideband< \2Counting objects: 25% (1/4)\15
09:14:29.307118 pkt-line.c:80 packet: sideband< \2Counting objects: 50% (2/4)\15
09:14:29.312119 pkt-line.c:80 packet: sideband< \2Counting objects: 75% (3/4)\15
09:14:29.312119 pkt-line.c:80 packet: sideband< \2Counting objects: 100% (4/4)\15
09:14:29.312119 pkt-line.c:80 packet: sideband< \2Counting objects: 100% (4/4), done.
remote: Counting objects: 100% (4/4), done.
09:14:29.313119 pkt-line.c:80 packet: sideband< \2Compressing objects: 25% (1/4)\15
09:14:29.313119 pkt-line.c:80 packet: sideband< \2Compressing objects: 50% (2/4)\15
09:14:29.325117 pkt-line.c:80 packet: sideband< \2Compressing objects: 75% (3/4)\15Compressing objects: 100% (4/4)\15
09:14:29.325117 pkt-line.c:80 packet: sideband< \2Compressing objects: 100% (4/4), done.
remote: Compressing objects: 100% (4/4), done.
09:14:29.349029 pkt-line.c:80 packet: sideband< \2Total 4 (delta 0), reused 0 (delta 0), pack-reused 0
remote: Total 4 (delta 0), reused 0 (delta 0), pack-reused 0
09:14:29.349029 pkt-line.c:80 packet: sideband< PACK ...
Receiving objects: 100% (4/4), done.
debug3: receive packet: type 98
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
09:14:29.440181 pkt-line.c:80 packet: sideband< 0000
debug3: receive packet: type 96
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: chan_shutdown_write: channel 0: (i0 o1 sock -1 wfd 6 efd 7 [write])
debug2: channel 0: output drain -> closed
debug3: receive packet: type 97
debug2: channel 0: rcvd close
debug2: chan_shutdown_read: channel 0: (i0 o3 sock -1 wfd 5 efd 7 [write])
debug2: channel 0: input open -> closed
debug3: channel 0: will not send data after close
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug3: send packet: type 97
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
#0 client-session (t4 r0 i3/0 o3/0 e[write]/0 fd -1/-1/7 sock -1 cc -1)
debug3: send packet: type 1
Transferred: sent 3520, received 4312 bytes, in 0.7 seconds
Bytes per second: sent 5087.7, received 6232.4
debug1: Exit status 0
09:14:29.448177 run-command.c:668 trace: run_command: git rev-list --objects --stdin --not --all --quiet --alternate-refs '--progress=Checking connectivity'
09:14:29.465173 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
09:14:29.467172 git.c:455 trace: built-in: git rev-list --objects --stdin --not --all --quiet --alternate-refs '--progress=Checking connectivity'
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Norbert Csupka first of all, let me thank you once again for your support and quick feedback in helping me with in this issue.
I believe I finally figured it out and, as usual, it's always the simplest things...
- I had two separate key files (one for work, one for private pet projects) in my machine, each assigned to separate bitbucket accounts.
- I had each public key correctly added to their respective bitbucket account.
- I was performing the correct git clone command EXCEPT that in this case I was NOT specifying the account's specific key, so it was using the wrong one (the default one):
- I was actually led to think that it was reading the right key, since the initial command output was:
debug1: Authentication succeeded (publickey).
Authenticated to bitbucket.org ([104.192.141.1]:22).
- Since I was just doing a quick hack at the time, I did not take the time to investigate a little further (I know, my bad)
SOLUTION:
- I tried adding the same key to both work and personal bitbucket just to test if it was taking the wrong key previously, and it succeeded right away.
- It probably will also work if in the git clone command or .ssh/config file I explicitly specify which public key file to use for which bitbucket user (I will check this later)
Regardless, here's the full output if it helps anyone else in the future:
XXXXXX@3770K MINGW64 ~
$ GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_CURL_VERBOSE=1 GIT_SSH_COMMAND="ssh -vvv" git clone git@bitbucket.org:YYYYYY/gtfs-rt2mapify.git
09:12:21.562999 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/bin
09:12:21.564000 git.c:455 trace: built-in: git clone git@bitbucket.org:YYYYYY/gtfs-rt2mapify.git
Cloning into 'gtfs-rt2mapify'...
09:12:21.589075 run-command.c:668 trace: run_command: unset GIT_DIR; GIT_PROTOCOL=version=2 'ssh -vvv' -o SendEnv=GIT_PROTOCOL git@bitbucket.org 'git-upload-pack '\''YYYYYY/gtfs-rt2mapify.git'\'''
OpenSSH_8.8p1, OpenSSL 1.1.1l 24 Aug 2021
debug1: Reading configuration data /etc/ssh/ssh_config
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/c/Users/XXXXXX/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/c/Users/XXXXXX/.ssh/known_hosts2'
debug2: resolving "bitbucket.org" port 22
debug3: resolve_host: lookup bitbucket.org:22
debug3: ssh_connect_direct: entering
debug1: Connecting to bitbucket.org [2406:da00:ff00::3403:4be7] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::3403:4be7 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::22c5:2ef4] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::22c5:2ef4 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::22e9:9f55] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::22e9:9f55 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::22c0:3470] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::22c0:3470 port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::22cd:e0db] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::22cd:e0db port 22: Connection timed out
debug1: Connecting to bitbucket.org [2406:da00:ff00::6b17:d1f5] port 22.
debug3: set_sock_tos: set socket 4 IPV6_TCLASS 0x48
debug1: connect to address 2406:da00:ff00::6b17:d1f5 port 22: Connection timed out
debug1: Connecting to bitbucket.org [104.192.141.1] port 22.
debug3: set_sock_tos: set socket 4 IP_TOS 0x48
debug1: Connection established.
debug1: identity file /c/Users/XXXXXX/.ssh/id_rsa type 0
debug1: identity file /c/Users/XXXXXX/.ssh/id_rsa-cert type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_dsa type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_dsa-cert type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ecdsa type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ecdsa-cert type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ecdsa_sk type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ed25519 type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ed25519-cert type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ed25519_sk type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_xmss type -1
debug1: identity file /c/Users/XXXXXX/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.8
debug1: Remote protocol version 2.0, remote software version conker_3895844432 90c724de96bc
debug1: compat_banner: no match: conker_3895844432 90c724de96bc
debug2: fd 4 setting O_NONBLOCK
debug1: Authenticating to bitbucket.org:22 as 'git'
debug3: record_hostkey: found key type RSA in file /c/Users/XXXXXX/.ssh/known_hosts:1
debug3: load_hostkeys_file: loaded 1 keys from bitbucket.org
debug1: load_hostkeys: fopen /c/Users/XXXXXX/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug3: order_hostkeyalgs: prefer hostkeyalgs: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256
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,ext-info-c
debug2: host key algorithms: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,aes256-cbc,aes192-cbc
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,aes256-cbc,aes192-cbc
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-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss
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: rsa-sha2-512
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: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-rsa SHA256:zzXQOXSRBEiUtuE8AikJYKwbHaxvSc0ojez9YXaGp1A
debug3: record_hostkey: found key type RSA in file /c/Users/XXXXXX/.ssh/known_hosts:1
debug3: load_hostkeys_file: loaded 1 keys from bitbucket.org
debug1: load_hostkeys: fopen /c/Users/XXXXXX/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host 'bitbucket.org' is known and matches the RSA host key.
debug1: Found key in /c/Users/XXXXXX/.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/XXXXXX/.ssh/id_rsa RSA SHA256:+gTeuGPbJMrPrm+Zm8XT6zmTmC2bucP325dyQqSxJDo
debug1: Will attempt key: /c/Users/XXXXXX/.ssh/id_dsa
debug1: Will attempt key: /c/Users/XXXXXX/.ssh/id_ecdsa
debug1: Will attempt key: /c/Users/XXXXXX/.ssh/id_ecdsa_sk
debug1: Will attempt key: /c/Users/XXXXXX/.ssh/id_ed25519
debug1: Will attempt key: /c/Users/XXXXXX/.ssh/id_ed25519_sk
debug1: Will attempt key: /c/Users/XXXXXX/.ssh/id_xmss
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-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp521,ssh-dss-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ecdsa-sha2-nistp384,ssh-rsa-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/XXXXXX/.ssh/id_rsa RSA SHA256:+gTeuGPbJMrPrm+Zm8XT6zmTmC2bucP325dyQqSxJDo
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: /c/Users/XXXXXX/.ssh/id_rsa RSA SHA256:+gTeuGPbJMrPrm+Zm8XT6zmTmC2bucP325dyQqSxJDo
debug3: sign_and_send_pubkey: RSA SHA256:+gTeuGPbJMrPrm+Zm8XT6zmTmC2bucP325dyQqSxJDo
debug3: sign_and_send_pubkey: signing using rsa-sha2-512 SHA256:+gTeuGPbJMrPrm+Zm8XT6zmTmC2bucP325dyQqSxJDo
debug3: send packet: type 50
debug3: receive packet: type 52
Authenticated to bitbucket.org ([104.192.141.1]:22) using "publickey".
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Entering interactive session.
debug1: pledge: filesystem full
debug3: receive packet: type 91
debug2: channel_input_open_confirmation: channel 0: callback start
debug2: fd 4 setting TCP_NODELAY
debug3: set_sock_tos: set socket 4 IP_TOS 0x20
debug2: client_session2_setup: id 0
debug1: Sending environment.
debug3: Ignored env USERDOMAIN
debug3: Ignored env OS
debug3: Ignored env COMMONPROGRAMFILES
debug3: Ignored env PROCESSOR_LEVEL
debug3: Ignored env PSModulePath
debug3: Ignored env CommonProgramW6432
debug3: Ignored env CommonProgramFiles(x86)
debug3: Ignored env _
debug3: Ignored env MSYSTEM_CARCH
debug3: Ignored env DISPLAY
debug3: Ignored env HOSTNAME
debug3: Ignored env PUBLIC
debug3: Ignored env CONFIG_SITE
debug3: Ignored env GIT_TRACE_PACKET
debug3: Ignored env EXEPATH
debug3: Ignored env GIT_TRACE
debug3: Ignored env MSYSTEM_CHOST
debug3: Ignored env USERNAME
debug3: Ignored env ChocolateyInstall
debug3: Ignored env JAVA_HOME
debug3: Ignored env LOGONSERVER
debug3: Ignored env PROCESSOR_ARCHITECTURE
debug1: channel 0: setting env GIT_PROTOCOL = "version=2"
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env LOCALAPPDATA
debug3: Ignored env COMPUTERNAME
debug3: Ignored env !::
debug3: Ignored env SYSTEMDRIVE
debug3: Ignored env USERPROFILE
debug3: Ignored env PATHEXT
debug3: Ignored env SYSTEMROOT
debug3: Ignored env USERDOMAIN_ROAMINGPROFILE
debug3: Ignored env PROCESSOR_IDENTIFIER
debug3: Ignored env MINGW_PACKAGE_PREFIX
debug3: Ignored env OneDriveConsumer
debug3: Ignored env PWD
debug3: Ignored env SSH_ASKPASS
debug3: Ignored env HOME
debug3: Ignored env TMP
debug3: Ignored env LC_CTYPE
debug3: Ignored env TERM_PROGRAM
debug3: Ignored env TERM_PROGRAM_VERSION
debug3: Ignored env MSYSTEM_PREFIX
debug3: Ignored env GIT_SSH_COMMAND
debug3: Ignored env GIT_CURL_VERBOSE
debug3: Ignored env OneDrive
debug3: Ignored env PROCESSOR_REVISION
debug3: Ignored env TMPDIR
debug3: Ignored env NUMBER_OF_PROCESSORS
debug3: Ignored env ProgramW6432
debug3: Ignored env COMSPEC
debug3: Ignored env GIT_EXEC_PATH
debug3: Ignored env APPDATA
debug3: Ignored env TERM
debug3: Ignored env SHELL
debug3: Ignored env WINDIR
debug3: Ignored env MINGW_CHOST
debug3: Ignored env ProgramData
debug3: Ignored env SHLVL
debug3: Ignored env PLINK_PROTOCOL
debug3: Ignored env PROGRAMFILES
debug3: Ignored env ACLOCAL_PATH
debug3: Ignored env MANPATH
debug3: Ignored env ORIGINAL_TEMP
debug3: Ignored env ORIGINAL_TMP
debug3: Ignored env ALLUSERSPROFILE
debug3: Ignored env TEMP
debug3: Ignored env DriverData
debug3: Ignored env MSYSTEM
debug3: Ignored env MINGW_PREFIX
debug3: Ignored env SESSIONNAME
debug3: Ignored env ProgramFiles(x86)
debug3: Ignored env PATH
debug3: Ignored env HOMEDRIVE
debug3: Ignored env ChocolateyLastPathUpdate
debug3: Ignored env PKG_CONFIG_PATH
debug3: Ignored env INFOPATH
debug3: Ignored env HOMEPATH
debug3: Ignored env ORIGINAL_PATH
debug1: Sending command: git-upload-pack 'YYYYYY/gtfs-rt2mapify.git'
debug2: channel 0: request exec confirm 1
debug3: send packet: type 98
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 2097152 rmax 32768
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: exec request accepted on channel 0
09:14:29.063203 pkt-line.c:80 packet: clone< c3dab80029fdc1fbe9e09f2c3b52bd0237b33828 HEAD\0multi_ack thin-pack side-band side-band-64k ofs-delta shallow deepen-since deepen-not deepen-relative no-progress include-tag multi_ack_detailed allow-reachable-sha1-in-want symref=HEAD:refs/heads/master object-format=sha1 agent=git/2.32.0
09:14:29.087403 pkt-line.c:80 packet: clone< c3dab80029fdc1fbe9e09f2c3b52bd0237b33828 refs/heads/master
09:14:29.089392 pkt-line.c:80 packet: clone< 0000
09:14:29.108394 pkt-line.c:80 packet: clone> want c3dab80029fdc1fbe9e09f2c3b52bd0237b33828 multi_ack_detailed side-band-64k thin-pack ofs-delta deepen-since deepen-not agent=git/2.34.1.windows.1
09:14:29.108394 pkt-line.c:80 packet: clone> want c3dab80029fdc1fbe9e09f2c3b52bd0237b33828
09:14:29.108394 pkt-line.c:80 packet: clone> 0000
09:14:29.108394 pkt-line.c:80 packet: clone> done
debug2: channel 0: rcvd adjust 217
09:14:29.235760 pkt-line.c:80 packet: clone< NAK
09:14:29.248741 run-command.c:668 trace: run_command: git index-pack --stdin -v --fix-thin '--keep=fetch-pack 14584 on 3770K' --check-self-contained-and-connected
09:14:29.279736 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
09:14:29.289741 git.c:455 trace: built-in: git index-pack --stdin -v --fix-thin '--keep=fetch-pack 14584 on 3770K' --check-self-contained-and-connected
09:14:29.302107 pkt-line.c:80 packet: sideband< \2Enumerating objects: 4, done.
remote: Enumerating objects: 4, done.
09:14:29.306125 pkt-line.c:80 packet: sideband< \2Counting objects: 25% (1/4)\15
09:14:29.307118 pkt-line.c:80 packet: sideband< \2Counting objects: 50% (2/4)\15
09:14:29.312119 pkt-line.c:80 packet: sideband< \2Counting objects: 75% (3/4)\15
09:14:29.312119 pkt-line.c:80 packet: sideband< \2Counting objects: 100% (4/4)\15
09:14:29.312119 pkt-line.c:80 packet: sideband< \2Counting objects: 100% (4/4), done.
remote: Counting objects: 100% (4/4), done.
09:14:29.313119 pkt-line.c:80 packet: sideband< \2Compressing objects: 25% (1/4)\15
09:14:29.313119 pkt-line.c:80 packet: sideband< \2Compressing objects: 50% (2/4)\15
09:14:29.325117 pkt-line.c:80 packet: sideband< \2Compressing objects: 75% (3/4)\15Compressing objects: 100% (4/4)\15
09:14:29.325117 pkt-line.c:80 packet: sideband< \2Compressing objects: 100% (4/4), done.
remote: Compressing objects: 100% (4/4), done.
09:14:29.349029 pkt-line.c:80 packet: sideband< \2Total 4 (delta 0), reused 0 (delta 0), pack-reused 0
remote: Total 4 (delta 0), reused 0 (delta 0), pack-reused 0
09:14:29.349029 pkt-line.c:80 packet: sideband< PACK ...
Receiving objects: 100% (4/4), done.
debug3: receive packet: type 98
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
09:14:29.440181 pkt-line.c:80 packet: sideband< 0000
debug3: receive packet: type 96
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: chan_shutdown_write: channel 0: (i0 o1 sock -1 wfd 6 efd 7 [write])
debug2: channel 0: output drain -> closed
debug3: receive packet: type 97
debug2: channel 0: rcvd close
debug2: chan_shutdown_read: channel 0: (i0 o3 sock -1 wfd 5 efd 7 [write])
debug2: channel 0: input open -> closed
debug3: channel 0: will not send data after close
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug3: send packet: type 97
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
#0 client-session (t4 r0 i3/0 o3/0 e[write]/0 fd -1/-1/7 sock -1 cc -1)
debug3: send packet: type 1
Transferred: sent 3520, received 4312 bytes, in 0.7 seconds
Bytes per second: sent 5087.7, received 6232.4
debug1: Exit status 0
09:14:29.448177 run-command.c:668 trace: run_command: git rev-list --objects --stdin --not --all --quiet --alternate-refs '--progress=Checking connectivity'
09:14:29.465173 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
09:14:29.467172 git.c:455 trace: built-in: git rev-list --objects --stdin --not --all --quiet --alternate-refs '--progress=Checking connectivity'
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Norbert Csupka
Atlassian Team
January 23, 2022 edited Atlassian Team members are employees working across the company in a wide variety of roles.
Hi @Mário Sobral ,
You're welcome, I'm glad to hear you were able to resolve this issue :).
You're right, in case you use two different SSH keys in your computer, you need to configure your client, that with which SSH key should be used. Also, thank you for providing this solution! We appreciate it :)
Have a great day ahead Mário and stay safe!
Best Regards,
Norbert
Atlassian Bitbucket Cloud Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Was this helpful?
Thanks!
- FAQ
- Community Guidelines
- About
- Privacy policy
- Notice at Collection
- Terms of use
- © 2025 Atlassian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.