Last night I updated my Lab from Proxmox VE 7.2 to 7.3. My lab consists of four (4) nodes (pve01,pve02,pve03,pve04). After performing this update (pve non subscription) I started getting the following when attempting to access pve02 from the Proxmox webui from my assigned 'proxmox.networkname.net' (pve01):
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 RSA key sent by the remote host is
SHA256:UfFtQHGwtY8NO7xPgD9rolK2dFewRHJ2KTEYopiBVy4.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending RSA key in /etc/ssh/ssh_known_hosts:3
remove with:
ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R "pve02"
RSA host key for pve02 has changed and you have requested strict checking.
Host key verification failed.
TASK ERROR: Failed to run vncproxy.
I have found that I get the same error if I log into the Webui from pve01 (above), pve03 and pve04.
I have searched to find the proper way to fix this with limited success.
I performed the 'pvecm updatecerts' on all four nodes. After this I was able to get the pve02 server shell and able to get the shell from the single container I have on pve02. However, I continue to get the same message (above) when I attempt to access the console (vncproxy). In the 'console' window I get the red band at the top "Failed to connect to server" and the above message is in the Cluster Log.
It would appear that the update on pve02 changed something (I wish I knew what). I can recreate the above from all three (3) other nodes (pve01,pve03,pve04) when attempting to access node pve02 VM consoles.
I am now no longer able to migrate templates, VMs and Containers to/from pve02 to the rest of the cluster.
Thank You in advance for your help
MD
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 RSA key sent by the remote host is
SHA256:UfFtQHGwtY8NO7xPgD9rolK2dFewRHJ2KTEYopiBVy4.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending RSA key in /etc/ssh/ssh_known_hosts:3
remove with:
ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R "pve02"
RSA host key for pve02 has changed and you have requested strict checking.
Host key verification failed.
TASK ERROR: Failed to run vncproxy.
I have found that I get the same error if I log into the Webui from pve01 (above), pve03 and pve04.
I have searched to find the proper way to fix this with limited success.
I performed the 'pvecm updatecerts' on all four nodes. After this I was able to get the pve02 server shell and able to get the shell from the single container I have on pve02. However, I continue to get the same message (above) when I attempt to access the console (vncproxy). In the 'console' window I get the red band at the top "Failed to connect to server" and the above message is in the Cluster Log.
It would appear that the update on pve02 changed something (I wish I knew what). I can recreate the above from all three (3) other nodes (pve01,pve03,pve04) when attempting to access node pve02 VM consoles.
I am now no longer able to migrate templates, VMs and Containers to/from pve02 to the rest of the cluster.
Thank You in advance for your help
MD