Mac - Chrome / Not Secure / Certificate is not valid

[susanBuck]

System

Mac BigSur 11.2.1
Chrome 95.0.4638.69 (Latest version as of this writing)

Issue

I'm seeing the "Not Secure" flag in Chrome and a message that "Certificate is not valid"

When I click the more info icon for the "Certificate is not valid" message, it shows the following with no further indication as to what the problem might be.

Steps I followed to set up

1. Created a new certificate w/ mkcert
2. Added it to Mac's Keychain Access and made sure it was set to "Always Trust"
3. Configured my Apache server to use the certificate/key for the site in question.

[Mihir-Bhasin]

I am getting the same issue in chrome.

[bilalbayasut]

I'm getting the same issue in any browser

[bilalbayasut]

@susanBuck have you got it working? Any solution for this guys ?

[bilalbayasut]

I solve this issue with manually importing the certs into chrome/safari : https://www.keokukschools.org/certificate-safari-chrome/ .
if you got error when importing the certs, ignore it. once you are done with the steps above, restart your mac, and it should work

[andreasvirkus]

I had to call mkcert -install first and then call mkcert localhost. This SO answer helped me solve it https://stackoverflow.com/a/57226788/2803743

[rpuig]

I have a similar issue. When I installed it in windows 10, then i checked the certificate validity dates and it is as if it was creted with wrong dates . 11/11/2009 to 09/11/2019. But i have created it today and today is 04/04/2022 . Anyone knows why this is happening?

[skuppuraj]

I am also using macOS Big Sur (11.6.5) and Apache Server with the virtual host.

I am sharing the steps I followed and installed successfully. Check if it works for you.

My local site name: example.test

I created the directory crt in the document root of the directory

Then I installed the certificate for example.test site

mkcert example.test

Then I configured the virtual host to load the certificate.

Listen 443

<VirtualHost *:443>
    DocumentRoot "/Users/[username]/Sites/example"
    ServerName example.test
    SSLCertificateFile "/Users/[username]/Sites/crt/example.test.pem"
    SSLCertificateKeyFile "/Users/[username]/Sites/crt/example.test-key.pem"
    VirtualDocumentRoot /Users/[username]/Sites/example
</VirtualHost>

[FiloSottile]

As mentioned in #412 (comment), it looks like OP is using the root certificate directly, which is not how mkcert works. Instead, you need to generate a certificate for the website, for example in this case by running mkcert hesweb.loc.

[lydhr]

I used mkcert myurl.example and everything was working until around last month.
Chrome says 'certificate is not valid' while I could proceed to the website(unsafe) by ignoring the warning.