我在windows环境中通过git bash运行ssh。我有一切正常,但现在(几天后),当我尝试连接到bitbucket时,我收到消息:ssh-exchange_identification: read: connection reset by peer.
完整日志如下所示:
$ ssh -Tvvv -p 443 git@altssh.bitbucket.org
OpenSSH_6.6.1, OpenSSL 1.0.1i 6 Aug 2014
debug2: ssh_connect: needpriv 0
debug1: Connecting to altssh.bitbucket.org [131.103.20.174] port 443.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/c/Documents and Settings/xxx/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /c/Documents and Settings/xxx/.ssh/id_rsa type 1
debug1: identity file /c/Documents and Settings/xxx/.ssh/id_rsa-cert type -1
debug1: identity file /c/Documents and Settings/xxx/.ssh/id_dsa type -1
debug1: identity file /c/Documents and Settings/xxx/.ssh/id_dsa-cert type -1
debug1: identity file /c/Documents and Settings/xxx/.ssh/id_ecdsa type -1
debug1: identity file /c/Documents and Settings/xxx/.ssh/id_ecdsa-cert type -1
debug1: identity file /c/Documents and Settings/xxx/.ssh/id_ed25519 type -1
debug1: identity file /c/Documents and Settings/xxx/.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
ssh_exchange_identification:读取:通过对等方重置连接
我的问题与bibucket ssh_exchange_identification: read: Connection reset by peer 完全相同,只有
1)我可以确认我的公司没有通过端口443检查和阻止数据包(虽然他们 阻塞端口22,这就是我开始使用443的原因)
2)我可以确认问题不在于bitbucket服务器 - 我团队中的其他人可以很好地进入
如上所述,此前工作正常。我擦掉了所有的钥匙并重新开始但无济于事。
帮助!我已经在这两天坚持不懈了......
已更新 - 添加了更详细的日志
答案 0 :(得分:0)
好的,所以认为仅仅因为我团队中的其他成员有权访问 我 并未被阻止,这是错误的逻辑。我/是。