mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3575] Exponential back off on autorenew #2372
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#2372
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 @DrogoNevets on GitHub (Feb 21, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3575
Is your feature request related to a problem? Please describe.
LetsEncrypt multiple failures cause the user to hit the rate limiter on LetsEncrypt
Describe the solution you'd like
Either the ability to turn off auto renew for certificates or exponential backoff after failures
Describe alternatives you've considered
Looked to see if i can turn auto renew off easily, but I cant see it
Additional context
I keep getting failures on auto renew, i suspect becasue of the ForceSSL bug mentioned elsewhere - but it appears to run every hour without fail. It would be great if I could control if it run at all, and if the auto runs used an exponential back off so as not to litter the logs etc
@tr1p0p commented on GitHub (Mar 11, 2024):
Yeah, because of this bug cannot just... Config my domains with nginx proxy manager and have to wait to just have a working website. Kind of annoying
@github-actions[bot] commented on GitHub (Oct 28, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Nov 1, 2025):
Issue was closed due to inactivity.