1. Bitbucket
  2. Public Issue Tracker
  3. master

Issues

Issue #9759 resolved

Shell access is disabled !

funky funky
created an issue

Hi,

I have problem i can not push to my new repository in bitbucket. I did all of this instruction https://confluence.atlassian.com/pages/viewpage.action?pageId=270827678

But when i use this commands:

git remote add origin git@bitbucket.org:RyanHeung/bebi.vn.git
git push -u origin --all

and problem:

conq: repository access denied. access via a deployment key is read-only. fatal: Could not read from remote repository.

Then i run debug the result is:

root@server [/home/bebi/public_html]# ssh -v git@bitbucket.org
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to bitbucket.org [131.103.20.167] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type 1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'bitbucket.org' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:7
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /root/.ssh/id_rsa
debug1: Remote: Forced command: conq deploykey:197002
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: Remote: Forced command: conq deploykey:197002
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
authenticated via a deploy key.

                               You can use git or hg to connect to Bitbucket. Shell access is disabled.
                     debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
Connection to bitbucket.org closed.
debug1: Transferred: stdin 0, stdout 0, stderr 37 bytes in 0.5 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 75.4
debug1: Exit status 0

So what is my problem ? please help me !

Comments (13)

  1. Chris Somme staff

    That would normally happen if you tried to push to a repository using an ssh key that you had configured to be used as a deployment key. Have you configured a deployment key for one of your repositories?

  2. funky funky reporter

    Yes i did ! I configured a deployment key for my repository. I copied from my id_rsa.pub in my server. I did the same for my repositories in another server, all of them are ok but in this server i dont know what happen.

  3. Chris Somme staff

    You're attempting to use a deployment key to push changes back to Bitbucket. A deployment key is intended to be used in places where you want to retrieve your code from Bitbucket but not update that code. You're getting an error when you attempt to push.

    If you want to push code back up, you'll have to use an SSH key associated with a user account, not a deployment key.

  4. Log in to comment