[SOLVED] Proxmox GUI not reachable after activating Qemu-guest-agent


Apr 28, 2018
Hello guys, as the title already says my Proxmox GUI is not reachable after activating Qemu-guest-agent for a VM as mentioned here: https://pve.proxmox.com/wiki/Qemu-guest-agent

Before that, I installed virtio-win-0.1.190.iso (https://fedorapeople.org/groups/vir...ownloads/archive-virtio/virtio-win-0.1.190-1/) on my Windows Server 2012R2 machine. After that, I did a shutdown of my Windows Server, enabled the Qemu-guest-agent setting in Proxmox and started the VM again.

Now my Proxmox GUI is not reachable (browser says connection timed out). With and without port :8006 (I enabled access via port 443).

Already did a service pveproxy restart, but did not help. Do you have any more things to do without doing a full reboot of my host? Thanks!

If this helps:
# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.3-6 (running version: 6.3-6/2184247e)
pve-kernel-5.4: 6.3-8
pve-kernel-helper: 6.3-8
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.103-1-pve: 5.4.103-1
pve-kernel-5.4.78-2-pve: 5.4.78-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.8
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.12-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-9
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-5
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-10
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
Last edited:
Sorry for posting too early, I checked the logs in /var/log/daemon.log now and found following:

Apr 14 12:17:24 HOST pveproxy[29641]: /etc/pve/local/pve-ssl.pem: failed to use local certificate chain (cert_file or cert) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1775.
Apr 14 12:17:26 HOST pvestatd[1091]: mkdir /storage: File exists at /usr/share/perl5/PVE/Storage/DirPlugin.pm line 136.

After regenerating the SSL certificate and restarting, it did work again. Interesting that the error happened at the exact same time when starting my VM with Qemu. So that error was not because of the client-agent!


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!