2015-10-15 90 views
1

我在Windows環境中通過git bash運行ssh。我擁有了一切工作正常,但現在(幾天後),當我嘗試連接到到位桶我得到的消息:ssh-exchange_identification: read: connection reset by peer.ssh - '通過同級重置連接' - windows

完整的日誌看起來是這樣的:

$ ssh -Tvvv -p 443 [email protected] 
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)我可以證實,我公司未檢查和阻止PA通過端口443打成小包(雖然他們阻塞端口22這就是爲什麼我要在443開始)

2)我可以證實這個問題是不是到位桶服務器 - 其他人在我的球隊可以得到在就好了

如上所述,這是之前的工作就好了。我清除了所有的鑰匙,並重新開始,但無濟於事。

幫助!我一直在敲打我在這頭,現在看兩天......

更新 - 增加了更多的詳細日誌

+0

1)請張貼詳細的日誌與'-vvv' 2)檢查什麼是客戶端配置文件的內容。 – Jakuje

回答

0

好了,這是錯誤的邏輯去思考,只是因爲我的團隊的其他成員有訪問,沒有被阻止。我是/我。

+0

你好,那你是怎麼知道的? –