问题描述
从 heroku 成功克隆我的 repo 并添加另一个远程后
1/git clone git@heroku.com:[APP].git2/git远程添加bitbucket ssh://git@bitbucket.org/[ACCOUNT]/[REPO].git3/git push bitbucket master
在运行第 (3) 行或使用 SourceTree 后,我仍然收到此错误
conq:存储库访问被拒绝.通过部署密钥访问是只读的.
首先我不明白这条消息在实践中意味着什么.这是耻辱.
我确实创建了 ssh 密钥对并添加到 heroku 中:
ssh-keygen -t rsaheroku 键:添加 ./id_rsa.pub
我还在 BitBucket 的部署密钥部分添加了我的密钥.但我一定错过了什么.这个问题并非出于懒惰,我一直在阅读各种文档,包括 BitBuckets 指南.但它仍然没有解决这个问题.
这篇文章与
After successfully cloning my repo from heroku and added another remote
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
I am still getting this error after running line (3) or using SourceTree
conq: repository access denied. access via a deployment key is read-only.
First I don't understand what this message means in practice. And that's shame.
I did create ssh key pair and added to heroku :
ssh-keygen -t rsa
heroku keys:add ./id_rsa.pub
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.
This post is related to Can I import my heroku git repo into bitbuket? and how?
ADDITIONAL FACTS:
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->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 /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
Looks like all is fine.
First confusion on my side was about where exactly to set SSH Keys in BitBucket.
I am new to BitBucket and I was setting a Deployment Key which gives read-access only.
So make sure you are setting your rsa pub key
in your BitBucket Account Settings.
Click your BitBucket avatar and select Bitbucket Settings(). There you'll be able to set SSH Keys.
I simply deleted the Deployment Key, I don't need any for now. And it worked
这篇关于存储库访问被拒绝.通过部署密钥访问是只读的的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!