Undefined Code: 1006

[Maetz]

Every time im trying to open the Webconsole/Webshell to one of my VM's, I get the same error message:

For the Shells its:
Undefined Code: 1006

And for the Consoles its:
Failed to connect to server

You can look see them both in the screenshots I uploaded.
This is what I found in the logs:
failed waiting for client: timed out
TASK ERROR: command '/usr/bin/termproxy 5902 --path /vms/104 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole104 -r winch -z lxc-attach --clear-env -n 104' failed: exit code 1

This all started about a week ago. Before that everything was working just fine.

Im thankful for all answers!

 

[oguz]

hi,

This all started about a week ago. Before that everything was working just fine.

did you do an upgrade or change something in the meantime?

see this post's solution[0] , you probably have the same problem -- once you do the fix it should be working

[0]: https://forum.proxmox.com/threads/server-disconnected-code-1006.20036/#post-213288

 

[Maetz]

I didn't change anything. This solution also didnt fix ist. Im thinking of reinstalling proxmox because i think my whole installation is messed up. I cant even update my node anymore!

 

[oguz]

This solution also didnt fix ist.

can you ssh between the nodes normally?

I cant even update my node anymore!

what error do you get?

 

[Maetz]

can you ssh between the nodes normally?


what error do you get?

I get the same error as if im trying to open a normal console: The error says: Undefinded Code: 1006.

 

[ph0x]

Did you harden your ssh config in any way?

 

[Maetz]

Did you harden your ssh config in any way?

No. I only setup a homeassistant VM in the past week. Other from that I dont remember changing anything.

 

[Maetz]

Not even reinstalling works... Ive tried it with different versions of proxmox and used a CD and a USB Stick aswell...
Im getting really frustrated because I dont know what to do anymore...
I also can't find a thread where someone had the same issue as I did.

 

[Maetz]

failed waiting for client: timed out
TASK ERROR: command '/usr/bin/termproxy 5900 --path /nodes/pve --perm Sys.Console -- /bin/login -f root' failed: exit code 1

 

[oguz]

Not even reinstalling works... Ive tried it with different versions of proxmox and used a CD and a USB Stick aswell...
Im getting really frustrated because I dont know what to do anymore...
I also can't find a thread where someone had the same issue as I did.

have you checked the thread i've linked in my previous post?

 

[Maetz]

have you checked the thread i've linked in my previous post?

Ive solved the problem already… ESET Security denied the connections and I only had to change one setting.
I was so frustrated but after remebering that I activated my ESET Security that day, everything was clear to me.
Thank you for your help!

 

[erikwie]

Ive solved the problem already… ESET Security denied the connections and I only had to change one setting.
I was so frustrated but after remebering that I activated my ESET Security that day, everything was clear to me.
Thank you for your help!

I'm experiencing the same issue on a fresh installed Proxmox, and I run ESET Security, could you let me know what the one setting that needs changing in ESET is?

 

[Maetz]

I'm experiencing the same issue on a fresh installed Proxmox, and I run ESET Security, could you let me know what the one setting that needs changing in ESET is?

https://forum.proxmox.com/threads/console-timeout.57303/

Hope this helps!

 

[trueman]

I am having the same issue but only with one of my two servers and only using safari. I have easy workaround but would like to know what's blocking me from using shell. Im not sure what ESET would translate to for a Mac user.
Thanks for the help in advance!

 

[Kevo]

Try manually importing the cert into the keychain and setting it to always trusted. It fixed it for me in Safari. I think my server updated it's cert or something recently and Safari wouldn't automatically trust the new certificate. I don't think this would be an issue with a non-self signed cert.

 

[OD3UNICRON]

This happened to me also,
I installed Nginx-Proxy-Manager, and I tried to log in remotely. I had the same issue; The issue was corrected in my case by enabling Websockets Support, and that solved my problem; now I can connect remotely, no more code 1006.

 

[Mr.J]

This happened to me also,
I installed Nginx-Proxy-Manager, and I tried to log in remotely. I had the same issue; The issue was corrected in my case by enabling Websockets Support, and that solved my problem; now I can connect remotely, no more code 1006.

I'm getting the same code 1006, and I'm also using Nginx-Proxy-Manager. But I'm fairly new, so can you please tell me how to enable the websocket support.

 

[OD3UNICRON]

I'm getting the same code 1006, and I'm also using Nginx-Proxy-Manager. But I'm fairly new, so can you please tell me how to enable the websocket support.

It's on your Nginx-Proxy-Manger when you create a proxy, it gives you the option to enable WebSocket.

 

[sprickw]

I administer my nginx reverse proxy server by CLI only. How do I enable WebSocket this way?

 

[banditbiker]

I fixed this on my mac by going into KeyChain Access --> Login keychain (Under default keychain) --> tab Certificates and then double click on the hostname of your proxmox box. Under Trust, select always trust.