0%

SSH [WARNING. REMOTE HOST IDENTIFICATION HAS CHANGED!]

💢 This message appears because the first SSH connection now generates a certificate that is stored in the client’s known_hosts, but if the server is reloaded, the authentication information will change. This error occurs when the server side is different from the client side.

1
2
3
4
5
6
7
8
9
10
11
12
13
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
xx.xx.xx.xx.xx...
Please contact your system administrator.
Add correct host key in /home/hostname/.ssh/known_hosts to get rid of this message.
Offending key in /home/hostname/.ssh/known_hosts:10
RSA host key for 192.168.x.xx has changed and you have requested strict checking.
Host key verification failed.

Therefore, just delete the authentication information from your computer. It will be regenerated when it is connected. Deleting is very simple, just enter an instruction on the client:

1
ssh-keygen -R [host]
  • For example: 🙋
1
2
3
4
ssh-keygen -R 192.168.xx.xx

# or
ssh-keygen -f "/home/hostname/.ssh/known_hosts" -R [192.168.xx.xx]:3333
  • Next, connect again and it will appear.
1
Are you sure you want to continue connecting (yes/no)?

Enter yes to complete the connection! At the same time, new certifications have been generated.


Note: This message may also be caused by a hacker attack, unless you are sure that this is really due to key inconsistencies caused by factors such as reloading, otherwise please try another network environment, maybe you are not a secure network environment! 🚨