Host key verification failed.
SSH couldn't confirm the server's identity
Seen in OpenSSH client, git over SSH, CI pipelines, Ansible
SSH refused to connect because the server's host key is unknown or does not match the one in known_hosts, and it could not ask you to confirm.
Common causes
- The host is not in known_hosts and the session is non-interactive (CI, scripts, git in a container).
- The server was rebuilt or its IP reused, so its key changed.
- You answered 'no' at the fingerprint prompt.
How to fix it
- Connect once interactively and verify the fingerprint against the provider's published one before accepting.
- In CI, add the host key to known_hosts in advance: ssh-keyscan github.com >> ~/.ssh/known_hosts, after checking the fingerprint.
- If the key genuinely changed, remove the old entry with ssh-keygen -R hostname.
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
- 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