Let's Encrypt Ending Support for Expiration Notification Emails
-
-
I think yeah, most people don't use calendars.My wife doesn't even use one at work.
My dad though started using it after I implemented audible announcements of them in Home Assistant. He normally doesn't use his phone or computer much, but this way anywhere he is in his house he is reminded 90min before the event and then at the event again. With this he never misses appointments at doctors and so on anymore. That was what pushed him to use a digital calendar, every missed appointment costs quite some money.
-
Yeah, I love Sync, but currently it's the last thing I would pick to set a standard
-
Sync markup/rendering is presently a semi-completed conversion from reddit's and it's functional enough.
-
-
-
emails
Needs a [sic] in there.
-
I scheduled a doctor's appointment recently and they were confused when I opted out of SMS notifications. They were shocked when I whipped out my calendar to type the appointment in.
-
I think uptime Kuma can be configured to look for expiring certs
-
Their are multiple different way u can configure certbot to verify.
-
I actually think it's set by default. If there's a cert it gives you the expiration.
-
Oh no, the free service is going to make you put a reminder on your calendar.
-
Sigh, yeah I know that and that's not the point I was making but sure.
-
What manual hooks? All the systems I've used LE certs in have supported fully automatic DNS challenges.
-
I know, clients not wrapping lines in codeblocks are also "rendering properly". Wrapping it's up to the client's parser, reason why I noted to use the aproppriate syntax regardless.
-
Change is hard, I get it, if this change is upsetting, I'd personally figure out the automation piece. it took me a bit but after getting it going it's rock solid. If using Linux of some flavor, acme.sh works really well.
-
If you use Caddy with ACME DNS, all of this can be automated.
If you also use Cloudflare, you can do that + traffic routing with cloudflared without any need for port forwarding .
-
It’s twoo, it’s twoo
-
It's more than needing a reminder: Let's Encrypt Certs are valid for a maximum of 90 days before they need to be reissued. Doing this 4 times (or more) a year, for years on end will be tedious and error prone.
Most tools that request and install Let's Encrypt Certs automatically do this without the need for human interaction (30 days prior to the expiration) . Actually, they work so well you don't notice the "behind the scenes work" that's happening.
The problem is when this renewal process "stop working". I'd been using Let's Encrypt for years w/o problems, but eventually the client I was using wasn't updating and it was using a deprecated Let's Encrypt API. Ultimately, the cert stopped updating, but I got the email reminder from Let's Encrypt and I was able to fix it w/o a disruption.
Now, this was just a server for personal use. So if the SSL cert expired, it would not be the end of the world. Plus, I would have gotten a bunch of SSL errors the next time my client was trying to sync data, and I probably would have dropped everything to fix it. But the email reminder was a convenient feature, which allowed me to fix it whenever I had time.
That said, if Let's Encrypt wants to save some money for their free service, I'm certainly not going to complain (although I will miss it).
-
I use uptime kuma to check my certificate isn't going to expire.
Also tells me if any of my services are down.
