Databases
StackOverflow2013
Postsdbo
PORepository access denied. access via a deployment key is read-only
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORepository access denied. access via a deployment key is read-only
    primarykey
    data
    text
    <p>After successfully cloning my repo from heroku and added another remote</p> <pre><code>1/ git clone git@heroku.com:[APP].git 2/ git remote add bitbucket ssh://git@bitbucket.org/[ACCOUNT]/[REPO].git 3/ git push bitbucket master </code></pre> <p>I am still getting this error after running line (3) or using SourceTree</p> <pre><code>conq: repository access denied. access via a deployment key is read-only. </code></pre> <p>First I don't understand what this message means in practice. And that's shame.</p> <p>I did create ssh key pair and added to heroku :</p> <pre><code>ssh-keygen -t rsa heroku keys:add ./id_rsa.pub </code></pre> <p>I also added my key in deployment keys section in BitBucket. But I must be missing something. This question is not out of laziness, I have been reading various docs including BitBuckets guides. But it still don't get around this issue.</p> <p>This post is related to <a href="https://stackoverflow.com/questions/13300068/can-i-import-my-heroku-git-repo-into-bitbuket-and-how/">Can I import my heroku git repo into bitbuket? and how?</a> </p> <p>ADDITIONAL FACTS:</p> <pre><code>ssh -T hg@bitbucket.org conq: authenticated via a deploy key. You can use git or hg to connect to Bitbucket. Shell access is disabled. $ ssh -v git@bitbucket.org OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011 debug1: Reading configuration data /Users/joel/.ssh/config debug1: Applying options for bitbucket.org debug1: Reading configuration data /etc/ssh_config debug1: Applying options for * debug1: Connecting to bitbucket.org [207.223.240.181] port 22. debug1: Connection established. debug1: identity file /Users/joel/.ssh/id_rsa type 1 debug1: identity file /Users/joel/.ssh/id_rsa-cert type -1 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_5.6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-&gt;client aes128-ctr hmac-md5 none debug1: kex: client-&gt;server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024&lt;1024&lt;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 /Users/joel/.ssh/known_hosts:5 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server 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 RSA public key: /Users/joel/.ssh/id_rsa debug1: Remote: Forced command: conq deploykey:13907 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 279 debug1: read PEM private key done: type RSA debug1: Remote: Forced command: conq deploykey:13907 debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug1: Authentication succeeded (publickey). Authenticated to bitbucket.org ([207.223.240.181]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessions@openssh.com debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LC_CTYPE = UTF-8 PTY allocation request failed on channel 0 </code></pre> <p>Looks like all is fine.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USzabumba
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORepository access denied. access via a deployment key is read-only
      1. USPhilippe Y. Rigovanov
      1. VTFavorite
    2. VO
      singulars
      1. PORepository access denied. access via a deployment key is read-only
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORepository access denied. access via a deployment key is read-only
      1. USted.strauss
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload