[GH-ISSUE #138] New certificate "appears to be expired" #83

New issue

Closed

opened 2026-02-25 22:32:33 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 22:32:33 +03:00

Owner

Originally created by @selfagency on GitHub (Feb 15, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/138

I just created a new certificate for a project on my local machine. But when I load up the site, I get the following error:

"Websites prove their identity via certificates, which are valid for a set time period. The certificate for local.test appears to be expired."

Examining the certificate, it says creation date is June 29, 2017 and the expiration date is June 29, 2018.

Very odd and confusing. What's happening here?

Originally created by @selfagency on GitHub (Feb 15, 2019). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/138 I just created a new certificate for a project on my local machine. But when I load up the site, I get the following error: "Websites prove their identity via certificates, which are valid for a set time period. The certificate for local.test appears to be expired." Examining the certificate, it says creation date is June 29, 2017 and the expiration date is June 29, 2018. Very odd and confusing. What's happening here?

kerem closed this issue

2026-02-25 22:32:33 +03:00

kerem commented

2026-02-25 22:32:33 +03:00

Author

Owner

@selfagency commented on GitHub (Feb 15, 2019):

Never mind, it was an Nginx issue.

@selfagency commented on GitHub (Feb 15, 2019): Never mind, it was an Nginx issue.

kerem commented

2026-02-25 22:32:33 +03:00

Author

Owner

@rossPatton commented on GitHub (Nov 9, 2019):

Currently having this problem, could you elaborate on how you resolved this?

@rossPatton commented on GitHub (Nov 9, 2019): Currently having this problem, could you elaborate on how you resolved this?

kerem commented

2026-02-25 22:32:33 +03:00

Author

Owner

@rfay commented on GitHub (Nov 9, 2019):

Please check that you are using v1.4.0, especially if macOS Catalina is involved. Versions prior to v1.4.0 could not be valid on Catalina.

@rfay commented on GitHub (Nov 9, 2019): Please check that you are using v1.4.0, especially if macOS Catalina is involved. Versions prior to v1.4.0 could not be valid on Catalina.