Timeline for Invalid certificate on all SE sites
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 10, 2021 at 12:39 | history | edited | This_is_NOT_a_forum | CC BY-SA 4.0 |
Active reading [<https://en.wiktionary.org/wiki/time_zone#Noun> <http://stackoverflow.com/legal/trademark-guidance> (the last section)]. Added some information from comments (perhaps more should be added?).
|
| Oct 1, 2021 at 13:44 | history | edited | TylerH | CC BY-SA 4.0 |
added 87 characters in body
|
| Oct 1, 2021 at 12:36 | comment | added | GoodDeeds | That certificate had a fixed expiry date right when it was issued, so there was no need for there to have been any change on your end for it to become invalid on that date (which was yesterday). It was valid for 21 years, from 2000-2021, the new one is valid till 2035. | |
| Sep 30, 2021 at 19:12 | history | edited | Polyhat | CC BY-SA 4.0 |
added 542 characters in body
|
| Sep 30, 2021 at 18:41 | comment | added | rene Mod | For reference: superuser.com/a/1054727 | |
| Sep 30, 2021 at 18:35 | comment | added | animuson StaffMod | @Polyhat Yes, issuers have root certificates that verify the authenticity of all site certificates, making them trusted, and are usually issued for 10 or 20 years at a time. Root certificates are installed directly onto your system. They are not fetched each time you connect to a site because they are global and not specific to a site. Any site you connected to that uses a Let's Encrypt certificate will stop functioning due to that certificate's expiration if you don't have a new one installed. It's not specific to us in any way. | |
| Sep 30, 2021 at 18:33 | comment | added | Ramhound | I suspect Safari on iOS will have a problem with the certificate, since another Let's Encrypt certificate, was also a problem. The problem with the website in question was on an iPhone 13 running iOS 15 | |
| Sep 30, 2021 at 18:32 | comment | added | Polyhat | Firefox tells me the certificate that expired is from the issuer: "SEC_ERROR_EXPIRED_ISSUER_CERTIFICATE". The error does not appear to be related to my end of things at all. | |
| Sep 30, 2021 at 18:29 | comment | added | rene Mod | Okay, go to Let's Encrypt: letsencrypt.org/certificates and download their ISRG Root X1 certificate and add it manually to the Firefox certificate store as Trusted CA. Notice that on the page I linked they also offer test links so you can verify if you installed the certificates correctly. Once it works there, SE sites should work as well. | |
| Sep 30, 2021 at 18:29 | comment | added | Polyhat | There were no updates to my system between yesterday and today. Nothing changed on my end. | |
| Sep 30, 2021 at 18:28 | history | edited | Polyhat | CC BY-SA 4.0 |
added 166 characters in body
|
| Sep 30, 2021 at 18:27 | comment | added | animuson StaffMod | @Polyhat It's really not our decision to do that, though. Our certificate is valid. We don't control root certificates - those are installed onto your system through standard security updates. Our only solution would be to find a completely different provider to get trust through a different root certificate, which is a bit unreasonable. Refusing to install updates will eventually cause all root certificates on your device to expire over time. | |
| Sep 30, 2021 at 18:24 | comment | added | Polyhat | I'm on Mac OSX 10.8.3 and using Firefox 48.0.2. I cannot upgrade Firefox for this OS, so if the SE sites are just throwing users like me under the bus, I won't be back after this. My MacBook is a mid-2013 model and has too much of importance to risk any OS upgrades. | |
| Sep 30, 2021 at 18:20 | comment | added | rene Mod | What browser / OS is this? Include the versions if you can and whether your OS/Browser is managed by an enterprise or by yourself. | |
| Sep 30, 2021 at 18:16 | history | answered | Polyhat | CC BY-SA 4.0 |