"noVNC - failed to connect to server" on Chrome or Edge Chromium or Brave, works on Firefox

nikin

New Member
Mar 2, 2022
2
0
1
36
Hi
FF works fine, but opening console with other browsers does fail.
I do use selfsigned SSL so wonder if that might be the problem. Maybe Chrome and Edge does deployed more strict policy for WSS connection i.e. valid SSL is required. Until recently it used to work fine with all browsers.
I do not use proxy.
Task viewer shows :
Code:
TASK ERROR: command '/usr/bin/termproxy 5901 --path /nodes/node-02 --perm Sys.Console -- /usr/bin/ssh -e none -t 198.96.0.147 -- /bin/login -f root' failed: exit code 1

Browser dev tools does show: "app.js?ver=1.2.0-3:10807 WebSocket connection to 'wss://xx.x.x.x:8006/api2/json/nodes/node-01/qemu/150/vncwebsocket?port=5900&vncticket=PVEVNC%3A621F9B1F%3A%3AMJI%2FiEG8ar22xCP%2BAgOePfmX9K34YgJmyZz6frIB%2F26GEWiTcb%2F6TxI8ezULTOHs8uf%2B7XMkBz%2Fvt8%2' failed:"
 

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!