Ending Support for Expiration Notification Emails
letsencrypt.org
external-link
Since its inception, Let’s Encrypt has been sending expiration notification emails to subscribers that have provided an email address to us. We will be ending this service on June 4, 2025. The decision to end this service is the result of the following factors: Over the past 10 years more and more of our subscribers have been able to put reliable automation into place for certificate renewal. Providing expiration notification emails means that we have to retain millions of email addresses connected to issuance records.

I think it’s a good idea, everyone should be automating this anyway.

Björn Tantau
link
fedilink
English
1424d

You’re not supposed to do it manually.

@ramble81@lemm.ee
link
fedilink
English
824d

Tell that to all the embedded device manufacturers… switches, appliances, nas, etc.

There’s a whole load of things that will have a massive administrative burden if the frequency is dropped.

Björn Tantau
link
fedilink
English
-524d

Skill issue.

Kokesh
link
fedilink
English
624d

My server does it automatically, but I have few services I can’t make to read the certs from server storage, so I have to manually copy cert content. Especially Adguard Home for some reason refuses to read my certs.

Björn Tantau
link
fedilink
English
1124d

Have the same problem. But symlinks or copying them via cron solved it for me.

Kokesh
link
fedilink
English
424d

Yes! yes | cp -Lrf /etc/letsencrypt/live/…domain…/*.pem /var/snap/adguard-home/current

You could use a reverse proxy to terminate tls, and take the tls off of ad guard itself.

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 277 users / day
  • 678 users / week
  • 1.48K users / month
  • 3.94K users / 6 months
  • 1 subscriber
  • 4.18K Posts
  • 87K Comments
  • Modlog