Navigated shell login error
- Thread starter pfraneto
- Start date
This is a common ssh error.
If you connect to a ssh server with an address the host key will be saved for that address. If the host key changes this error gets displayed, because it might be no the host your expecting to connect to.
This is expected if you reinstalled a host or VM because the old host key is lost. In that case type in the line in the error message starting with "ssh-keygen -f". This deletes the old key.
If you connect to a ssh server with an address the host key will be saved for that address. If the host key changes this error gets displayed, because it might be no the host your expecting to connect to.
This is expected if you reinstalled a host or VM because the old host key is lost. In that case type in the line in the error message starting with "ssh-keygen -f". This deletes the old key.
Last edited:
Hello
I am not entirely sure in what context you opened this terminal.
What I can tell you about this error:
When you connect with ssh the first time, the client saves a hash that identifies the host. At any future connection, the ssh client will compare the host hash with the one it got from the first connection. This is done for security reasons. If someone tried to impersonate the server you are trying to connect to, they would generate a different hash, resulting in this exact error.
However, it is also possible that you simply had a different server at this IP in the past. Then you set up a new one and the ssh client remembers that the fingerprint on that IP was different.
It is up to you now to find out if there is a good reason (like reinstalling a server) why this hash has changed, or if there is actually someone trying something nasty. If you think it's cool, the output you posted also contains a command you can simply run to remove the old hash from memory.
I am not entirely sure in what context you opened this terminal.
What I can tell you about this error:
When you connect with ssh the first time, the client saves a hash that identifies the host. At any future connection, the ssh client will compare the host hash with the one it got from the first connection. This is done for security reasons. If someone tried to impersonate the server you are trying to connect to, they would generate a different hash, resulting in this exact error.
However, it is also possible that you simply had a different server at this IP in the past. Then you set up a new one and the ssh client remembers that the fingerprint on that IP was different.
It is up to you now to find out if there is a good reason (like reinstalling a server) why this hash has changed, or if there is actually someone trying something nasty. If you think it's cool, the output you posted also contains a command you can simply run to remove the old hash from memory.
Azunai, I did the deletion process using this command "ssh-keygen -f" , but it still shows this message and the error code 1006
I recognize what was done by me, and I cannot access the Console, because of this error, I am accessing it using Putty or on the local server. I also ran the command "ssh-keygen -f", and it is also returning the error Code 1006.
You seem to be conflating multiple things here. SSH does not produce code 1006, you likely mean VNC?
Can you please produce, preferably in text form but if you cant - clear and full screenshots are ok, where are you trying to ssh (IP/host included) to where (IP/host included). What happens exactly when you are trying to SSH (and use external client like Putty).
If using Putty, you may want to clear known_hosts registry entries:
https://www.rit.edu/researchcomputing/instructions/Clearing-the-known_hosts-SSH-File
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Accessing via ssh does not show an error, only accessing via the browser, any browser is showing error 1006, firefox, opera, chrome, brave... This command "ssh-keygen -f" was to resolve the alert message reported in the console.
Even running the command to remove the key still gives me the error:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 ECDSA key sent by the remote host is
SHA256:3tZEqMDxjuOeTB1EQIbLM... .
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:1
remove with:
ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R "pve02"
ECDSA host key for pve02 has changed and you have requested strict checking.
Host key verification failed.
TASK ERROR: Failed to run vncproxy.
This error happens when I am in the virtual machine console or logging into the pves node group
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 ECDSA key sent by the remote host is
SHA256:3tZEqMDxjuOeTB1EQIbLM... .
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:1
remove with:
ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R "pve02"
ECDSA host key for pve02 has changed and you have requested strict checking.
Host key verification failed.
TASK ERROR: Failed to run vncproxy.
This error happens when I am in the virtual machine console or logging into the pves node group
Hello
Sorry. I should have been more specific. I mend to run the command on the Proxmox VE.
Regards
Philipp
Sorry. I should have been more specific. I mend to run the command on the Proxmox VE.
Regards
Philipp