Can't connect to shell from gui

Hi,

I seem not to be able anymore to connect to proxmox shell anymore through the gui.

Nothing pointing in the right direction in syslog:

Code:
Jun 12 21:42:20 pvenode1 pvedaemon[973976]: launch command: /usr/bin/vncterm -rfbport 5900 -timeout 10 -authpath /nodes/pvenode1 -perm Sys.Console -notls -listen localhost -c /bin/login -f root
Jun 12 21:42:21 pvenode1 login[973986]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
Jun 12 21:42:21 pvenode1 systemd-logind[3891]: New session 195 of user root.
Jun 12 21:42:21 pvenode1 systemd[1]: Started Session 195 of user root.
Jun 12 21:42:21 pvenode1 login[973991]: ROOT LOGIN  on '/dev/pts/1'
Jun 12 21:42:31 pvenode1 systemd-logind[3891]: Session 195 logged out. Waiting for processes to exit.
Jun 12 21:42:31 pvenode1 systemd[1]: session-195.scope: Succeeded.
Jun 12 21:42:31 pvenode1 systemd-logind[3891]: Removed session 195.
Jun 12 21:42:31 pvenode1 pvedaemon[298885]: <root@pam> end task UPID:pvenode1:000EDC98:01B996C1:62A6419C:vncshell::root@pam: OK

But the result always is "Failure to connect".

Is there some way fix it?

Thank you
 
Hi,

can you check if systemctl status pveproxy.service the service is up?
 
Ah I missread your post a bit. I missed the shell part.

You can try to open the browser debugger and see if there is something in the console log written there. Can you also post the output of pveversion -v?
 
Result of
Code:
pveversion -v
:

Code:
proxmox-ve: 7.2-1 (running kernel: 5.15.35-2-pve)
pve-manager: 7.2-4 (running version: 7.2-4/ca9d43cc)
pve-kernel-5.15: 7.2-4
pve-kernel-helper: 7.2-4
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph: 16.2.7
ceph-fuse: 16.2.7
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-4
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
openvswitch-switch: 2.15.0+ds1-2+deb11u1
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1


I'll get back to the PC in the evening (Europe/Rome) to check the browser debugger.
 
Last edited:
Immagine.jpg

This is Chrome's debugger, pointing to somethin g in pve's js.
I have to say that from Chrome I can't even upload images to the forum (I am on Firefox now).
From Firefox it seems the "popup" term (both xterm and novnc) is not working (failure to connect like in Chrome) but the incorporated term works (do not know if it launches noVnc or Xterm).
Edge seems to work like Chrome (eg. not working at all).

From the other PC, everything seems to work properly.

PS: Chrome and Edge have fairly different extensions enabled.
 
Ok, some more info, I get this when trying from Chrome:

Code:
client connection: 127.0.0.1:44068
failed reading ticket: connection closed before authentication
TASK ERROR: command '/usr/bin/termproxy 5900 --path /nodes/pvenode2 --perm Sys.Console -- /usr/bin/ssh -e none -t 10.0.10.12 -- /bin/login -f root' failed: exit code 1
 
I cannot reach any VM in any node, nor I can reach the nodes themselves through the gui terms.

I also saw that thread, the change in ssh port slightly moves it in another direction.
Only thing I did similar, has been to add an authorized key on the nodes to enable key ssh from a PC.
Going back with that change do not help, and with that authorized key in there, the other PC has access to the terminals.

Thank you very much for your time and patience.
 

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!