Local_certs gets "certificate invalid "

$ caddy version
v2.2.1 h1:Q62GWHMtztnvyRU+KPOpw6fNfeCD3SkwH7SfT1Tgt2c=

I am wondering if this is normal and not to worry about it, or if this is a bug of sorts with local_certs…

image

What other criteria do you need to know?

There are a few reasons this could be happening, most likely something to do with your setup or system; less likely to be a bug in Caddy. Browsers do weird things. How can we reproduce the error?

I am going to see if I can reproduce it on a clean VM (Ubunto 20.04)

I created a VM and installed and the local certificate is getting the same issue.

I am wonder if it’s this?
image

When it’s “localhost”, shouldn’t it be “Not Critical”? I don’t know…

No, the certificate is correct.

Is Caddy’s root cert in your system trust store?

Nov 18 13:08:04 FLEX-5 caddy[2182]: {"level":"warn","ts":1605730084.79021,"logger":"pki.ca.local","msg":"installing root certificate (you might be prompted for password)","path":"storage:pki/authorities/local/root.crt"}
Nov 18 13:08:04 FLEX-5 caddy[2182]: 2020/11/18 13:08:04 define JAVA_HOME environment variable to use the Java trust
Nov 18 13:08:04 FLEX-5 caddy[2182]: 2020/11/18 13:08:04 not NSS security databases found
Nov 18 13:08:04 FLEX-5 sudo[5506]: pam_unix(sudo:auth): conversation failed
Nov 18 13:08:04 FLEX-5 sudo[5506]: pam_unix(sudo:auth): auth could not identify password for [caddy]
Nov 18 13:08:04 FLEX-5 caddy[2182]: {"level":"error","ts":1605730084.795199,"logger":"pki.ca.local","msg":"failed to install root certificate","error":"failed to execute sudo: exit status 1","certificate_file":"storage:pki/authorities/local/root.crt"}

But, I have verified it is in the system root store

I am not sure what happened, but Chrome is no longer saying it’s invalid :man_shrugging:

90% of the time it ends up being a quirk in the web browser. Glad it’s working for you!

1 Like

This topic was automatically closed after 30 days. New replies are no longer allowed.