[SOLVED] Error when opening Console PVE

[adhiete]

Hi, this is my first post in here. I have an error when opening console on web gui. I only got a blank page everytime access console from GUI.
When opening container or even opening the proxmox itself.

timed out waiting for client
TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/100 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole100 -r winch -z lxc-console -n 100 -e -1' failed: exit code 4

Here's my pve version
proxmox-ve: 6.0-2 (running kernel: 5.0.21-1-pve)
pve-manager: 6.0-6 (running version: 6.0-6/c71f879f)
pve-kernel-5.0: 6.0-7 pve-kernel-helper: 6.0-7 pve-kernel-5.0.21-1-pve: 5.0.21-1
pve-kernel-5.0.18-1-pve: 5.0.18-3 pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1
corosync: 3.0.2-pve2 criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.11-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-4
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-7
libqb0: 1.0.5-1 lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-64 lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-7
pve-cluster: 6.0-5 pve-container: 3.0-5
pve-docs: 6.0-4 pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7 pve-firmware: 3.0-2
pve-ha-manager: 3.0-2 pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-5 pve-xtermjs: 3.13.2-1
qemu-server: 6.0-7 smartmontools: 7.0-pve2
spiceterm: 3.1-1 vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve2

Any suggestion how to fix this? I think i can't access after update the packages.

 

[adhiete]

I solved it by myself. When i moved to Firefox with updated java 8. All fixed. Thank you.

 

[Dominic]

When i moved to Firefox with updated java 8

Did you have an older version of Firefox before or some other browser such as chrome?

I'm asking as someone reported the same problem previously.

 

[janiali]

Hello,

Seems like this is not the solution, because it was working fine with same browser same version of proxmox, but it suddenly stopped working . to me it was a reboot on the server after that this issue started.

to proxmox team it is request to try to find this issue . let me know if need any information from logs etc.

Thank you

 

[PeterRoux]

I am seeing same issues with latest firefox browser on Ubuntu 20.04. What I have noticed is that if I open a spice against one of the guests then this sometimes gets novnc working (around 50% of the time). But often only solution seems to be to reboot proxmox.

I have done the following too which was proposed as a solution:

pvecm updatecerts --force
systemctl restart pvedaemon.service
systemctl restart pveproxy.service

 

[bagginses]

In case it helps anyone I was getting this error from the shell but only when accessing the webui through my reverse proxy, I only have one node configured. Enabling web sockets support in the proxy host configuration fixed the issue for me.

 

[J-dub]

In case it helps anyone I was getting this error from the shell but only when accessing the webui through my reverse proxy, I only have one node configured. Enabling web sockets support in the proxy host configuration fixed the issue for me.

Actually - just looked and have that setting enabled already (it's in your OPNsense --> Nginx --> HTTP(s) --> Locations --> location name --> Enable Advanced option --> Scroll down... for those looking for it).
It might be from response buffering however - so I disabled those. We shall see!

 

[J-dub]

Actually - just looked and have that setting enabled already (it's in your OPNsense --> Nginx --> HTTP(s) --> Locations --> location name --> Enable Advanced option --> Scroll down... for those looking for it).
It might be from response buffering however - so I disabled those. We shall see!

Nope! Maybe it's the IPS or the WAF... who knows.
SSH from my terminal is still better in every way, so I'm not to interested to dig deeper.