克隆Git存储库时出现SSH错误

Question

当我尝试使用SSH克隆存储库时，出现以下错误：

$ git clone ssh://[e-mail]:7999/eqt/myproject.git
Cloning into 'myproject'...
Read from socket failed: Connection reset by peer
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

SSH密钥存储在共享驱动器中，我可以在另一台也使用共享驱动器的机器上执行相同的克隆操作而没有任何问题。我的问题出现在Windows 7笔记本电脑上。

我尝试调试SSH连接并运行了以下命令：

$ ssh -Tvvv [e-mail] -p 7999
OpenSSH_6.6.1, OpenSSL 1.0.1i 6 Aug 2014
debug2: ssh_connect: needpriv 0
debug1: Connecting to stash.mydomain.com [10.105.255.156] port 7999.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/p/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /p/.ssh/id_rsa type 1
debug1: identity file /p/.ssh/id_rsa-cert type -1
debug1: identity file /p/.ssh/id_dsa type -1
debug1: identity file /p/.ssh/id_dsa-cert type -1
debug1: identity file /p/.ssh/id_ecdsa type -1
debug1: identity file /p/.ssh/id_ecdsa-cert type -1
debug1: identity file /p/.ssh/id_ed25519 type -1
debug1: identity file /p/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1
debug1: Remote protocol version 2.0, remote software version SSHD-CORE-0.9.0-ATLASSIAN-1
debug1: no match: SSHD-CORE-0.9.0-ATLASSIAN-1
debug2: fd 3 setting O_NONBLOCK
debug3: put_host_port: [stash.mydomain.com]:7999
debug3: load_hostkeys: loading entries for host "[stash.mydomain.com]:7999" from file "/p/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /p/.ssh/known_hosts:2
debug3: load_hostkeys: loaded 1 keys
debug3: order_hostkeyalgs: prefer hostkeyalgs: [e-mail],[e-mail],ssh-rsa
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: [e-mail],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-
debug2: kex_parse_kexinit: [e-mail],[e-mail],ssh-rsa,[e-mail],[e-mail],ecdsa-sha2-nistp521-cert-
stp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,[e-mail],[e-mail],[e-mail],aes128-cbc,3des-cbc,blowfish-cbc,cast128-c
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,[e-mail],[e-mail],[e-mail],aes128-cbc,3des-cbc,blowfish-cbc,cast128-c
debug2: kex_parse_kexinit: [e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],hmac-ripemd16
[e-mail],hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,[e-mail],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: [e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],hmac-ripemd16
[e-mail],hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,[e-mail],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,[e-mail],zlib
debug2: kex_parse_kexinit: none,[e-mail],zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa
debug2: kex_parse_kexinit: aes128-ctr,aes128-cbc,3des-cbc,blowfish-cbc
debug2: kex_parse_kexinit: aes128-ctr,aes128-cbc,3des-cbc,blowfish-cbc
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-md5-96,hmac-sha1-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-md5-96,hmac-sha1-96
debug2: kex_parse_kexinit: none
debug2: kex_parse_kexinit: none
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_setup: setup hmac-md5
debug1: kex: server->client aes128-ctr hmac-md5 none
debug2: mac_setup: setup hmac-md5
debug1: kex: client->server aes128-ctr hmac-md5 none
debug2: bits set: 1008/2048
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
Read from socket failed: Connection reset by peer

可能出现了什么问题？我的SSH密钥看起来很好，但似乎这个连接在某个地方被阻止了。我对SSH不够熟悉，不知道该从哪里开始查找。

- DJ180

---

远程服务器在建立安全通道时断开了连接。您需要对服务器进行故障排除。 - Kenster

服务器不可能是问题。正如我上面所说，完全相同的请求在另一台机器上是可以工作的。 - DJ180

“Connection reset by peer” 字面意思是连接的另一端关闭了它。实际上，这意味着远程端发生了“异常关闭”而不是正常关闭。程序崩溃可能会导致这种情况发生。 - Kenster

您可以通过提供用户名和密码，使用HTTPS链接克隆您的项目。使用以下命令“git clone httpslink”，并请告知是否成功克隆。 - Anjaneyulu Battula

如果在一个正常工作的客户端上运行出现错误的SSH命令并显示以上输出，你会得到什么？两个调试日志之间的差异可能很有启发性。 - Andrew Aylett

Answer 1

服务器不应该是问题所在

虽然如此，我仍然建议检查服务器sshd日志以确保（/var/log/auth.log）（也可以通过在sshd配置中增加LogLevel来帮助）

您可以尝试使用MobaXterm测试ssh连接（仅供测试），因为它有解决“connection reset by peer”问题的方法

您可以检查是否存在密码（客户端）问题

最后，您可以尝试生成一对新的公私钥，将公钥发布到服务器上，并检查问题是否仍然存在。

- VonC

---

从URL中我们可以推断出@DJ180正在使用stash，没有涉及到ssh进程，只是Java库。具体来说，是Apache SSH。 - Tomasz Szuba