VNCproxy error after change of hostname

Aug 2, 2020
27
3
23
68
When I installed the first PVE node, I left the hostname as PVE with a fixed IP on my subnet. Later on I decided to change the hostname to a proper one using hostnamectl.
DNS is updated accordingly, and I added PVE as a CNAME for backward compatibility.
But after doing that, I cannot connect any console to any VM

Nov 24 09:09:37 hp-srv00.xxx.se pvedaemon[313899]: starting vnc proxy UPID:pve:0004CA2B:08CAF008:6742DF41:vncproxy:106:root@pam:
Nov 24 09:09:38 hp-srv00.xxx.se pvedaemon[313899]: Failed to run vncproxy.

When changed back to PVE as actual hostname, everything started to work again. So what do I need to change in the VNC setup to allow the change to be done again?
/Anders
 

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!