VNC connection timed out

J

jleiss

Member
Sep 22, 2017
11
0
6
56
Unable to connect with VNC.. Brand new install from USB, and nothing else installed but updates

this is what I am seeing in syslog

Nov 15 20:50:20 lorien systemd[1]: Started User Manager for UID 0.
Nov 15 20:50:20 lorien systemd[1]: Started Session 1 of user root.
Nov 15 20:50:40 lorien systemd-timesyncd[1164]: Synchronized to time server for the first time 196.200.160.123:123 (2.debian.pool.ntp.org).
Nov 15 20:50:45 lorien pvedaemon[1602]: <root@pam> successful auth for user 'root@pam'
Nov 15 20:50:46 lorien pvedaemon[1601]: <root@pam> starting task UPID:lorien:000006C5:0000148F:5FB20526:vncproxy:100:root@pam:
Nov 15 20:50:46 lorien pvedaemon[1733]: starting vnc proxy UPID:lorien:000006C5:0000148F:5FB20526:vncproxy:100:root@pam:
Nov 15 20:50:53 lorien pvedaemon[1737]: starting vnc proxy UPID:lorien:000006C9:0000175F:5FB2052D:vncproxy:100:root@pam:
Nov 15 20:50:53 lorien pvedaemon[1602]: <root@pam> starting task UPID:lorien:000006C9:0000175F:5FB2052D:vncproxy:100:root@pam:
Nov 15 20:50:56 lorien pvedaemon[1733]: connection timed out
Nov 15 20:50:56 lorien pvedaemon[1601]: <root@pam> end task UPID:lorien:000006C5:0000148F:5FB20526:vncproxy:100:root@pam: connection timed out
Nov 15 20:51:00 lorien systemd[1]: Starting Proxmox VE replication runner...
Nov 15 20:51:01 lorien systemd[1]: pvesr.service: Succeeded.
Nov 15 20:51:01 lorien systemd[1]: Started Proxmox VE replication runner.
Nov 15 20:51:03 lorien pvedaemon[1737]: connection timed out
Nov 15 20:51:03 lorien pvedaemon[1602]: <root@pam> end task UPID:lorien:000006C9:0000175F:5FB2052D:vncproxy:100:root@pam: connection timed out
Nov 15 20:51:03 lorien pvedaemon[1767]: start VM 100: UPID:lorien:000006E7:00001B57:5FB20537:qmstart:100:root@pam:
Nov 15 20:51:03 lorien pvedaemon[1602]: <root@pam> starting task UPID:lorien:000006E7:00001B57:5FB20537:qmstart:100:root@pam:
Nov 15 20:51:03 lorien systemd[1]: Created slice qemu.slice.
Nov 15 20:51:03 lorien systemd[1]: Started 100.scope.
Nov 15 20:51:04 lorien pvedaemon[1602]: <root@pam> starting task UPID:lorien:000006F9:00001BD6:5FB20538:vncproxy:100:root@pam:
Nov 15 20:51:04 lorien pvedaemon[1785]: starting vnc proxy UPID:lorien:000006F9:00001BD6:5FB20538:vncproxy:100:root@pam:
Nov 15 20:51:05 lorien systemd-udevd[1762]: Using default interface naming scheme 'v240'.
Nov 15 20:51:05 lorien systemd-udevd[1762]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 15 20:51:05 lorien systemd-udevd[1762]: Could not generate persistent MAC address for tap100i0: No such file or directory
Nov 15 20:51:05 lorien kernel: [ 71.543589] device tap100i0 entered promiscuous mode
Nov 15 20:51:05 lorien kernel: [ 71.549553] vmbr0: port 2(tap100i0) entered blocking state
Nov 15 20:51:05 lorien kernel: [ 71.549554] vmbr0: port 2(tap100i0) entered disabled state
Nov 15 20:51:05 lorien kernel: [ 71.549614] vmbr0: port 2(tap100i0) entered blocking state
Nov 15 20:51:05 lorien kernel: [ 71.549615] vmbr0: port 2(tap100i0) entered forwarding state
Nov 15 20:51:05 lorien pvedaemon[1602]: <root@pam> end task UPID:lorien:000006E7:00001B57:5FB20537:qmstart:100:root@pam: OK
Nov 15 20:51:05 lorien pvedaemon[1830]: starting vnc proxy UPID:lorien:00000726:00001C2C:5FB20539:vncproxy:100:root@pam:
Nov 15 20:51:05 lorien pvedaemon[1602]: <root@pam> starting task UPID:lorien:00000726:00001C2C:5FB20539:vncproxy:100:root@pam:
Nov 15 20:51:14 lorien pvedaemon[1785]: connection timed out
Nov 15 20:51:14 lorien pvedaemon[1602]: <root@pam> end task UPID:lorien:000006F9:00001BD6:5FB20538:vncproxy:100:root@pam: connection timed out
Nov 15 20:51:15 lorien pvedaemon[1830]: connection timed out
Nov 15 20:51:15 lorien pvedaemon[1602]: <root@pam> end task UPID:lorien:00000726:00001C2C:5FB20539:vncproxy:100:root@pam: connection timed out
root@lorien:~#


