成功克隆我的回购从heroku和添加另一个远程

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

在运行line(3)或使用SourceTree后,我仍然得到这个错误

conq: repository access denied. access via a deployment key is read-only.

首先,我不明白这条信息在实践中意味着什么。这就是耻辱。

我确实创建了ssh密钥对并添加到heroku:

ssh-keygen -t rsa 
heroku keys:add ./id_rsa.pub 

我还在BitBucket的部署密钥部分添加了我的密钥。但我一定遗漏了什么。这个问题不是出于懒惰,我一直在阅读各种文档,包括BitBuckets指南。但它仍然没有解决这个问题。

这篇文章是有关我可以导入我的heroku git回购到bitbucket ?以及如何?

额外的事实:

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

看起来一切都很好。


当前回答

两步工艺才能推拉 Step1:生成ssh密钥(公钥和私钥)在mac2:将私钥放在mac中,公钥放在git网站中,下面的详细步骤是针对mac用户的

步骤1:生成密钥

(确保你安装了git)https://git-scm.com/download/mac 打开终端,输入ssh-keygen,这将提示您输入密钥的存储位置,您可以输入/Users/[machinename]/.ssh/[keyname] 接下来,它将要求密码短语,你可以通过按enter键让它空白,或者输入一些关键字,在下一个提示再次输入 这将为您创建两个密钥,私有和公共,名称[keyname]和[keyname].pub

第二步:将键推到适当的位置[mac和远程帐户,即Github, bitbucket, gitlab等]

输入ssh-add -K ~/。在终端上Ssh /[keyname]添加您的私钥到MAC 输入pbcopy < ~/.ssh/[keyname]。Pub将公钥复制到剪贴板 在你各自的git网站上打开账户设置,然后去添加密钥,在那里粘贴上面复制的公钥

完成,现在你可以推拉了。

其他回答

我的第一个困惑是在BitBucket中具体在哪里设置SSH密钥。

我是BitBucket的新手,我正在设置一个部署密钥,只提供读访问。

所以确保你在BitBucket帐户设置中设置了你的rsa pub密钥。

点击你的比特桶头像,选择比特桶设置(管理账户)。在那里,您将能够设置SSH密钥。

我只是删除了部署键,我现在不需要任何。这个方法奏效了

有时它不起作用,因为你手动在~/.ssh/config中为bitbucket设置了另一个键。

现在SSH选项在安全设置下

点击你的头像——> Bitbucket Settings——> SSH Key——> Add Key

粘贴公钥

当我试图使用部署键时发生了这种情况,因为这正是我想要的。

我可以通过ssh -T git@bitbucket.org连接,它会告诉我,我可以读取我想要的存储库,但git克隆会失败。

清除~/。Ssh /known_hosts,通过Ssh -keygen生成一个新密钥,将新密钥添加到bitbucket,并重新尝试为我修复它。

如果您打算在管理帐户SSH密钥下添加相同的密钥,则必须先删除部署密钥。