使用 AWS EC2 时，我有一个运行 Ubuntu 16 的 m5.large 实例，它有一个常规 IP 地址。我通过编辑机器的 /etc/sshd/config 添加了有限访问的 sftp 用户，这很好用。然后，我向盒子添加了一个弹性 IP 地址，现在每当我尝试访问盒子时，都会收到管道损坏的错误。我尝试通过 AMI 快照启动相同的实例来复制该问题，并尝试清除 openssh 并通过用户数据框重新安装它，但第二个实例也收到相同的错误。Web 服务器工作正常，我只是无法从任何机器访问它。它似乎可以通过私钥/公钥对正常登录，但最后一步结束了所有连接。实例 ID 是 i-03bdf244d7b1c98e6，我创建的副本是 i-04f02a5ec0c209a44。
这是我得到的详细输出：
ssh [email protected] -i ~/.ssh/xxxxxxx.pem -vvv
OpenSSH_7.9p1, LibreSSL 2.7.3
debug1: Reading configuration data /Users/xxxxxxx/.ssh/config
debug1: /Users/xxxxxxxx/.ssh/config line 1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 48: Applying options for *
debug2: resolve_canonicalize: hostname 34.225.96.92 is address
debug2: ssh_connect_direct
debug1: Connecting to 34.225.96.92 [34.225.96.92] port 22.
debug1: Connection established.
debug1: identity file /Users/xxxxxxx/.ssh/xxxxxxx.pem type -1
debug1: identity file /Users/xxxxxxx/.ssh/xxxxxxx.pem-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.9
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2p2 Ubuntu-4ubuntu2.7
debug1: match: OpenSSH_7.2p2 Ubuntu-4ubuntu2.7 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 34.225.96.92:22 as 'ubuntu'
debug3: hostkeys_foreach: reading file "/Users/xxxxxxx/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /Users/xxxxxxx/.ssh/known_hosts:66
debug3: load_hostkeys: loaded 1 keys from 34.225.96.92
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],[email protected],[email protected],ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,[email protected],zlib
debug2: compression stoc: none,[email protected],zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,[email protected]
debug2: compression stoc: none,[email protected]
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: [email protected]
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:ojf1ko9ntOaWR59QrGDg04Ft7uGLCiK7fSks7D91NUY
debug3: hostkeys_foreach: reading file "/Users/xxxxxxx/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /Users/xxxxxxx/.ssh/known_hosts:66
debug3: load_hostkeys: loaded 1 keys from 34.225.96.92
debug1: Host '34.225.96.92' is known and matches the ECDSA host key.
debug1: Found key in /Users/amatusko/.ssh/known_hosts:66
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug1: Will attempt key: /Users/xxxxxxx/.ssh/xxxxxxx.pem RSA SHA256:US/RaCxmNUMq224OF+MQ4g5Swdh4YEnU3v3mX9WRcPU agent
debug1: Will attempt key: /Users/xxxxxxx/.ssh/blogsftp RSA SHA256:lzv9cpAmHg8GOZBZ4CR7GsuikzEXC3WzjuQbi6Sp+jA agent
debug1: Will attempt key: /Users/xxxxxxx/.ssh/xxxxxxx explicit
debug2: pubkey_prepare: done
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /Users/xxxxxxx/.ssh/xxxxxxx.pem RSA SHA256:US/RaCxmNUMq224OF+MQ4g5Swdh4YEnU3v3mX9WRcPU agent
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: /Users/xxxxxxx/.ssh/xxxxxxx.pem RSA SHA256:US/RaCxmNUMq224OF+MQ4g5Swdh4YEnU3v3mX9WRcPU agent
debug3: sign_and_send_pubkey: RSA SHA256:US/RaCxmNUMq224OF+MQ4g5Swdh4YEnU3v3mX9WRcPU
debug3: sign_and_send_pubkey: signing using rsa-sha2-512
debug3: send packet: type 50
debug3: receive packet: type 52
debug1: Authentication succeeded (publickey).
Authenticated to 34.225.96.92 ([34.225.96.92]:22).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Requesting [email protected]
debug3: send packet: type 80
debug1: Entering interactive session.
debug1: pledge: network
debug3: send packet: type 1
packet_write_wait: Connection to 34.225.96.92 port 22: Broken pipe
有什么办法可以解决这个问题吗？没有 ssh，这个盒子就没用了。