here is my pveversion output

root@lorien:~# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-1
pve-kernel-helper: 6.2-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
 
Hi,

Did you clear Browser cache? - if yes please try the following commands:
Generate new certificate
Bash: 
pvecm updatecerts --force

Restart pvedaemon and pveproxy
Bash: 
systemctl restart pvedaemon.service
systemctl restart pveproxy.service
 
I had but I tried it again, no change.. Here are the logs from syslog during this

Nov 16 07:00:53 lorien kernel: [ 150.247180] device tap100i0 entered promiscuous mode
Nov 16 07:00:53 lorien kernel: [ 150.253303] vmbr0: port 2(tap100i0) entered blocking state
Nov 16 07:00:53 lorien kernel: [ 150.253304] vmbr0: port 2(tap100i0) entered disabled state
Nov 16 07:00:53 lorien kernel: [ 150.253366] vmbr0: port 2(tap100i0) entered blocking state
Nov 16 07:00:53 lorien kernel: [ 150.253366] vmbr0: port 2(tap100i0) entered forwarding state
Nov 16 07:00:53 lorien pvedaemon[1514]: <root@pam> end task UPID:lorien:00000754:000039CB:5FB29422:qmstart:100:root@pam: OK
Nov 16 07:00:53 lorien pvedaemon[1514]: <root@pam> starting task UPID:lorien:00000782:00003AE4:5FB29425:vncproxy:100:root@pam:
Nov 16 07:00:53 lorien pvedaemon[1922]: starting vnc proxy UPID:lorien:00000782:00003AE4:5FB29425:vncproxy:100:root@pam:
Nov 16 07:01:00 lorien systemd[1]: Starting Proxmox VE replication runner...
Nov 16 07:01:01 lorien systemd[1]: pvesr.service: Succeeded.
Nov 16 07:01:01 lorien systemd[1]: Started Proxmox VE replication runner.
Nov 16 07:01:01 lorien pvedaemon[1898]: connection timed out
Nov 16 07:01:01 lorien pvedaemon[1515]: <root@pam> end task UPID:lorien:0000076A:00003A44:5FB29423:vncproxy:100:root@pam: connection timed out
Nov 16 07:01:03 lorien pvedaemon[1922]: connection timed out
Nov 16 07:01:03 lorien pvedaemon[1514]: <root@pam> end task UPID:lorien:00000782:00003AE4:5FB29425:vncproxy:100:root@pam: connection timed out
Nov 16 07:01:23 lorien pvecm[2633]: got inotify poll request in wrong process - disabling inotify
Nov 16 07:01:32 lorien systemd[1]: Stopping PVE API Daemon...
Nov 16 07:01:32 lorien pvedaemon[1512]: received signal TERM
Nov 16 07:01:32 lorien pvedaemon[1512]: server closing
Nov 16 07:01:32 lorien pvedaemon[1514]: worker exit
Nov 16 07:01:32 lorien pvedaemon[1513]: worker exit
Nov 16 07:01:32 lorien pvedaemon[1512]: worker 1513 finished
Nov 16 07:01:32 lorien pvedaemon[1512]: worker 1514 finished
Nov 16 07:01:32 lorien pvedaemon[1512]: worker 1515 finished
Nov 16 07:01:32 lorien pvedaemon[1512]: server stopped
Nov 16 07:01:33 lorien pvedaemon[2713]: worker exit
Nov 16 07:01:33 lorien systemd[1]: pvedaemon.service: Succeeded.
Nov 16 07:01:33 lorien systemd[1]: Stopped PVE API Daemon.
Nov 16 07:01:33 lorien systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
Nov 16 07:01:33 lorien systemd[1]: Starting PVE API Daemon...
Nov 16 07:01:34 lorien pvedaemon[2723]: starting server
Nov 16 07:01:34 lorien pvedaemon[2723]: starting 3 worker(s)
Nov 16 07:01:34 lorien pvedaemon[2723]: worker 2724 started
Nov 16 07:01:34 lorien pvedaemon[2723]: worker 2725 started
Nov 16 07:01:34 lorien pvedaemon[2723]: worker 2726 started
Nov 16 07:01:34 lorien systemd[1]: Started PVE API Daemon.
Nov 16 07:01:34 lorien systemd[1]: Stopping PVE API Proxy Server...
Nov 16 07:01:34 lorien pveproxy[1522]: received signal TERM
Nov 16 07:01:34 lorien pveproxy[1522]: server closing
Nov 16 07:01:34 lorien pveproxy[1525]: worker exit
Nov 16 07:01:34 lorien pveproxy[1523]: worker exit
Nov 16 07:01:34 lorien pveproxy[1522]: worker 1525 finished
Nov 16 07:01:34 lorien pveproxy[1522]: worker 1523 finished
Nov 16 07:01:34 lorien pveproxy[1522]: worker 1524 finished
Nov 16 07:01:34 lorien pveproxy[1522]: server stopped
Nov 16 07:01:35 lorien systemd[1]: pveproxy.service: Succeeded.
Nov 16 07:01:35 lorien systemd[1]: Stopped PVE API Proxy Server.
Nov 16 07:01:35 lorien systemd[1]: Starting PVE API Proxy Server...
Nov 16 07:01:36 lorien pveproxy[2757]: starting server
Nov 16 07:01:36 lorien pveproxy[2757]: starting 3 worker(s)
Nov 16 07:01:36 lorien pveproxy[2757]: worker 2758 started
Nov 16 07:01:36 lorien pveproxy[2757]: worker 2759 started
Nov 16 07:01:36 lorien pveproxy[2757]: worker 2760 started
Nov 16 07:01:36 lorien systemd[1]: Started PVE API Proxy Server.
Nov 16 07:02:00 lorien systemd[1]: Starting Proxmox VE replication runner...
Nov 16 07:02:01 lorien systemd[1]: pvesr.service: Succeeded.
Nov 16 07:02:01 lorien systemd[1]: Started Proxmox VE replication runner.
Nov 16 07:02:19 lorien pvedaemon[2724]: <root@pam> successful auth for user 'root@pam'
Nov 16 07:02:20 lorien pvedaemon[2726]: <root@pam> starting task UPID:lorien:00000B2E:00005CDE:5FB2947C:vncproxy:100:root@pam:
Nov 16 07:02:20 lorien pvedaemon[2862]: starting vnc proxy UPID:lorien:00000B2E:00005CDE:5FB2947C:vncproxy:100:root@pam:
Nov 16 07:02:28 lorien pvedaemon[2724]: <root@pam> starting task UPID:lorien:00000B45:0000602E:5FB29484:qmstop:100:root@pam:
Nov 16 07:02:28 lorien pvedaemon[2885]: stop VM 100: UPID:lorien:00000B45:0000602E:5FB29484:qmstop:100:root@pam:
Nov 16 07:02:29 lorien kernel: [ 246.139477] vmbr0: port 2(tap100i0) entered disabled state
Nov 16 07:02:29 lorien qmeventd[1102]: read: Connection reset by peer
Nov 16 07:02:29 lorien systemd[1]: 100.scope: Succeeded.
Nov 16 07:02:29 lorien qmeventd[1102]: Starting cleanup for 100
Nov 16 07:02:29 lorien qmeventd[1102]: trying to acquire lock...
Nov 16 07:02:29 lorien qmeventd[1102]: OK
Nov 16 07:02:29 lorien qmeventd[1102]: Finished cleanup for 100
Nov 16 07:02:29 lorien pvedaemon[2724]: <root@pam> end task UPID:lorien:00000B45:0000602E:5FB29484:qmstop:100:root@pam: OK
Nov 16 07:02:30 lorien pvedaemon[2862]: connection timed out
Nov 16 07:02:30 lorien pvedaemon[2726]: <root@pam> end task UPID:lorien:00000B2E:00005CDE:5FB2947C:vncproxy:100:root@pam: connection timed out
Nov 16 07:02:39 lorien pvedaemon[2726]: <root@pam> starting task UPID:lorien:00000B6B:0000641D:5FB2948E:qmstart:100:root@pam:
Nov 16 07:02:39 lorien pvedaemon[2923]: start VM 100: UPID:lorien:00000B6B:0000641D:5FB2948E:qmstart:100:root@pam:
Nov 16 07:02:39 lorien systemd[1]: Started 100.scope.
Nov 16 07:02:39 lorien systemd-udevd[2935]: Using default interface naming scheme 'v240'.
Nov 16 07:02:39 lorien systemd-udevd[2935]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 16 07:02:39 lorien systemd-udevd[2935]: Could not generate persistent MAC address for tap100i0: No such file or directory
Nov 16 07:02:39 lorien kernel: [ 256.565003] device tap100i0 entered promiscuous mode
Nov 16 07:02:39 lorien kernel: [ 256.571111] vmbr0: port 2(tap100i0) entered blocking state
Nov 16 07:02:39 lorien kernel: [ 256.571112] vmbr0: port 2(tap100i0) entered disabled state
Nov 16 07:02:39 lorien kernel: [ 256.571172] vmbr0: port 2(tap100i0) entered blocking state
Nov 16 07:02:39 lorien kernel: [ 256.571173] vmbr0: port 2(tap100i0) entered forwarding state
Nov 16 07:02:39 lorien pvedaemon[2726]: <root@pam> end task UPID:lorien:00000B6B:0000641D:5FB2948E:qmstart:100:root@pam: OK
Nov 16 07:02:40 lorien pvedaemon[2725]: <root@pam> starting task UPID:lorien:00000B9E:00006499:5FB29490:vncproxy:100:root@pam:
Nov 16 07:02:40 lorien pvedaemon[2974]: starting vnc proxy UPID:lorien:00000B9E:00006499:5FB29490:vncproxy:100:root@pam:
Nov 16 07:02:40 lorien pvedaemon[2724]: <root@pam> starting task UPID:lorien:00000BA0:000064C6:5FB29490:vncproxy:100:root@pam:
Nov 16 07:02:40 lorien pvedaemon[2976]: starting vnc proxy UPID:lorien:00000BA0:000064C6:5FB29490:vncproxy:100:root@pam:
Nov 16 07:02:50 lorien pvedaemon[2974]: connection timed out
Nov 16 07:02:50 lorien pvedaemon[2725]: <root@pam> end task UPID:lorien:00000B9E:00006499:5FB29490:vncproxy:100:root@pam: connection timed out
Nov 16 07:02:50 lorien pvedaemon[2976]: connection timed out
Nov 16 07:02:50 lorien pvedaemon[2724]: <root@pam> end task UPID:lorien:00000BA0:000064C6:5FB29490:vncproxy:100:root@pam: connection timed out
 
