我在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 except 完全相同
1）我可以确认我的公司没有通过端口443检查和阻止数据包（虽然他们阻止了端口22，这就是为什么我要开始使用443）
2）我可以确认问题不在于bitbucket服务器 - 我团队中的其他人可以很好地进入
如上所述，这之前工作得很好 . 我擦掉了所有的钥匙并重新开始但无济于事 .
救命！我已经在这两天敲打了我的脑袋......
Updated - 添加了更详细的日志
1 回答
好的，所以认为这是错误的逻辑，因为我的团队中的其他成员都有访问 I 没有被阻止 . 我是/我 .