@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @

[djsami]

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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
SHA256OhNF7mZCgXbWkg7RcyKhQiz97tCv4WRn3cqqPX4Rh8.
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 "server1"
RSA host key for server1 has changed and you have requested strict checking.
Host key verification failed.
TASK ERROR: Failed to run vncproxy.

Promlem cluster proxmox error consol.

 

[matrix]

Is the issue on all VMs?

Promlem cluster proxmox error consol.

my guess is from Cluster. Please try to do this command: pvecm updatecerts -f and try again

if not work post pveversion -v

 

[alejandroc79]

Gracias, por la ayuda, con ese comando ya se puede visualizar las MV con el vizor VNC

 

[Jason Wang]

Is the issue on all VMs?


my guess is from Cluster. Please try to do this command: pvecm updatecerts -f and try again

if not work post pveversion -v

Thanks. it works.

 

[Noah0302]

Is the issue on all VMs?


my guess is from Cluster. Please try to do this command: pvecm updatecerts -f and try again

if not work post pveversion -v

Thank you, that also fixed it for me after I upgraded from:
Linux 5.15.85-1-pve #1 SMP PVE 5.15.85-1 ---> Linux 5.15.102-1-pve #1 SMP PVE 5.15.102-1
in my cluster

I dont know why it changed though...

 

[Bruno Gaiotto]

Is the issue on all VMs?


my guess is from Cluster. Please try to do this command: pvecm updatecerts -f and try again

if not work post pveversion -v

Obrigado me ajudou

 

[webardo]

Thanks. it works.

Is the issue on all VMs?


my guess is from Cluster. Please try to do this command: pvecm updatecerts -f and try again

if not work post pveversion -v

Thanks, it worked proxmox v8

 

[esi_y]

See also:

https://forum.proxmox.com/threads/s...s-how-to-bypass-ssh-known_hosts-bug-s.137809/