Connection closed by 203.0.113.10 port 22
The SSH server ended the session
Seen in OpenSSH client, git over SSH
The server closed the SSH connection, usually during the handshake or authentication, without giving the client a reason.
Common causes
- The server rejected the user or source address (AllowUsers, DenyUsers, fail2ban, hosts.deny).
- Authentication failed and the server dropped the session.
- sshd hit MaxStartups under load or a brute-force attempt and refused new sessions.
How to fix it
- Run ssh -vvv user@host to see the last step before the close.
- Check the server log (journalctl -u ssh or /var/log/auth.log) for the matching entry.
- If you are banned by fail2ban, unban your IP: fail2ban-client set sshd unbanip <ip>.
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
- kex_exchange_identification: Connection closed by remote host · The SSH server closed the connection before the handshake
- 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
- npm ERR! code ETIMEDOUT · npm couldn't reach the registry in time
- npm ERR! code ERR_SOCKET_TIMEOUT · The registry connection went silent