Public wildcard cert issues with Web GUI

Jun 8, 2024
2
0
1
So I have a public signed SSL cert (wildcard) that I use for my lab gear.

I know it works and the key is valid as it has been used on other web services (internally)

But when I put the CA-bundle and private key into the Web gui ... no luck.

I have the ca-bundle (root+intermediate), wildcard.crt, and private.key

ca-bundle.pem has 3 sections with pub certs.
wildcard.crt has just one section
private.key is just the one section

Every time I use the interface to drop in the files or copy/paste them manually, the web gui does not come back.

Response from another host:

Code:
[root@goofy ~]# curl -v https://proxmox.example.com:8006/
*   Trying 192.168.0.78:8006...
* Connected to proxmox.example.com (192.168.0.78) port 8006 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.0 (OUT), TLS header, Unknown (21):
* TLSv1.3 (OUT), TLS alert, decode error (562):
* error:0A000126:SSL routines::unexpected eof while reading
* Closing connection 0
curl: (35) error:0A000126:SSL routines::unexpected eof while reading

What am I missing? I tried with just the CA-bundle, CA-bundle+wildcard.pem as a single file (so 4 public certs are in there), and also just my wildcard cert
 

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!