[GH-ISSUE #422] Wrong SSL read in browsers #278

New issue

Closed

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

kerem commented

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

Owner

Originally created by @damms005 on GitHub (Jan 19, 2022).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/422

Strangely, I've been unable to get generated SSLs to work on my new computer (works on previous one). While trying to debug this, I found that the expiry dates reported by browsers for the cert are wrong. I will use snapshots of Chrome to explain.

After running mkcert -install, I generated the cert with mkcert tims.local "*.tims.local" example.test localhost 127.0.0.1 ::1. Command output was good.

I configured apache to use it. Relevant site config lines are:

        SSLEngine on
        SSLCertificateKeyFile   /etc/ssl/certs/tims.local+5-key.pem
        SSLCertificateFile      /etc/ssl/certs/tims.local+5.pem

Restarted apache, restarted browsers. Error persists. Clicking on "Not secure" on Chrome address bar area, I get this:

I ran the cert creation code at

Jan 19 2022 at 07:51
on my local computer. ls /etc/ssl/certs/tims.local+5-key.pem also confirms that.

Where did Chrome get an Expires On value of:

Wednesday, 5 November 2031 at 02:15:54

My best guess is that somehow Chrome is holding on to some old, previously generated cert? I've tried clearing cache and all that, to no avail

Originally created by @damms005 on GitHub (Jan 19, 2022). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/422 Strangely, I've been unable to get generated SSLs to work on my new computer (works on previous one). While trying to debug this, I found that the expiry dates reported by browsers for the cert are wrong. I will use snapshots of Chrome to explain. After running `mkcert -install`, I generated the cert with `mkcert tims.local "*.tims.local" example.test localhost 127.0.0.1 ::1`. Command output was good. I configured apache to use it. Relevant site config lines are: ``` SSLEngine on SSLCertificateKeyFile /etc/ssl/certs/tims.local+5-key.pem SSLCertificateFile /etc/ssl/certs/tims.local+5.pem ```` Restarted apache, restarted browsers. Error persists. Clicking on "Not secure" on Chrome address bar area, I get this: ![image](https://user-images.githubusercontent.com/9839355/150081047-d8d31386-b012-4e31-94cd-89b4a370f345.png) I ran the cert creation code at > Jan 19 2022 at 07:51 on my local computer. `ls /etc/ssl/certs/tims.local+5-key.pem` also confirms that. Where did Chrome get an `Expires On` value of: > Wednesday, 5 November 2031 at 02:15:54 My best guess is that somehow Chrome is holding on to some old, previously generated cert? I've tried clearing cache and all that, to no avail