mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3612] Let's Encrypt Certificate- too many failed authorizations recently #2394
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#2394
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 @ckoeber83 on GitHub (Mar 8, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3612
By adding a Let's Encrypt Certificate I got an Internal Error with too many failed authorizations recently: see https://letsencrypt.org/docs/failed-validation-limit/
NPM_BUILD_VERSION | 2.11.1
@bluekitedreamer commented on GitHub (Mar 9, 2024):
I would say to look at the log, but it doesn't look like it's mapped outside the container
Do this command, it will print the lets encrypt log file to your commandline
docker exec -it [CONTAINER-NAME] cat /tmp/letsencrypt-log/letsencrypt.logTake a look at why the lets encrypt authorization is failing
@bluekitedreamer commented on GitHub (Mar 9, 2024):
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3575
Related
@chriszuercher commented on GitHub (Mar 10, 2024):
I'm facing the same issue (and as well #3575 )
@tr1p0p commented on GitHub (Mar 11, 2024):
Facing the same issue, now my domain is blocked and have to wait to have a working website.
Here's the logs of letsencrypt failure :
@chriszuercher commented on GitHub (Mar 13, 2024):
Did anybody find a workarround or solution? My certificate will expire in the next days and cannot be renewed.
@bluekitedreamer commented on GitHub (Mar 14, 2024):
@chriszuercher Post your lets encrypt log, take note of personal information (emails, domains) and remove it
@tr1p0p
You're hitting letsencrypts limit, use a wildcard instead for that domain
@chriszuercher commented on GitHub (Mar 17, 2024):
Edit: I could finally just create a new certificate (using same data) and use this one. Let's hope next renew works again. The rate limit didn't occur (last I couldn't do this because I was blocked out becuase of to many requests).
Original Problem:
I'm using 3 domains in the same certificate. One of them is handled in NPM (ha.) the others not. The challenge works for the two domains not handled at NPM but not for the one which is used as proxy there. This one stays pending forever. Portforwarding and DNS config is the same for all of them (and ha. ist alsow working and handeld in NPM):
@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 (Oct 31, 2025):
Issue was closed due to inactivity.