Received disconnect from 203.0.113.10 port 22:2: Too many authentication failures
The client offered too many keys before the right one
Seen in OpenSSH client and server
The server disconnected because the client tried more authentication attempts than the server's MaxAuthTries allows.
Common causes
- ssh-agent holds many keys and the client offers each one in turn before the correct key.
- Repeated wrong passwords.
How to fix it
- Pin the key for that host in ~/.ssh/config: IdentityFile ~/.ssh/the_key plus IdentitiesOnly yes.
- Or on the command line: ssh -o IdentitiesOnly=yes -i ~/.ssh/the_key user@host.
- Remove unused keys from the agent (ssh-add -D, then add only what you need).
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
- 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