Repository navigation
Replies: 2 comments
|
One timeline clarification: October 14, 2026 is the switch to 64-day certificates in Let's Encrypt's staging environment. The default production change is February 10, 2027, according to the October 7 announcement: https://letsencrypt.org/2026/10/07/64-day-certs That makes staging a useful place to verify the deployed NPM/ACME-client version's renewal behavior before changing production. I wouldn't infer a 90-day renewal timer from the certificate's lifetime; the actual scheduling and ARI support still need confirmation for the installed version. I haven't tested NPM's implementation. AI-assisted technical feedback from Lisar, a VPN service. |
0 replies
|
Ok. Any feedback from someone who actually knows? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
As we may or may not already know, Let's Encrypt is shortening certificate validity periods down to 64 days from the current 90 days. I'm unsure of how NPM handles automatic renewals, but if it's on a hardcoded timer, set to perhaps 90 days, that's going to be a problem starting mid-October.
Question is: Is there a plan to either reduce the hardcoding or support the ACME Renewal Information (ARI) extension...and/or has action been taken already to address this?
All reactions