[SOLVED] Failed to start VNC server: The server Certificate /etc/pve/local/pve-ssl.pem is not yet active

pizza

Renowned Member
Nov 7, 2015
96
8
73
I have 2 Proxmox 4.1 with the latest updates (feb,10) in a cluster freshly setup

After creater a VM, the VM won't start:

Running as unit 100.scope.
kvm: -vnc unix:/var/run/qemu-server/100.vnc,x509,password: Failed to start VNC server: The server certificate /etc/pve/local/pve-ssl.pem is not yet active.
 
Solved, now the VM starts, maybe it take some time for a freshly setup cluster?
 
Hi,

i have the same problem with a fresh install
the problem that the certificat has generate into the future (+ 12 hours)
So i don't start a VM when the certificate become valide (i wait 12 Hours)

i install proxmox with iso proxmox-ve_4.1-2f9650d4-21
with previous version the problem not exist
 
You can regenerate the node certificate with pvecm:
Code:
pvecm updatecerts -f

If you need to regenerate the cluster CA certificate as well, you need to delete it first:
Code:
rm /etc/pve/priv/pve-root-ca.key /etc/pve/pve-root-ca.pem
and then run the pvecm command on all nodes of your cluster.

If you could answer the following questions, it might help us to reproduce this issue and fix it:
  1. Did you install on baremetal or under some other hypervisor?
  2. Did you have internet access during the installation?
  3. Was your RTC set to UTC or to your local time zone prior to the installation?
  4. What is the output of "timedatectl" now?
  5. Are certificates regenerated using the above command also affected by this issue, or only those created during the installation?
We have only experienced this issue sometimes when installing in a VM where the hypervisor set the RTC of the VM to the hosts local time instead of the expected UTC.
 
I have install only One machine with the iso 4.1
I have internet connection (DHCP with ntp info)
i didnt't set RTC time on bios setup

root@phy1:~# timedatectl
Local time: jeu. 2016-03-10 14:20:51 CET
Universal time: jeu. 2016-03-10 13:20:51 UTC
RTC time: jeu. 2016-03-10 13:20:51
Time zone: Europe/Paris (CET, +0100)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: no
Last DST change: DST ended at
dim. 2015-10-25 02:59:59 CEST
dim. 2015-10-25 02:00:00 CET
Next DST change: DST begins (the clock jumps one hour forward) at
dim. 2016-03-27 01:59:59 CET
dim. 2016-03-27 03:00:00 CEST

Yes above commmand solve the issue.

Thanks U
 
Just to clarify - this was a baremetal install?
 
did you install directly on a physical machine, or inside some (other) virtualization product?
 

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!