Eu ssh para o EC2 o tempo todo, usando tanto o PuTTY quanto o WinSCP. Eu descobri recentemente a função Commands > Open in PuTTY no WinSCP, no entanto, parece que não funciona. Ao conectar recebo este erro (PuTTY):
Network error: Connection refused
E este é o erro no log de eventos do PuTTY:
2018-05-23 22:40:11 Connecting to ::1 port 22
2018-05-23 22:40:11 We claim version: SSH-2.0-PuTTY_Release_0.70
2018-05-23 22:40:12 Failed to connect to ::1: Network error: Connection refused
2018-05-23 22:40:12 Connecting to 10.8.x.x port 22
2018-05-23 22:40:13 Failed to connect to 10.8.x.x: Network error: Connection refused
2018-05-23 22:40:13 Connecting to 192.168.x.x port 22
2018-05-23 22:40:14 Failed to connect to 192.168.56.1: Network error: Connection refused
2018-05-23 22:40:14 Connecting to 192.168.x.x port 22
2018-05-23 22:40:15 Failed to connect to 192.168.x.x: Network error: Connection refused
2018-05-23 22:40:15 Network error: Connection refused
(endereços IP parcialmente redigidos com x.x)
O problema é que o IP está se conectando a (primeira linha)
2018-05-23 22:40:11 Connecting to ::1 port 22
É assim que um log de evento de trabalho se parece:
2018-05-23 22:44:01 Connecting to o.o.o.o port 22
2018-05-23 22:44:01 We claim version: SSH-2.0-PuTTY_Release_0.70
2018-05-23 22:44:01 Server version: SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4
2018-05-23 22:44:01 Using SSH protocol version 2
2018-05-23 22:44:01 Doing ECDH key exchange with curve Curve25519 and hash SHA-256
2018-05-23 22:44:02 Server also has ecdsa-sha2-nistp256/ssh-rsa host keys, but we don't know any of them
2018-05-23 22:44:02 Host key fingerprint is:
2018-05-23 22:44:02 ssh-ed25519 256 <removed>
2018-05-23 22:44:02 Initialised AES-256 SDCTR client->server encryption
2018-05-23 22:44:02 Initialised HMAC-SHA-256 client->server MAC algorithm
2018-05-23 22:44:02 Initialised AES-256 SDCTR server->client encryption
2018-05-23 22:44:02 Initialised HMAC-SHA-256 server->client MAC algorithm
2018-05-23 22:44:02 Reading key file "<removed>"
2018-05-23 22:44:02 Pageant is running. Requesting keys.
2018-05-23 22:44:02 Pageant has 1 SSH-2 keys
2018-05-23 22:44:02 Configured key file not in Pageant
2018-05-23 22:44:02 Offered public key
2018-05-23 22:44:02 Offer of public key accepted
2018-05-23 22:44:02 Sent public key signature
2018-05-23 22:44:02 Access granted
2018-05-23 22:44:02 Opening session as main channel
2018-05-23 22:44:03 Opened main channel
2018-05-23 22:44:03 Allocated pty (ospeed 38400bps, ispeed 38400bps)
2018-05-23 22:44:03 Started a shell/command
Onde o.o.o.o na linha 1 representa o IP público da instância do EC2.
Alguma idéia de por que a conexão é ::1 do WinSCP e não o endereço IP correto?
Quando pressiono Ctrl + Shift enquanto clico em Open in PuTTY , este é o conteúdo da área de transferência:
"C:\Program Files\PuTTY\putty.exe" -load aws-ubuntu
aws-ubuntu sendo o nome de uma configuração / site no WinSCP.
Quando você tiver uma sessão armazenada no PuTTY que corresponda a um nome do site atual no WinSCP, o WinSCP instruirá o PuTTY a usar essa sessão, em vez de passar as configurações do WinSCP para o PuTTY.
Veja link
Esse é o seu caso ( -load aws-ubuntu ).
Parece que sua sessão aws-ubuntu no PuTTY não está configurada da mesma maneira que WinSCP aws-ubuntu site.
Remova ou corrija a sessão aws-ubuntu no PuTTY.