Unable to access shell

denp1

New Member
Dec 25, 2019
3
0
1
30
I am unable to connect to the shell from the proxmox web-page.

Error below:
Code:
TASK ERROR: command '/usr/bin/termproxy 5900 --path /nodes/proxmox --perm Sys.Console -- /bin/login -f root' failed: exit code 4

Steps ive been through
1 - Installed proxmox onto a laptop
2 - had to change network interfaces - originally setup to bridge wlp2s0 so changed it to bridge ethernet enp1s0. Then after reboot able to connect to webpage and also able to ssh into the proxmox host but cant connect to the webpage shell
3 - setup a new vm started it from webpage but couldn't open a terminal from webpage or qm terminal vid
4 - reinstalled proxmox to try to make it work and still same problem

I also added a serial device for my virtual machine
when running qm terminal 100
starting serial terminal on interface serial0 (press Ctrl+O to exit)

running proxmox 6.1
running chrome browser

Code:
root@proxmox:~# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2
 
Last edited:

I do have Eset on one computer I was trying to use. Will try Firefox on a computer without Eset.
But I don’t understand how either of those things could stop qm terminal <vid> from working when it is run locally on the host (its a laptop running Proxmox so I can run vms without being connected to a network). And logically if running that command doesn’t work locally on the host then it won’t work through a browser?
 
In the end this was down to a culmination of problems.
1 - Eset was stopping proxmox from working on one computer.
2 - The VM had the wrong display set - I was setting up a vm with a git pull of an open source home assistant server - needed to be set to default display.
3 - Also the virtual machine wasn't happy with its connection to the DHCP server so it wasnt getting an ip address so I couldnt SSH directly into it.

Thanks for the help.
 
Hello,

Having same issue but with 6.2-4 version of proxmox . I am not using any firewall in windows nor any antivirus but having same issue, I even can not access the main host via console. same for all vms .

any one please help
 
same here its bs! I have eset and unchecked block encrypted comm protocol ssl v2 and disabled firewall tried using Chrome and edge with allowing all from my proxmox box such as Java pop ups etc nothing... broken! someone please help us!
 
same here its bs! I have eset and unchecked block encrypted comm protocol ssl v2 and disabled firewall tried using Chrome and edge with allowing all from my proxmox box such as Java pop ups etc nothing... broken! someone please help us!
please post your pveversion and the exact error message you get (also please open the failed task log and copy the whole output)
 
please post your pveversion and the exact error message you get (also please open the failed task log and copy the whole output)

error :
timed out waiting for client
TASK ERROR: command '/usr/bin/termproxy 5900 --path /nodes/proxmox --perm Sys.Console -- /bin/login -f root' failed: exit code 4

ive done a apt-get update / apt-get dist-upgrade and issue persists i do have internet connectivity on proxmox as I updated in shell via putty. no shells work within proxmox for even proxmox :/ this is an issue as im trying to install pfsense with no luck

root@proxmox:~# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-1
pve-kernel-helper: 6.2-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
 
For anyone that's coming here now. I had this same issue and the reason turned out that my cluster was not quorate. I intentionally turned off a couple of servers. I didn't expect it to bring down shell access but it did with a similar error message to the one from OP. Once I brought the cluster quorum, I can access the shell via GUI.