Environment:
When an LXC container is in a stopped state, opening the "Console" tab causes xterm.js to render a black canvas overlay on the top half of the screen. This overlay covers the "Start Now" button, making it impossible to click directly from the console view .
Furthermore, if you attempt to interact with the console before starting the container (or if the backend mistakenly initializes the connection), PVE throws a hard backend error:
text
failed waiting for client: timed out
TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/100 --perm VM.Console --vncticket-endpoint --verify-port --ticket-fd 6 -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole100 -r winch -z lxc-console -n 100 -e -1' failed: exit code 1
To Reproduce:
Has anyone else encountered this? Any feedback would be greatly appreciated.
- Proxmox VE version: pve-manager/9.2.11 (Debian Trixie)
- Browser: Tested on Chrome, Edge, and Incognito mode across multiple devices.
- Scope: All LXC containers, including brand new ones created after the issue started.
When an LXC container is in a stopped state, opening the "Console" tab causes xterm.js to render a black canvas overlay on the top half of the screen. This overlay covers the "Start Now" button, making it impossible to click directly from the console view .
Furthermore, if you attempt to interact with the console before starting the container (or if the backend mistakenly initializes the connection), PVE throws a hard backend error:
text
failed waiting for client: timed out
TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/100 --perm VM.Console --vncticket-endpoint --verify-port --ticket-fd 6 -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole100 -r winch -z lxc-console -n 100 -e -1' failed: exit code 1
To Reproduce:
- Stop any LXC container (e.g., ID 100).
- Click the "Console" tab.
- Observe the black canvas overlay blocking the "Start Now" button .
- If you try to click "Start" through the console (or force the connection), the backend throws the termproxy timed out error mentioned above.
- The issue can be bypassed by going to the "Summary" tab, clicking "Start" there first, and then opening the console. The terminal works fine when the container is running.
- This is purely a frontend/UI issue and does not affect container performance or pct enter from the host shell.
- I have already tried:
- Hard browser refresh and clearing cache.
- Using different browsers and devices.
- Full physical host reboot.
- Reinstalling pve-manager and pve-xtermjs via apt.
- Cleaning /var/run/dtach and restarting pveproxy.
- Patching the CSS (.xterm-scrollable-element { display: none !important; }) directly into /usr/share/pve-manager/css/ext6-pve.css (which hides the overlay in some contexts but does not fix the underlying rendering logic).
Has anyone else encountered this? Any feedback would be greatly appreciated.