[SOLVED] HTTPS certificate: our own certificate failed validation

ckx3009

New Member
Feb 18, 2014
21
0
1
Good morning,

on my Proxmox 5.2 cluster, following the guide at https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer) I replaced the certificates for the Web GUI with my own CA's certificates.
But I'm actually unable to start the VMs.

The error I get is:
Code:
kvm: -vnc unix:/var/run/qemu-server/115.vnc,x509,password: Failed to start VNC server: Our own certificate /etc/pve/local/pve-ssl.pem failed validation against /etc/pve/pve-root-ca.pem: The certificate hasn't got a known issuer

I've seen other topics about this issue but I don't seem to find the correct solution.

Now the guide says to use the fullchain.pem without the root CA.
I don't have any sub CA so the fullchain.pem in this case should only be composed by the certificate itself, correct?
Or do I need to also to remove or replace the /etc/pve/pve-root-ca.pem with my own root CA?

Thank you very much in advance!
Best regards
 
Good morning again,

afrer re-reading some topics I managed to solve the issue.
The guide correctly says to copy the key and pem files to a directory but, not finding the certificates already there I thought that the names were mistaken on the guide, so moved my certificate to /etc/pve/nodes/<node>/pve-ssl.pem and key instead of pveproxy-ssl.pem.

My mistake for not following the guide as it was written.

Thank you very much and best regards
 

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!