In case anybody here uses Letsencrypt and a) hasn't received an email from them b) doesn't have some auto-renewal or reminder set up, they won't be issuing expiry reminders: https://letsencrypt.org/2025/01/22/Ending-Expiration-Emails
 

> We will be ending this service on June 4, 2025.

Well that's a slight relief - the only date in the email I saw was "24 February 2025" which is far too short notice for something like this.

The email also lacks the part where they recommend alternatives people can use instead: //letsencrypt.org/docs/monitoring-options/

Still means extra effort when setting up a certificate to then go login to a web-based service and add a watch.

for me it's very mixed. Would have been a royal pita a year ago. Now incredibly mixed feelings since the nextcloud snap covers all my letsencrypyt needs. What does teh use?

 

Teh uses Let's Encrypt, but Matt handles that.

Most of the time it's a non-issue - upgrades are automatic and without issue, but when there's something up with the server, it was useful to have a "your certificate should have been renewed by now" notification to go check it out.

My website had some sort of possibly related certificate hiccup last night. I couldn't remember if I had manually set it up through LE/certbot (I did this for a work domain a few years back, so maybe had it confused with that), and had a discouraging poke around before retiring (to bed). Anyway this morning it's back up, apparently all thanks to my benevolent, taciturn, and very difficult to contact hosting provider.

They just sent me another reminder that they won't be reminding me anymore. I used to use certbot when I had an owncloud server. Then I switched to Nextcloud with a snap and it's sort of automagical. I didn't know it would do that so there's all kinds of left over bits and pieces of not-snap letsencrypt and certbot lying around that I must get rid of one day.

ISTR having done this previously by adding A records to the domain DNS to validate, but my personal domain registrar (GD, who else) has custom DNS servers set by my hosting provider, so I can't edit the DNS. Anyway it's been so long I'd have to read through it again, and it's probably all changed.