You should talk the administrators of this x.x.x.x host and the network that it's attached to, to see if they can identify the problem from their end. So the SSH server process is apparently able to talk to a client without crashing. It looks like the ssh-keyscan program was able to connect to the server and get a version string without an error. Some firewall is interfering with connections to the ssh server.The SSH server process malfunctioned (crashed), or perhaps it detected some serious issue causing it to exit immediately.The error that you're getting means that the TCP connection from the client to the server was 'abnormally closed' while the client was waiting for this data from the server, in other words immediately after the TCP connection was opened.Īs a practical matter, it's likely to mean one of two things: When an SSH client connects to an SSH server, the server starts by sending a version string to the client.

Kex_exchange_identification: read: Connection reset by peer

$ scp -rv api.yml program /usr/bin/ssh host x.x.x.x, user root, command scp -v -r -t /home/services/test/ĭebug1: Reading configuration data /etc/ssh/ssh_configĭebug1: Authenticator provider $SSH_SK_PROVIDER did not resolve disablingĭebug1: Connecting to x.x.x.x port 22.ĭebug1: identity file /root/.ssh/id_rsa type -1ĭebug1: identity file /root/.ssh/id_rsa-cert type -1ĭebug1: identity file /root/.ssh/id_dsa type -1ĭebug1: identity file /root/.ssh/id_dsa-cert type -1ĭebug1: identity file /root/.ssh/id_ecdsa type -1ĭebug1: identity file /root/.ssh/id_ecdsa-cert type -1ĭebug1: identity file /root/.ssh/id_ecdsa_sk type -1ĭebug1: identity file /root/.ssh/id_ecdsa_sk-cert type -1ĭebug1: identity file /root/.ssh/id_ed25519 type -1ĭebug1: identity file /root/.ssh/id_ed25519-cert type -1ĭebug1: identity file /root/.ssh/id_ed25519_sk type -1ĭebug1: identity file /root/.ssh/id_ed25519_sk-cert type -1ĭebug1: identity file /root/.ssh/id_xmss type -1ĭebug1: identity file /root/.ssh/id_xmss-cert type -1ĭebug1: Local version string SSH-2.0-OpenSSH_8.6 $ ssh-keyscan -H $IP > ~/.ssh/known_hosts Identity added: /root/.ssh/id_rsa (/root/.ssh/id_rsa) $ echo '$SSH_PRIVATE_KEY' | tr -d ' ' > ~/.ssh/id_rsa The error is: kex_exchange_identification: read: Connection reset by peer

I want to copy data with scp in a GitLab pipeline using PRIVATE_KEY.

Protonvpn connecting failed mac