1. Bitbucket Website
  2. Public Issue Tracker
  3. master

Issues

Issue #491 resolved

Problem with SSH access

Jason Mayfield
created an issue

Yesterday, everything was working fine. Today, I cannot pull via SSH. Absolutely nothing has changed from then to now.

Input: {{{ $ hg pull -v }}}

Output: {{{ running ssh -C hg@bb "hg -R <repo name removed> serve --stdio" remote: Connection closed by 75.101.141.151 abort: no suitable response from remote hg! }}}

Comments (23)

  1. Jesper Nøhr

    Can you try that again? We had a few other people experience this as well - it was due to a malformed key entered by another user, which incidentally broke any key entered after it (like yours.)

  2. Lars Yencken
    • changed status to open

    Same thing happening to me today. Happens for all my repositories, but luckily it's just ssh broken. Https access still works fine.

    $ hg pull -v
    running ssh hg@bitbucket.org "hg -R <snip> serve --stdio"
    remote: Connection closed by 75.101.141.151
    

    Perhaps another malformed key?

  3. Peter Aronoff

    I'm unable to clone using ssh. HTTPS works fine, but I've tried on two machines (both OSX 10.5.8, if it matters). Here's the verbose output from my work machine:

    hektor mercurial $ hg clone ssh://hg@bitbucket.org/telemachus/practice/ --ssh 'ssh -v'
    running ssh -v hg@bitbucket.org "hg -R telemachus/practice/ serve --stdio"
    remote: OpenSSH_5.2p1, OpenSSL 0.9.7l 28 Sep 2006
    remote: debug1: Reading configuration data /Users/hektor/.ssh/config
    remote: debug1: Reading configuration data /etc/ssh_config
    remote: debug1: Connecting to bitbucket.org [75.101.141.151] port 22.
    remote: debug1: Connection established.
    remote: debug1: identity file /Users/hektor/.ssh/identity type -1
    remote: debug1: identity file /Users/hektor/.ssh/id_rsa type 1
    remote: debug1: identity file /Users/hektor/.ssh/id_dsa type -1
    remote: debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-5
    remote: debug1: match: OpenSSH_5.1p1 Debian-5 pat OpenSSH*
    remote: debug1: Enabling compatibility mode for protocol 2.0
    remote: debug1: Local version string SSH-2.0-OpenSSH_5.2
    remote: debug1: SSH2_MSG_KEXINIT sent
    remote: debug1: SSH2_MSG_KEXINIT received
    remote: debug1: kex: server->client aes128-ctr hmac-md5 none
    remote: debug1: kex: client->server aes128-ctr hmac-md5 none
    remote: debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
    remote: debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
    remote: debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
    remote: debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
    remote: debug1: Host 'bitbucket.org' is known and matches the RSA host key.
    remote: debug1: Found key in /Users/hektor/.ssh/known_hosts:23
    remote: debug1: ssh_rsa_verify: signature correct
    remote: debug1: SSH2_MSG_NEWKEYS sent
    remote: debug1: expecting SSH2_MSG_NEWKEYS
    remote: debug1: SSH2_MSG_NEWKEYS received
    remote: debug1: SSH2_MSG_SERVICE_REQUEST sent
    remote: debug1: SSH2_MSG_SERVICE_ACCEPT received
    remote: debug1: Authentications that can continue: publickey
    remote: debug1: Next authentication method: publickey
    remote: debug1: Trying private key: /Users/hektor/.ssh/identity
    remote: debug1: Offering public key: /Users/hektor/.ssh/id_rsa
    remote: debug1: Authentications that can continue: publickey
    remote: debug1: Trying private key: /Users/hektor/.ssh/id_dsa
    remote: debug1: No more authentication methods to try.
    remote: Permission denied (publickey).
    abort: no suitable response from remote hg!
    

    The public keys at my end work in other contexts (remote logins & Github for example), so I'm unsure what else to try here.

  4. Anonymous

    Same issue for me. Last sunday all ok, and on monday after scheduled downtime (Aug 30) ssh pull/push fails with "permission denied". Https work ok though.

  5. vstrakh
    • changed status to open

    I have exactly same expirience. ssh fails with permission denied, and https works ok. Broken after maintenance downtime.

    $ hg pull -uv
    running ssh -C hg@bitbucket.org "hg -R <hidden> serve --stdio"
    remote: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
    abort: no suitable response from remote hg!
    

    Nothing changed from yesterday on my side. I even removed and uploaded again public key. Doesn't help.

  6. Michael Granger

    [+1] Same situation for me: I can access my repos through HTTPS, but not ssh:

    $ hg pull -u --ssh 'ssh -v'
    remote: OpenSSH_5.2p1, OpenSSL 0.9.8l 5 Nov 2009
    [...]
    remote: debug1: Authentication succeeded (publickey).
    remote: debug1: channel 0: new [client-session]
    remote: debug1: Requesting no-more-sessions@openssh.com
    remote: debug1: Entering interactive session.
    remote: debug1: Requesting authentication agent forwarding.
    remote: debug1: Sending command: hg -R ged/ruby-pg serve --stdio
    remote: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
    remote: debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
    remote: debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
    remote: debug1: channel 0: free: client-session, nchannels 1
    remote: debug1: fd 0 clearing O_NONBLOCK
    remote: debug1: fd 1 clearing O_NONBLOCK
    remote: debug1: fd 2 clearing O_NONBLOCK
    remote: Transferred: sent 1672, received 2616 bytes, in 0.6 seconds
    remote: Bytes per second: sent 2754.6, received 4309.8
    remote: debug1: Exit status 0
    remote: debug1: compress outgoing: raw data 261, compressed 162, factor 0.62
    remote: debug1: compress incoming: raw data 165, compressed 137, factor 0.83
    abort: no suitable response from remote hg!
    
  7. tyoc213
    • changed status to open

    Im having same problem now with a newly created ssh ssha key.

    running ssh -C tyoc213@bitbucket.org "hg -R tyoc213/... serve --stdio"

    sending hello command

    sending between command

    remote: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

    abort: no suitable response from remote hg!

  8. Log in to comment