mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3861] Renewing Cert - Error #2533
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#2533
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 @sias32 on GitHub (Jul 8, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3861
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
When trying to autoupdate a certificate, an error appears in the application logs:
And on the database side, a warning comes out in the logs:
But at the same time the certificate is renewed, it has an extended date...
Nginx Proxy Manager Version
Using jc21/nginx-proxy-manager:2.11.2
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Clearly no errors should pop up when updating a certificate
Operating System
Debian 12, Docker. Run in docker swarm
Additional context
If you do the renewal manually, no errors occur
Application environment variables
@sias32 commented on GitHub (Jul 10, 2024):
After upgrading to 2.11.3, the error remains
@sias32 commented on GitHub (Jul 11, 2024):
This doesn't happen with all certificates, some update without problems, it's hard to figure out which ones yet
@sias32 commented on GitHub (Jul 12, 2024):
I created a test service, on the latest version 2.11.3
There are three domains on it, leading to one service whoami, for each of them access list was created. The first one is completely open, the second one is closed under authorization and the third one is limited by addresses. At first everything was ok, but after a day errors started to appear
@jo-pouradier commented on GitHub (Nov 4, 2024):
Hello got same issue, which DNS are you using ? If its cloudflare, desactivate cloudflare proxy (test but wait a few minutes), get your ssl certs and put cloudlfare proxy again.
Otherwise for other DNS use nslookup <your_domain> and verify its your ip.
@sias32 commented on GitHub (Mar 27, 2025):
@jo-pouradier No, I don't use it. It's interesting that everything works
@Silicon51 commented on GitHub (May 21, 2025):
So, there's a chance that you have my case: both piHole and NPM as docker containers.
Due to some weird behavior of DNS resolver NPM container do not have access to internet so cannot request for cert.
For me it log errors like
Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/cloudflare/Also I have error
Failed to check the reachability due to a communication error with site24x7.com nginx proxywhen in version 2.12.3 I use option "Test Server Reachability" from tab SSL Certificates.How to solve it?
add following to your NPM docker compose:
@github-actions[bot] commented on GitHub (Nov 23, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