[SOLVED] Unable to run Shell for PVE (error 500: waiting for port 5900)

latrik

New Member
Jan 10, 2024
6
1
3
Hello everyone, If I want to run the Shell on my PVE, I get this error:

Connection failed (Error:500: timeout while waiting for port '5900' to get ready!)

I suspect that this problem occurred after changing the default ip address of the Proxmox server (default ip: 192.168.1.70, new IP: 192.168.50.2). Access via SSH works fine, I only have problems in the web interface. I also tested all browsers and the same error everywhere.

Error statement:

TASK ERROR: command '/usr/bin/termproxy 5900 --path /nodes/nuc --perm Sys.Console -- /bin/login -f root' failed: open3: exec of /usr/bin/termproxy 5900 --path /nodes/nuc --perm Sys.Console -- /bin/login -f root failed: No such file or directory at /usr/share/perl5/PVE/Tools.pm line 494.

Anyone have any idea what the problem is?

intefaces (after edit):
Code:
auto lo
iface lo inet loopback
iface eno1 inet manual

auto vmbr0
iface vmbr0 inet manual
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto vmbr0.50
iface vmbr0.50 inet static
address 192.168.50.2/24
gateway 192.168.50.1

source /etc/network/interfaces.d/*

iface wlp0s20f3 inet manual

hosts:
Code:
127.0.0.1 localhost.localdomain localhost
192.168.50.2 nuc.local nuc

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

pveversion:
Code:
proxmox-ve: 8.1.0 (running kernel: 6.5.11-7-pve)
pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
pve-kernel-5.15: 7.4-4
proxmox-kernel-6.5: 6.5.11-7
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
pve-kernel-5.15.108-1-pve: 5.15.108-1
ceph: 17.2.7-pve1
ceph-fuse: 17.2.7-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.2-1
proxmox-backup-file-restore: 3.1.2-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.2
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.3
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-2
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.1.5
pve-qemu-kvm: 8.1.2-6
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve1
 
I tried changing the IP address back and the error persists. Syslog:

Code:
Jan 12 17:49:20 nuc pvedaemon[4968]: starting termproxy UPID:nuc:00001368:000055F7:65A16D90:vncshell::root@pam:
Jan 12 17:49:20 nuc pvedaemon[1000]: <root@pam> starting task UPID:nuc:00001368:000055F7:65A16D90:vncshell::root@pam:
Jan 12 17:49:20 nuc pvedaemon[4968]: command '/usr/bin/termproxy 5900 --path /nodes/nuc --perm Sys.Console -- /bin/login -f root' failed: open3: exec of /usr/bin/termproxy 5900 --path /nodes/nuc --perm Sys.Console -- /bin/login -f root failed: No such file or directory at /usr/share/perl5/PVE/Tools.pm line 494.
Jan 12 17:49:26 nuc pvedaemon[1000]: <root@pam> end task UPID:nuc:00001368:000055F7:65A16D90:vncshell::root@pam: command '/usr/bin/termproxy 5900 --path /nodes/nuc --perm Sys.Console -- /bin/login -f root' failed: open3: exec of /usr/bin/termproxy 5900 --path /nodes/nuc --perm Sys.Console -- /bin/login -f root failed: No such file or directory at /usr/share/perl5/PVE/Tools.pm line 494.
 
Looks like the problem is solved, Shell (xterm.js) is working gain.

The solution was to reinstall the proxmox-termproxy.
 

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!