Console -> noVNC - Failed to connect to server

U

ursus

New Member
Oct 26, 2021
10
1
3
55
Hi

I have the newest version of ProxMox installed (7.0-14+1) - I did not upgrade but have installed all updated packages. I am getting the dreaded noVNC error in all the browsers that I have (I have tried Mac: Safari, Chrome and Firefox. Windows: Chrome and Firefix). This is not normally a problem as I can just SSH to the machines and work that way, no real need for the console. I would now like to install a new Debian VM and cannot connect to install - major problem! I have tried to reboot the Proxmox server i.e. restarted the Hardware but even this did not help. I have read in the forums that something similar happened if you updated from 5 to 6 without doing some preliminary steps, but I started with 7.

Thank you for any help given
ursus
 
Hi,

ursus said:
I have the newest version of ProxMox installed (7.0-14+1) - I did not upgrade but have installed all updated packages.
Click to expand...
Are you mean that you installed the updated packages manually or using apt?

Could you please post the output of pveversion -v. However, did you try to renew the certificate for your PVE with pvecm updatecerts -f command?
 
Hi.

Yes, I installed and updated the packages manually.

here is the output from: pveversion -v

Code: 
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_TERMINAL = "iTerm2",
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
proxmox-ve: 7.0-2 (running kernel: 5.11.22-7-pve)
pve-manager: 7.0-15 (running version: 7.0-15/4a1f720f)
pve-kernel-helper: 7.1-4
pve-kernel-5.11: 7.0-10
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-6-pve: 5.11.22-11
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
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.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-7
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.13-1
proxmox-backup-file-restore: 2.0.13-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.4-1
pve-cluster: 7.0-5
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.1.0-1
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-19
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3

and the result of pvecm updatecerts -f:

Code: 
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_TERMINAL = "iTerm2",
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
(re)generate node files
generate new node certificate
merge authorized SSH keys and known hosts

and the updatecerts command did not change my situation!

Cheers
Ursus
 
Last edited:
What says journalctl -f during opening the noVNC?
Did you try to stop/disable the firewall to see if the issue is from it?
 
I have reinstalled the Proxmox server and now all is well. Thank you for helping but I needed my VMs during the weekend Should this happen again I will report back here!
 
HI guys,
I have the same issue with the new Ver. 7.1-10 especially with FreeNas11.3 / TrueNas12u8 VM ( i have tried both )
I noticed that after adding the PCI Device Passthrough of the LSI raid card on the Truenas VM Hardware section the VNC won't start, if i remove the PCI Device , the Truenass boot o.k but i won't see my drives.

before upgrading to the new Proxmox Ver ( new install from scratch ) i had Proxmox 6.3.3 Ver with Freenas 11.3 working grate for a Year+ now
even though my Prec h710 Raid card isn't on IT mode ( i just configured each of the 4 SAS/SATA 2 TB drives as Raid 0 on different Virtual group for each Drive )

Specs: Del T320 / 96 GB ram
CPU: 20 x Intel(R) Xeon(R) CPU E5-2470 v2 @ 2.40GHz (1 Socket )
Kernel Version : Linux 5.13.19-4-pve #1 SMP PVE 5.13.19-8 (Mon, 31 Jan 2022 10:09:37 +0100)
PVE Manager Version: pve-manager/7.1-10/6ddebafe

needless to say the my CPU support IOMMU
All VTd on Bios are enabled

On Proxmox pve:

on: /etc/default/grub
Code: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on"

on: /etc/modules
Code: 
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd


Code: 
root@vm-host-1:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-9
pve-kernel-5.13: 7.1-7
pve-kernel-5.13.19-4-pve: 5.13.19-8
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
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.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-1
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1

output of ( journalctl -f ) during VM starts

Code: 
root@vm-host-1:~#  journalctl -f
-- Journal begins at Sat 2022-02-05 20:38:46 IST. --
Feb 06 23:04:35 vm-host-1 systemd-logind[2073]: New session 4 of user root.
Feb 06 23:04:35 vm-host-1 systemd[1]: Started Session 4 of user root.
Feb 06 23:05:16 vm-host-1 pvedaemon[21021]: start VM 102: UPID:vm-host-1:0000521D:00028109:6200380C:qmstart:102:root@pam:
Feb 06 23:05:16 vm-host-1 pvedaemon[2821]: <root@pam> starting task UPID:vm-host-1:0000521D:00028109:6200380C:qmstart:102:root@pam:
Feb 06 23:05:16 vm-host-1 pvedaemon[21021]: Cannot bind 0000:08:00.0 to vfio
Feb 06 23:05:16 vm-host-1 pvedaemon[2821]: <root@pam> end task UPID:vm-host-1:0000521D:00028109:6200380C:qmstart:102:root@pam: Cannot bind 0000:08:00.0 to vfio
Feb 06 23:05:18 vm-host-1 pveproxy[2846]: worker exit
Feb 06 23:05:18 vm-host-1 pveproxy[2843]: worker 2846 finished
Feb 06 23:05:18 vm-host-1 pveproxy[2843]: starting 1 worker(s)
Feb 06 23:05:18 vm-host-1 pveproxy[2843]: worker 21098 started

lspci:
Code: 
08:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS 2208 [Thunderbolt] (rev 05)

Any ideas what is wrong?

Thanks
Gil
 
I did have the following problem as well -> I setup a self signed cert to access the machine (proxmox.home.local) and I have the problem whenever I use this link -> if I logon directly using the IP the VPN works perfectly...
 
ursus said:
I did have the following problem as well -> I setup a self signed cert to access the machine (proxmox.home.local) and I have the problem whenever I use this link -> if I logon directly using the IP the VPN works perfectly...
Click to expand...
Thanks, I was having the same problem. Did you figure out how to make it work with your custom certificate? I'm guessing the certificate needs to be added to pve-proxy and not just whatever reverse proxy we're using (I use nginx-proxy-manager)
 
You must log in or register to reply here.
Top Bottom