[SOLVED] noVNC - server refusing connection

[Nifelheim]

Hi all,

having gotten my first Proxmox Server up and running, I am eagerly playing with my new setup and have created a number of (Linux Desktop) VMs to test.

Within Proxmox, I have no problem accessing the desktop (built in noVNC), but when I try it from my Windows 10 PC (using either the EDGE or CHROME browser or TightVNC Viewer), I keep getting a "connection refused" message. Using IPTRAF on the host, I can see that the requests are coming in.

I've configured the respective VM config file to include (based on this article) :

args: -vnc 0.0.0.0:77

Any help would be appreciated.

Cheers!

 

[oguz]

hi,

what is your pveversion -v output?

I've configured the respective VM config file to include

did you restart the VM afterwards? try doing a "Reboot" on the PVE GUI (not from reboot inside the VM, that won't apply the settings)

also are you connecting to the correct port for VNC?

is the PVE firewall enabled?

 

[Nifelheim]

Thank you for your reply !

I did reboot from the pve-GUI after changing the conf.

I am trying to connect to the port 5988 (88 is the number I had used).

When I look at the firewall (from pve GUI), I am not seeing any entry.

pveversion shows:

proxmox-ve: 7.1-1 (running kernel: 5.15.7-1-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
pve-kernel-5.15: 7.1-7
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.15.7-1-pve: 5.15.7-1
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.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
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-4
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.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.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.1-pve3

 

[Nifelheim]

Currently, the EDGE and CHROME browsers gives me an "ERR_INVALID_HTTP_RESPONSE" when using HTTP
or an "ERR_SSL_PROTOCOL_ERROR", if I try HTTPS ...

 

[oguz]

Currently, the EDGE browser gives me an "ERR_INVALID_HTTP_RESPONSE" when using HTTP
or an "ERR_SSL_PROTOCOL_ERROR", if I try HTTPS ...

i'm not sure what you mean... the vnc option starts a regular VNC service, not noVNC. (so i'm not sure how you'd access it with your browser without a plugin or something).

if you try to access it with a regular VNC client (e.g. tightvnc viewer like you said) and use port 5988 you still get connection refused?

When I look at the firewall (from pve GUI), I am not seeing any entry.

but is it enabled? check with pve-firewall status
it might be blocking the VNC port if you didn't add an allow rule for it.

 

[Nifelheim]

Thank you!
I had not tried the TightVNC viewer after I rebooted from the pve-GUI ... now everything works with the TightVNC (except that it has a US keyboard layout, even though the VM has defined a German keyboard ... but I'm sure I'll figure that out).