Remote Host Identification Has Changed
SSH refuses to connect and shows:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!...Host key verification failed.Your computer remembers each server’s identity (its host key) from the first connection. Reinstalling a server creates a new host key on the same IP address. The saved host key does not match the new one.
Fixing it after a reinstall
Section titled “Fixing it after a reinstall”Remove the saved host key for that IP address, then connect again:
ssh-keygen -R 203.0.113.10ssh root@203.0.113.10This works the same in Windows PowerShell. SSH asks you to confirm the server again, as on your first login.
In Bitvise, the warning shows as a host key prompt. Hit “Accept and Save” if you reinstalled the server.
If you did not reinstall
Section titled “If you did not reinstall”A changed host key without a reinstall can mean something is intercepting your connection. Do not accept it. Check the server’s real fingerprint on the dashboard console instead:
- Head over to the instance list on our control panel and open your instance
- Open the “Terminal” tab
- Log in with the instance password
- Print the fingerprint and compare it with the one SSH shows:
ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pubIf they match, remove the old key as above. If they do not, contact support.