8.3 console - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!

[Treeman]

Because of the Ubuntu 24.04 issue, I recently updated my 5 node cluster to 8.3. (3 5800 mini pc's, 2 n100's) 4 of the nodes are great, everything is stable, working well, but... One of my n100 nodes now displays the typical SSH error when trying to console into anything, including a fresh new container spun up just for testing it. Versions match across the board on everything.

Anyone have any ideas for fixes? I'm hesitant to blow it away and out of the cluster to rebuild, proxmox clustering always seems to get a bit finicky when doing deletes. There is nothing running on the node at the moment, I migrated everything off, so it isn't a big deal if I have to though. (I've tried all the standard stuff, manually trying to find/update known hosts, running pvecm updatecerts -F, rebooting, etc... No change)

 

[BobhWasatch]

Did you try saying "yes" to the message?

 

[Treeman]

Can't unfortantely, it is what Prox uses to establish the console and doesn't give you the opportunity. This is the full message.


On a different note, I did decide to wipe and reinstall that node. Worked until I joined it to the cluster, and the problem returned. So something is being pushed that is causing it. I'm guessing I could maybe fix it by making sure the new one is named something else, but my limited OCD is not going to allow me to have proxmox1-3, proxmox5,6 (4 is the broken one!)



@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:+z3gTuvZ8HNGGt7IyNEBNYsc4kxUB+IVePtnKQYxLHY.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /root/.ssh/known_hosts:15
remove with:
ssh-keygen -f "/root/.ssh/known_hosts" -R "192.168.0.72"
Host key for 192.168.0.72 has changed and you have requested strict checking.
Host key verification failed.

 

[maxim.webster]

remove with:
ssh-keygen -f "/root/.ssh/known_hosts" -R "192.168.0.72"

Way to go.

 

[Treeman]

Way to go.

I tried that several times both before and after reinstalling, but... It depends which node! I normally web into node 2, that is what I'm proxing to via cloudflare so it just is my default. I had been running the command on node 4, the problem child. Turns out, I needed to run it on node 2 instead!

Cleared it up entirely!

 

[maxim.webster]

The message appears on the client, if the host you are connecting to has changed it‘s IP address, hostname or SSH public key, since you initially connected to it.

So the fix must be done on every client.