Can no longer access Server/VM/LXC's Shell/Console with Firefox

rs_taylor

New Member
Mar 11, 2024
3
0
1
HI,

Firstly, i've found several people with similiar issues, but most seem to be VERY old and seem to be related to using Clusters which im not.
I have a Single PC, running Proxmox VE 8.2.2, have been using it for about 6months, its runs several LXC's and a OPNSense virutal machine.

All containers are running their apps just fine & can be started and stopped from the Proxmox WebGUI.
I can maintain most of them via their own WebGUI's but occassionally i need to drop to a shell.
I used do this from the Proxmox WebGUI, selecting the node/container/app i wanted a shell for & right clicked and chose Console/Shell.

Recently (in the past couple of days) this has stopped working. Whether it be the Nodes themselves or the "pve" (i never renamed it).
I have always used Firefox but have discovered Bing works fine (gives me the shell/Console i want)

Examples of Output Error
Code:
failed waiting for client: timed out
TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/101 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole101 -r winch -z lxc-attach --clear-env -n 101' failed: exit code 1

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

Any help greatly appreciated!
 
Last edited:
Hi,

Can you please check the `pct enter 101` of the LXC?

And did you see other above provided output in the syslog? you can run `journalctl -f` and try to access the LXC Console in the Proxmox VE Web UI.
 
I cant(or couldn't) use the WebGUI to drop/shell to console at the parent level, but i can with SSH & i can use PCT Enter to access any of the running LXC's.

Should i run journalctl -f from the LXC or at the parent level?

root@pve:~# journalctl -f
Oct 31 19:55:57 pve systemd[764648]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Oct 31 19:55:57 pve systemd[764648]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Oct 31 19:55:57 pve systemd[764648]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Oct 31 19:55:57 pve systemd[764648]: Reached target sockets.target - Sockets.
Oct 31 19:55:57 pve systemd[764648]: Reached target basic.target - Basic System.
Oct 31 19:55:57 pve systemd[764648]: Reached target default.target - Main User Target.
Oct 31 19:55:57 pve systemd[764648]: Startup finished in 86ms.
Oct 31 19:55:57 pve systemd[1]: Started user@0.service - User Manager for UID 0.
Oct 31 19:55:57 pve systemd[1]: Started session-192.scope - Session 192 of User root.
Oct 31 19:55:57 pve sshd[764600]: pam_env(sshd:session): deprecated reading of user environment enabled

I dont know if this "Fixed" it (if it did thank you!), but my console/shells are now opening as expected.
 
If you want to know what happened exactly and how fixed the issue, you can post more information for the syslog/journalctl!
 

About

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!