git 试图推送到 BitBucket，但我收到“master conq：存储库访问被拒绝”。“致命：远端意外挂断”
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/10901102/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Trying to push to BitBucket but I get "master conq: repository access denied." "fatal: The remote end hung up unexpectedly"
提问by user1077220
I'm doing like this to push changes my bitbucket repository:
我这样做是为了推送更改我的 bitbucket 存储库：
$: git push origin
master conq: repository access denied.
fatal: The remote end hung up unexpectedly
What does this error mean and how do I fix it?
这个错误是什么意思，我该如何解决？
Debug info for bitbucket: ssh -T -v [email protected]
bitbucket 的调试信息： ssh -T -v [email protected]
OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010
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/identity-cert type -1
debug1: identity file /root/.ssh/id_rsa type 1
debug1: identity file /root/.ssh/id_rsa-cert type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: identity file /root/.ssh/id_dsa-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.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:5
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: Trying private key: /root/.ssh/identity
debug1: Offering public key: /root/.ssh/id_rsa
debug1: Remote: Forced command: conq deploykey:435246
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: read PEM private key done: type RSA
debug1: Remote: Forced command: conq deploykey:435246
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: Requesting [email protected]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
authenticated via agent_smith.
You can use git or hg to connect to Bitbucket. Shell access is disabled.
This deploy key has read access to the following repositories:
myserver/scripts: [email protected] -- [email protected]
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype [email protected] reply 0
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 2440, received 3032 bytes, in 0.0 seconds
Bytes per second: sent 58903.0, received 73194.2
debug1: Exit status 0
It's some problem that has to do with the authenticated user agent_smithabove.
这是与agent_smith上面经过身份验证的用户有关的一些问题。
采纳答案by VonC
In term of ssh access (like an ssh BitBucket repo address similar to ssh://[email protected]/accountname/reponame.git, double-check:
在 ssh 访问方面（如类似于 的 ssh BitBucket 存储库地址ssh://[email protected]/accountname/reponame.git，请仔细检查：
- the help page "Using the SSH protocol with bitbucket" and "troubleshooting SSH Issues for bitbucket"
- the case used in your address (case-sensitive)
- the nature of your ssh key (is it password protected? Did you then nadd it to the ssh-agent?)
- the number of your ssh keys (if you have several keys, you need to declare them in a
~/.ssh/configfile, or you can follow this answer)
- 帮助页面“在 bitbucket 中使用 SSH 协议”和“ bitbucket 的 SSH 问题故障排除”
- 您的地址中使用的大小写（区分大小写）
- 您的 ssh 密钥的性质（是否受密码保护？然后您是否将其添加到 ssh-agent？）
- 您的 ssh 密钥的数量（如果您有多个密钥，则需要在
~/.ssh/config文件中声明它们，或者您可以按照此答案进行操作）
Note: on Windows, then environment variable HOMEisn't defined by default. Make sure it is.
回答by Igor Parra
Check that you have write permission on repo.
检查您是否对 repo 具有写权限。
Step 4. Create a SSH config file
Using your favorite text editor, edit an existing (or create a new) ~/.ssh/config file. Add an entry to the configuration file using the following format: Host bitbucket.org IdentityFile ~/.ssh/privatekeyfile The second line is indented. That indentation (a single space) is important, so make sure you include it. The second line is the location of your private key file. If you are following along with these instructions, your file is here: ~/.ssh/id_rsa When you are done editing, your configuration looks similar to the following: Host bitbucket.org IdentityFile ~/.ssh/id_rsa Save and close the file. Restart the GitBash terminal.
步骤 4. 创建一个 SSH 配置文件
Using your favorite text editor, edit an existing (or create a new) ~/.ssh/config file. Add an entry to the configuration file using the following format: Host bitbucket.org IdentityFile ~/.ssh/privatekeyfile The second line is indented. That indentation (a single space) is important, so make sure you include it. The second line is the location of your private key file. If you are following along with these instructions, your file is here: ~/.ssh/id_rsa When you are done editing, your configuration looks similar to the following: Host bitbucket.org IdentityFile ~/.ssh/id_rsa Save and close the file. Restart the GitBash terminal.
回答by Eric Leschinski
This git error:
这个 git 错误：
$: git pull
master conq: repository access denied.
fatal: The remote end hung up unexpectedly
Remedied by:
补救措施：
- Blow away the public and private ssh keys in your ~/.ssh directory
- Create new ssh keys.
- Log in to bitbucket for your repository.
- Delete the old ssh key from bitbucket.
- Add your new ssh key to bitbucket.
- Try it again, then ssh negotiates with bitbucket with the correct user.
- 吹掉 ~/.ssh 目录中的公钥和私钥
- 创建新的 ssh 密钥。
- 登录到您的存储库的 bitbucket。
- 从 bitbucket 中删除旧的 ssh 密钥。
- 将新的 ssh 密钥添加到 bitbucket。
- 再试一次，然后 ssh 与正确的用户协商 bitbucket。
What caused this?
这是什么原因造成的？
The credentials that ssh on the client machine was using to negotiate with bitbucket had changed in such a way as to cause bitbucket to think that this is an unauthorized user.
客户端计算机上 ssh 用于与 bitbucket 协商的凭据已更改，导致 bitbucket 认为这是未经授权的用户。
回答by Daniel
If you are using Mac OSX or Linux what worked for me is ensuring that ssh-agent is loaded and running with my keys.
如果您使用的是 Mac OSX 或 Linux，那么对我有用的是确保 ssh-agent 已加载并使用我的密钥运行。
$ ps -e | grep [s]sh-agent
9060 ?? 0:00.28 /usr/bin/ssh-agent -l
checks to see if the agent is running. You should see something like the above results. If you do not see the above results, you can type
检查代理是否正在运行。您应该会看到类似上述结果的内容。如果你没有看到上面的结果，你可以输入
$ eval ssh-agent $SHELL
to start the ssh-agent by hand. Next you want to check to see if the keys are running. Type
手动启动 ssh-agent。接下来，您要检查密钥是否正在运行。类型
$ ssh-add -l
2048 68:ef:d6:1e:4b:3b:a3:52:6f:b0:c3:4b:da:e8:d1:9f /c/Documents and Settings/manthony/.ssh/personalid (RSA)
and you should see the above results. If you don't you can type
你应该会看到上面的结果。如果你不这样做，你可以输入
$ ssh-add ~/.ssh/workid
where workidis the name of your private keyset you generated.
workid您生成的私钥集的名称在哪里。
taken directly from this link: Configure multiple SSH identities for GitBash, Mac OSX, & Linux
