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
Seen in OpenSSH 8.8 and later connecting to old servers, network devices, older Git servers
Your SSH client no longer accepts the host key algorithm the server offers, usually ssh-rsa with SHA-1 or ssh-dss.
Common causes
- OpenSSH 8.8 disabled ssh-rsa (RSA with SHA-1) signatures by default.
- The server, appliance or switch runs an old SSH implementation that offers nothing newer.
How to fix it
- Upgrade the server or add a modern host key (ed25519 or ecdsa) so it offers a current algorithm.
- As a temporary per-host workaround, in ~/.ssh/config: Host oldbox, HostKeyAlgorithms +ssh-rsa, PubkeyAcceptedAlgorithms +ssh-rsa.
- Keep the workaround scoped to that one host rather than global.
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 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