[SOLVED] Odd issue with updating certificates in Proxmox: "Valid" but "Insecure" in Chromium but not Firefox

[V3nom]

I placed a certificate I bough last year on my Proxmox host which was working. I then replaced it today with a new one, now when I check Chromium it says the certificate is valid, but "Not Secure". I checked Firefox and there it's valid and "Secure" so not marked in red that it's "Not Secure". I decided to put a backup back of my old certificate from last year and now I have the same issue as with the new one. The odd thing is I also placed a new certificate from the same provider on a Unifi device of mine and when I go to the url in Chromium the certificate is "Valid" and "Secure" there. So it seems to be something specific to Proxmox. Anybody have an idea of where to start looking for this, as I find this very confusing since both the old and new certificate now give "Valid" but "Insecure", even though the old certificate used to show "Valid" and "Secure"?

Valid but Insecure in Chromium but Valid and secure in Firefox

openssl s_client -connect pve.lan.feedmebits.nl:8006 -showcerts
Connecting to 2001:1c04:500a:9600:befc:e7ff:fe52:3b
CONNECTED(00000003)
depth=0 CN=pve.lan.feedmebits.nl
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 CN=pve.lan.feedmebits.nl
verify error:num=21:unable to verify the first certificate
verify return:1
depth=0 CN=pve.lan.feedmebits.nl
verify return:1

Valid and secure in Chromium and also Firefox.

openssl s_client -connect unifi.lan.feedmebits.nl:443 -showcerts
Connecting to 2001:1c04:500a:9600::1
CONNECTED(00000003)
depth=0 CN=unifi.lan.feedmebits.nl
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 CN=unifi.lan.feedmebits.nl
verify error:num=21:unable to verify the first certificate
verify return:1
depth=0 CN=unifi.lan.feedmebits.nl
verify return:1

 

[Onslow]

Hi, a brief Google search for "certificate valid but not secure" list many examples of a similar problem with Chrome or Chromium. Reasons can be various so I'm not quoting them here.
You can use trial and error method .

 

[V3nom]

The odd thing is I started a private browsing session in Chromium and there the certificate is both "Valid" and "Secure". So I decided to clear my browser cache and history, then it's the same problem again in Chromium.

Hi, a brief Google search for "certificate valid but not secure" list many examples of a similar problem with Chrome or Chromium. Reasons can be various so I'm not quoting them here.
You can use trial and error method .

Yeah I already did a search but was hoping someone would have an idea here.

 

[V3nom]

I found a difference between the old and new cert. Will ask the certificate provider if they have an idea.

 

[V3nom]

I tried another Chromium-based browser(Vivaldi), there was no problem there. So I figured it might be a caching issue. I rebooted my PC and voila now when opening Proxmox web-interface in Chromium I see "Valid" and "Secure" Really odd issue, as I've never come across a situation before where I had to reboot my PC before my web-browser saw the new certificate correctly.