kex_exchange_identification: Connection closed by remote host
The SSH server closed the connection before the handshake
Seen in OpenSSH client, git over SSH (GitHub, GitLab)
The TCP connection opened, but the server (or something in between) closed it before sending its SSH version banner.
Common causes
- A firewall, proxy or VPN blocks or intercepts SSH on port 22.
- sshd on the server is refusing new connections: MaxStartups reached, fail2ban, or hosts.deny rules.
- Something other than sshd is listening on the port, or sshd is crashing on start-up.
How to fix it
- For GitHub, try SSH over port 443: ssh -T -p 443 git@ssh.github.com.
- Run ssh -v to see where it stops, and test from another network to rule out a local firewall.
- On your own server, check the sshd log (journalctl -u ssh or -u sshd) and any fail2ban bans.
Got a different message? Paste it into the error explainer.
Related errors
- error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413 · The push is larger than the server or proxy accepts
- error: RPC failed; curl 18 transfer closed with outstanding read data remaining · The connection dropped during a git transfer
- fatal: the remote end hung up unexpectedly · The Git server closed the connection
- Permission denied (publickey) · The server rejected every SSH key you offered
- Host key verification failed. · SSH couldn't confirm the server's identity
- WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! · The server's SSH host key is different from last time
- Unable to negotiate with 203.0.113.10 port 22: no matching host key type found. Their offer: ssh-rsa · The server only offers an old host key type
- Unable to negotiate with 203.0.113.10 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 · Client and server share no key exchange algorithm
- Received disconnect from 203.0.113.10 port 22:2: Too many authentication failures · The client offered too many keys before the right one
- Connection closed by 203.0.113.10 port 22 · The SSH server ended the session
- npm ERR! code ETIMEDOUT · npm couldn't reach the registry in time
- npm ERR! code ERR_SOCKET_TIMEOUT · The registry connection went silent