Server disconnected (code: 1006)

[opaxweb]

Hello,

I am new to the forum and proxmox, currently i am facing an issue when connecting to the console.

Everytime i try to connect to the console i get the following error message: "Server disconnected (code: 1006)"

Any help is greatly appreciated.

 

[dietmar]

What browser/os/version do you use?

 

[informant]

Hi, same issue here, but only on one node in cluster.

Test with newest FF, Opera, IE and Chrome.

error msg in log:

TASK ERROR: command '/bin/nc -l -p 5901 -w 10 -c '/usr/bin/ssh -T -o  BatchMode=yes 217.*.*.* /usr/sbin/qm vncproxy 5402 2>/dev/null''  failed: exit code 255
TASK ERROR: command '/bin/nc -l -p 5900 -w 10 -c '/usr/bin/ssh -T -o  BatchMode=yes 217.*.*.* /usr/sbin/qm vncproxy 5131 2>/dev/null''  failed: exit code 255

regards

 

[dietmar]

Hi, same issue here, but only on one node in cluster.

That IP address looks strange "217.*.*.*" Why does it conatin '*'?

 

[informant]

Hi, we can post our IP if you would, we have only comment it on this post^^.

regards

 

[dietmar]

Hi, we can post our IP if you would, we have only comment it on this post^^.

Next time, please mention that you manually modified the log output ...

 

[informant]

ok, i wouldn´t modify it in next time, but do you have a workarround for this issue?

regards

 

[dietmar]

but do you have a workarround for this issue?

no idea, sorry. Please try to debug by running those command on the command line ...

 

[informant]

Hi, without /dev/null:

'/bin/nc -l -p 5900 -w 10 -c '/usr/bin/ssh -T -o BatchMode=yes 217.69.254.69 /usr/sbin/qm vncproxy 5131
-bash: /bin/nc -l -p 5900 -w 10 -c /usr/bin/ssh: Datei oder Verzeichnis nicht gefunden

/bin/nc -l -p 5900 -w 10 -c /usr/bin/ssh -T -o BatchMode=yes 217.69.254.69 /usr/sbin/qm vncproxy 5131
BatchMode=yes: forward host lookup failed: Host name lookup failure

 

[dietmar]

Make sure you quote the command currectly, and verify what is missing /bin/nc or /usr/bin/sh ?

 

[informant]

Hi, i have edit the post, with correct command.

regards

 

[informant]

Hi all,

any ideas to fix it?

regards

 

[informant]

Hi all, we have test lookup hostname, and reverse lookup and ping hostname ... all working fine. what can we do do solve this error?

please help. very thanks and bet regards

 

[informant]

Hi all, we have found a solution for this problem.

you must clean /root/.ssh/know_hosts on node and cluster. after this you connect via ssh to node and cluster and have new keys. after this the vnc console works fine, without 1006 error.

regards

 

[term]

Hi all, we have found a solution for this problem.

you must clean /root/.ssh/know_hosts on node and cluster. after this you connect via ssh to node and cluster and have new keys. after this the vnc console works fine, without 1006 error.

regards

Hi,

Can you give any more detail on what you did? I emptied known_hosts on the nodes, but what else needs to be done?

Thanks!

 

[term]

After more investigation, I found that netcat6 was installed on my servers and caused this error. I ran "apt-get remove netcat6" and novnc started working immediately afterwards.

 

[Bent]

For future time travelers:

If you want to see the console from a vm on another node in your cluster and you get error 1006 in your browser console your issue might be this:

Try to ssh from the node which throws an error to the desired target node.

node01 -> node02 (example)

You may get an error similar to this one:

Warning: the ECDSA host key for 'XXXX' differs from the key for the IP address 'X.X.X:X'
Offending key for IP in /etc/ssh/ssh_known_hosts:4
Matching host key in /root/.ssh/known_hosts:1
Are you sure you want to continue connecting (yes/no)?

To fix this error, remove the entries of the broken target node in the following files (in this sample all entries about node02):

/etc/pve/priv/known_hosts
/etc/ssh/ssh_known_hosts
/root/.ssh/known_hosts

After this ssh from node01 to node02 via command line. You should get this info:

The authenticity of host 'node02 (X.X.X.X)' can't be established.
ECDSA key fingerprint is SHA256:XXXX
Are you sure you want to continue connecting (yes/no)?

Accept with yes. Log out of the remote shell again and try to ssh into node02 (from node01) again just to check that you'll be grated access without any further question or error.

You should now be able to use your cluster as expected again.