I have a private CA I singe all certificates for my internal servers. All our browsers trust that CA. So I can access all my internal web sites without browser warning.
No I created a pve.mydomain.de certificate. And used the GUI to upload. But not the expected certificates are seen but a new pveproxy-ssl.pem with alternate names of my server name and my server IP Address, valid for one year and not for 2 as my created certificate.
The browser (Chrom) accepts the certificate as valid but the connection as unsecure.
Why, why a new certificate, why not for two years as I linke, why still the unsecure warning.
P.S. I can not use Lets Encrypt as my servers are not reachable from the internet and if the via reverse proxy.
Dont know why but suddendly my browser does not only accept the certificate but also recognizes the connection as secure, so everything is fine
No I created a pve.mydomain.de certificate. And used the GUI to upload. But not the expected certificates are seen but a new pveproxy-ssl.pem with alternate names of my server name and my server IP Address, valid for one year and not for 2 as my created certificate.
The browser (Chrom) accepts the certificate as valid but the connection as unsecure.
Why, why a new certificate, why not for two years as I linke, why still the unsecure warning.
P.S. I can not use Lets Encrypt as my servers are not reachable from the internet and if the via reverse proxy.
Dont know why but suddendly my browser does not only accept the certificate but also recognizes the connection as secure, so everything is fine
Last edited: