Hey @abroes – I took a closer look at the certificate to see what was going on, and it looks like it’s related to a bug that we fixed in an earlier version of Local: SSL Not working on Chrome with NET::ERR_CERT_INVALID
We did ship a fix with Local, but looking at the certificate you provided, it seems that’s using a cert generated on an older version of Local.
For example, if I save that certificate and examine it with openssl, I see that the CA value is set to false:
One question I have – have you used this site for a long time? For example, I think we released the fix for this back in March/April of 2022. Did you create, and trust the certificate for this site before that time?
Since it looks like you are on the latest version of Local, I think you can have Local regenerate the certificate for you by doing a couple manual steps:
- Navigate to where Local stores the certificates for the sites. The easiest way is to click the “Reveal Local router’s logs” from the help menu, and then click through to the
certfolder - Delete the key/cert pairs
- Quit, and re-start Local, and click the “Trust” button for each site so that Local will re-generate the missing cert and re-register it with the OS.
Here’s a screenshot to help visualize where to go on Windows:
My hunch is that this site was created a while ago and was using a certificate that was generated on an earlier version of Local. @abroes – can you give that a shot and let us know how it goes?