mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #4341] Updates on Lets Encrypt Subscriber Agreement & Ending Expiration Notification #2791
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2791
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @HassanMullah on GitHub (Feb 4, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4341
I get that e-Mail today. Can NPM ACME Client ARI?
Hi,
As a Let’s Encrypt Subscriber, you benefit from access to free, automated TLS certificates. One way we have supported Subscribers is by sending expiration notification emails when it’s time to renew a certificate.
We’re writing to inform you that we intend to discontinue sending expiration notification emails. You can learn more in this blog post. You will receive this reminder email again in the coming months:
https://letsencrypt.org/2025/01/22/Ending-Expiration-Emails
Here are some actions you can take today:
Automate with an ACME Client that supports Automated Renewal Information (ARI). ARI enables us to automatically renew your certificates ahead of schedule should the need arise:
https://letsencrypt.org/2024/04/25/guide-to-integrating-ari-into-existing-acme-clients
Sign up for a third-party monitoring service that may provide expiration emails. We can recommend Red Sift Certificates Lite, which provides free expiration emails for up to 250 active certificates:
https://redsift.com/pulse-platform/certificates-lite
Opt in to emails. While we are deprecating expiration notification emails, you can opt in to continue to receive other emails. We’ll keep you informed about technical updates, and other news about Let’s Encrypt and our parent nonprofit, ISRG, based on the preferences you choose:
https://letsencrypt.org/opt-in/
In accordance with this change, we are updating our Subscriber Agreement, effective 24 February 2025. This is the agreement that governs the relationship between you and ISRG with regards to your acquisition and use of SSL/TLS digital certificates issued by ISRG (via Let's Encrypt). You don't need to take any action to continue to use the Let's Encrypt service but we encourage you to review the new agreement. You can find the latest agreement (v1.5) here:
https://letsencrypt.org/repository/
If you are receiving this email in error, unsubscribe at:
http://delivery.letsencrypt.org/track/unsub.php?u=30850198&id=bbe368e209284fbdb46619e9c4d104b2.WGEtBkEVDdE8zeI3RXtgDtL+Flo=&r=https://mandrillapp.com/unsub?md_email=i%2A%2A%2A%2A%40h%2A%2A%2A%2A.%2A%2A%2A
All the best,
Let’s Encrypt
@robogeek commented on GitHub (Feb 7, 2025):
I received the same, of course. I wondered if this has any impact on us NGINX Proxy Manager users
@fortinmike commented on GitHub (Feb 16, 2025):
I came here to check if someone already asked for expiration notifications in n-p-m. As
nginx-proxy-managermanages certificates for us, it should be a good place to add renewal failure notifications or emails when required? Something like Pushover integration (maybe through a webhook-style setup) and/or SMTP support would be nice.@github-actions[bot] commented on GitHub (Aug 24, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