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

Push not permitted error from eclipse

Jahan Kadhar
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 11, 2023

We are not able to push from eclipse to bitbucket. It used to work earlier. Now none of the users are able to push code from eclipse. We get the error "push not permitted"

1 answer

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

Hello @Jahan Kadhar 

and thank you for reaching out to Community!

That error is usually related to authentication issues. Could you confirm if you have eclipse configured to use SSH or HTTPS protocol when pushing to the repository? 

Based on the protocol being used, I would suggest the following : 

  • For HTTPS ( https://USERNAME@bitbucket.org/WORKSPACE/REPOSITORY.git ), make sure you are authenticating using : 
    • username: you can find the username of your account by navigating to Your personal bitbucket account settings. 
    • app password : a token to authenticate git requests over HTTPS. If you haven't already, you can create a new app password
  • For SSH (the bitbucket URL will look like git clone git@bitbucket.org:WORKSPACE/REPOSITORY.git), make sure your public key was added to a user profile that has access to the repository. You can use the command 
    ssh -Tvvv git@bitbucket.org
    in the machine where you are facing the issue. This command will test the SSH authentication to Bitbucket.

Thank you, @Jahan Kadhar !
Patrik S

Jahan Kadhar
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 12, 2023

Hi,

         my eclipse is configured to use SSH. The bitbucket url in my eclipse looks like below. 

git@bitbucket.org:WORKSPACE/REPOSITORY.git

          All the team members are using the same SSH mechanism. We were able to pull and push to multiple repositories using this. However in the last few weeks only pull is working and push is not working. When we push there is an error that says "Not Permitted". I have also verified that permissions for the users have also beed set to "write". Infact I am pushing as an admin and still same issue.

          I went through some of the documentation which mentioned that going forward we will need a Repository Access Token created which will need to be used for push. I was able to create the token but I dont see a way to add this token to the eclipse while pushing. This token seems to be specific to a repository. But when I push from eclipse it only asks for password and not for a token. All the examples I see on the internet are using https and there you can see an option for token. Not sure how I can add the token while pushing a specific repository from the eclipse.

         When I try the command "ssh -Tvvv git@bitbucket.org" I see a lot of logs as shown below. I am sure it is connecting to the repository because I am able to pull code. It is only with push that there is a problem. 

 

OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
debug3: Failed to open file:C:/Users/XXXXX/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolving "bitbucket.org" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to bitbucket.org [104.192.141.1] port 22.
debug1: Connection established.
debug1: identity file C:\\Users\\XXXXX/.ssh/id_rsa type 0
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_rsa-cert error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_rsa-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_rsa-cert type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_dsa error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_dsa.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_dsa type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_dsa-cert error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_dsa-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_dsa-cert type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ecdsa error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ecdsa.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_ecdsa type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ecdsa-cert error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ecdsa-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_ecdsa-cert type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ed25519 error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ed25519.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_ed25519 type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ed25519-cert error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ed25519-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_ed25519-cert type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_xmss error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_xmss.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_xmss type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_xmss-cert error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_xmss-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_7.7
debug1: Remote protocol version 2.0, remote software version conker_5933d25285 426e976cb448
debug1: no match: conker_5933d25285 426e976cb448
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to bitbucket.org:22 as 'git'
debug3: hostkeys_foreach: reading file "C:\\Users\\XXXXX/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\XXXXX/.ssh/known_hosts:1
debug3: record_hostkey: found key type RSA in file C:\\Users\\XXXXX/.ssh/known_hosts:2
debug3: load_hostkeys: loaded 2 keys from bitbucket.org
debug3: Failed to open file:C:/Users/XXXXX/.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,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256,ssh-rsa
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-group-exchange-sha1,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,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-ed25519-cert-v01@openssh.com,ssh-ed25519
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
debug2: compression stoc: none
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\\XXXXX/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\XXXXX/.ssh/known_hosts:1
debug3: record_hostkey: found key type RSA in file C:\\Users\\XXXXX/.ssh/known_hosts:2
debug3: load_hostkeys: loaded 2 keys from bitbucket.org
debug3: Failed to open file:C:/Users/XXXXX/.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\\XXXXX/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\XXXXX/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from 104.192.141.1
debug3: Failed to open file:C:/Users/XXXXX/.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\\XXXXX/.ssh/known_hosts:1
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey 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 after 134217728 blocks
debug2: key: C:\\Users\\XXXXX/.ssh/id_rsa (000001FC0D45A030), agent
debug2: key: C:\\Users\\XXXXX/.ssh/id_dsa (0000000000000000)
debug2: key: C:\\Users\\XXXXX/.ssh/id_ecdsa (0000000000000000)
debug2: key: C:\\Users\\XXXXX/.ssh/id_ed25519 (0000000000000000)
debug2: key: C:\\Users\\XXXXX/.ssh/id_xmss (0000000000000000)
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512,ecdsa-sha2-nistp521,ssh-dss-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ssh-rsa-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: RSA SHA256:gG7b+T++/D6YBKjWyW/4YU+tAyp2Cr/vtGOT0UTTMk0 C:\\Users\\XXXXX/.ssh/id_rsa
debug3: send_pubkey_test
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: pkalg rsa-sha2-512 blen 279
debug2: input_userauth_pk_ok: fp SHA256:gG7b+T++/D6YBKjWyW/4YU+tAyp2Cr/vtGOT0UTTMk0
debug3: sign_and_send_pubkey: RSA SHA256:gG7b+T++/D6YBKjWyW/4YU+tAyp2Cr/vtGOT0UTTMk0
warning: agent returned different signature type ssh-rsa (expected 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
debug1: console supports the ansi parsing
debug3: Successfully set console output code page from:437 to 65001
debug3: Successfully set console input code page from:437 to 65001
debug3: receive packet: type 80
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
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 pty-req confirm 1
debug3: send packet: type 98
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
debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
debug3: send packet: type 98
debug3: receive packet: type 100
debug2: channel_input_status_confirm: type 100 id 0
PTY allocation request failed on channel 0
debug3: Successfully set console output code page from 65001 to 437
debug3: Successfully set console input code page from 65001 to 437

C:\Users\XXXXX>ssh -Tvvv git@bitbucket.org
OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
debug3: Failed to open file:C:/Users/XXXXX/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolving "bitbucket.org" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to bitbucket.org [104.192.141.1] port 22.
debug1: Connection established.
debug1: identity file C:\\Users\\XXXXX/.ssh/id_rsa type 0
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_rsa-cert error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_rsa-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_rsa-cert type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_dsa error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_dsa.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_dsa type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_dsa-cert error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_dsa-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_dsa-cert type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ecdsa error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ecdsa.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_ecdsa type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ecdsa-cert error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ecdsa-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_ecdsa-cert type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ed25519 error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ed25519.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_ed25519 type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ed25519-cert error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_ed25519-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_ed25519-cert type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_xmss error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_xmss.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_xmss type -1
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_xmss-cert error:2
debug3: Failed to open file:C:/Users/XXXXX/.ssh/id_xmss-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\XXXXX/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_7.7
debug1: Remote protocol version 2.0, remote software version conker_7b6fdbf7c0 4bc7087324ee
debug1: no match: conker_7b6fdbf7c0 4bc7087324ee
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to bitbucket.org:22 as 'git'
debug3: hostkeys_foreach: reading file "C:\\Users\\XXXXX/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\XXXXX/.ssh/known_hosts:1
debug3: record_hostkey: found key type RSA in file C:\\Users\\XXXXX/.ssh/known_hosts:2
debug3: load_hostkeys: loaded 2 keys from bitbucket.org
debug3: Failed to open file:C:/Users/XXXXX/.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,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256,ssh-rsa
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-group-exchange-sha1,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,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-ed25519-cert-v01@openssh.com,ssh-ed25519
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
debug2: compression stoc: none
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\\XXXXX/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\XXXXX/.ssh/known_hosts:1
debug3: record_hostkey: found key type RSA in file C:\\Users\\XXXXX/.ssh/known_hosts:2
debug3: load_hostkeys: loaded 2 keys from bitbucket.org
debug3: Failed to open file:C:/Users/XXXXX/.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\\XXXXX/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\XXXXX/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from 104.192.141.1
debug3: Failed to open file:C:/Users/XXXXX/.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\\XXXXX/.ssh/known_hosts:1
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey 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 after 134217728 blocks
debug2: key: C:\\Users\\XXXXX/.ssh/id_rsa (00000229AE11B9C0), agent
debug2: key: C:\\Users\\XXXXX/.ssh/id_dsa (0000000000000000)
debug2: key: C:\\Users\\XXXXX/.ssh/id_ecdsa (0000000000000000)
debug2: key: C:\\Users\\XXXXX/.ssh/id_ed25519 (0000000000000000)
debug2: key: C:\\Users\\XXXXX/.ssh/id_xmss (0000000000000000)
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-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-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: RSA SHA256:gG7b+T++/D6YBKjWyW/4YU+tAyp2Cr/vtGOT0UTTMk0 C:\\Users\\XXXXX/.ssh/id_rsa
debug3: send_pubkey_test
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: pkalg rsa-sha2-512 blen 279
debug2: input_userauth_pk_ok: fp SHA256:gG7b+T++/D6YBKjWyW/4YU+tAyp2Cr/vtGOT0UTTMk0
debug3: sign_and_send_pubkey: RSA SHA256:gG7b+T++/D6YBKjWyW/4YU+tAyp2Cr/vtGOT0UTTMk0
warning: agent returned different signature type ssh-rsa (expected 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 80
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
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: close_read
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
debug3: channel 0: will not send data after close
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
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
s 1

Patrik S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 13, 2023

Thanks for sharing the results @Jahan Kadhar ,

I'm not really sure about the eclipse particular configuration, but when it comes to the SSH connection, the logs say you are successfully authenticated with Bitbucket Cloud using the SSH key.

Since you mentioned this issue affects only pull and push, could you confirm where this SSH was added?

I ask this because depending on where in Bitbucket you added the SSH key, it will give different levels of access.

SSH keys added to a user's bitbucket account will have the same permission to repositories that the user does.

On the other hand, access keys added in the project or repository level have only read access. Workspace access keys have read and write access. You can learn more on Difference between Repository, Project and Workspace Access keys .

Thank you, @Jahan Kadhar !

Patrik S

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events