VM Connection Timeout One Second, Starts Next Second...


Mar 9, 2023
Whenever I start a VM, I get: TASK ERROR: connection timed out, then, exactly the next second, it starts and run as if the timeout message had not occurred...wanting to understand why it does that?

root@nolliprivatecloud:~# pveversion
pve-manager/8.0.4/d258a813cfa6b390 (running kernel: 6.2.16-19-pve)
Last edited:
Had hope someone would have an idea, knowing that even if I check the logs, it most likely would not offer a clear message as to why. So, I checked the log:
Nov 02 20:51:08 nolliprivatecloud pveproxy[2103]: proxy detected vanished client connection
Nov 02 20:51:09 nolliprivatecloud pvedaemon[2709]: starting vnc proxy UPID:nolliprivatecloud:00000A95:000016D5:6544520D:vncproxy:100:root@pam:
Nov 02 20:51:09 nolliprivatecloud pvedaemon[2076]: <root@pam> starting task UPID:nolliprivatecloud:00000A95:000016D5:6544520D:vncproxy:100:root@pam:
Nov 02 20:51:18 nolliprivatecloud pvedaemon[2705]: connection timed out
Nov 02 20:51:18 nolliprivatecloud pvedaemon[2076]: <root@pam> end task UPID:nolliprivatecloud:00000A91:000016CD:6544520C:vncproxy:100:root@pam: connection ti>
Nov 02 20:51:25 nolliprivatecloud kernel: usb 1-7: reset full-speed USB device number 2 using xhci_hcd

It appears that the act of clicking start in the VNC is responsible...at 20:51:08 then at 20;51:09 it realized that starting the VM boot process had occured...however, it took another 9 seconds to log the connection timed out...


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!