noVNC Error 1006

pottsi

Active Member
Jan 18, 2016
11
0
41
33
Hi,

I've been trying to fix this issue for a while. I did a clean install to Proxmox 4.4-13 all went well. After setting up a new container and vm. i try to connect using the noVNC option. It looks to load but then disconnect, reconnects then disconnects again with error "Failed to connect to server (1006)"

Looking at System log i see:

Code:
Mar 19 18:34:21 prox.local.contractors.co.uk pveproxy[9767]: problem with client 151.225.149.107; ssl3_read_bytes: tlsv1 alert unknown ca
Mar 19 18:34:21 prox.local.contractors.co.uk pvedaemon[1557]: <root@pam> starting task UPID:prox:0000313C:0001B6F4:58CEC11D:vncproxy:104:root@pam:
Mar 19 18:34:21 prox.local.contractors.co.uk pvedaemon[12604]: starting vnc proxy UPID:prox:0000313C:0001B6F4:58CEC11D:vncproxy:104:root@pam:
Mar 19 18:34:22 prox.local.contractors.co.uk pvedaemon[1557]: <root@pam> end task UPID:prox:0000313C:0001B6F4:58CEC11D:vncproxy:104:root@pam: OK

I'm currently using the default SSL Certificate that was made on installing Proxmox.

Any idea what i should do?

Proxmox setup is:

Debian 8
Proxmox 4.4-13
Browser used. Chrome, Edge, Firefox

I've attempted to reinstall novnc-pve and rebooted the server and cleared web cache multiple times.

Regards.
 
what the output of pveversion -v
 
Code:
prox ~ # pveversion -v
proxmox-ve: 4.4-84 (running kernel: 4.4.44-1-pve)
pve-manager: 4.4-13 (running version: 4.4-13/7ea56165)
pve-kernel-4.4.44-1-pve: 4.4.44-84
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-109
pve-firmware: 1.1-10
libpve-common-perl: 4.0-94
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-1
pve-docs: 4.4-3
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-96
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
 
Hi i have the same problem :(
Hi Noovy,

It's a weird one, i actually fixed the issue by logging on to a machine i *Hadn't* cleaned the cache after updating ( i was luck enough to already be logged in) i click console on the old machine and it worked. Went back to test on the machine i had been using all night and it continued to work. I've not had an issue since.

I think it could be due to web-cache not clearing properly, but i'm not to sure.

Sorry i can't be of more help.

Regards,
Pottsi
 
It's not like that. I ran on 3 different computers.... i have this error on my task :
nc6: connection timed out
TASK ERROR: command '/bin/nc6 -l -p 5900 -w 10 -e '/usr/sbin/qm vncproxy 101 2>/dev/null'' failed: exit code 1
 
It's not like that. I ran on 3 different computers.... i have this error on my task :
nc6: connection timed out
TASK ERROR: command '/bin/nc6 -l -p 5900 -w 10 -e '/usr/sbin/qm vncproxy 101 2>/dev/null'' failed: exit code 1
if you get this error, you are not running the latest version
 

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!