When I found I didn't have the right rep in sources.list I reinstalled and put in the correct repository and updated everything, the issue hasn't gone away though I am still unable to connect with VNC.

Here is an updated pveversion

root@lorien:/archive/vmstorage/record# pveversion -v
proxmox-ve: 6.2-2 (running kernel: 5.4.65-1-pve)
pve-manager: 6.2-15 (running version: 6.2-15/48bd51b6)
pve-kernel-5.4: 6.2-7
pve-kernel-helper: 6.2-7
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-4
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-10
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.1-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.3-10
pve-cluster: 6.2-1
pve-container: 3.2-2
pve-docs: 6.2-6
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-6
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-19
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve2
 
Could you post output of cat /var/log/daemon.log | grep -e pveproxy -e pvedaemon command, please the output between [CODE][/CODE]
 
appears that might be the case, I know firewall is disabled on both machines but I spun up a new VM and connected and it worked fine. I'll do some more troubleshooting here.
 
on 2 machines it didn't but it did on a 3rd so I think it's something more specific to those machines I will have to examine further.
 
I would like to give my two cents here as I have just witnessed this error, too.

Currently I am accessing my Proxmox installation at home via an ssh tunnel from a macOS Big Sur (11.7.4) and the integrated Safari Browser - not working, all Console connections are failing.
After switching to Firefox it's working like a charme without any changes.
 
  • Like
Reactions: a_running_cat
spintike said:
I would like to give my two cents here as I have just witnessed this error, too.

Currently I am accessing my Proxmox installation at home via an ssh tunnel from a macOS Big Sur (11.7.4) and the integrated Safari Browser - not working, all Console connections are failing.
After switching to Firefox it's working like a charme without any changes.
Click to expand...
Yes. Does anyone know why? Firefox works well, but Chrome doesn't.
I use nginx proxy vnc.
PVE 8.2.4, Novnc 1.4.0
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom