mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1537] Renewal of certificates via https challenge returns 404 #1170
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#1170
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 @Apollon77 on GitHub (Oct 30, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1537
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
None of my current certificates renews atm ... a log looks like as the "https" URL that is tried to be called is not exiosting or such
When I call the page after getting the error I get an Error 404 from OpenResty, so I assume that the routing is correct
Letsencrypt Logs
Nginx Proxy Manager Version
2.9.11
To Reproduce
Renew cert ... or wait until he tries to auto renew ... also happens there
Expected behavior
Reniew works
Operating System
Runs on an intel nuc as docker inside lxc, but this should be irrelevant
@chaptergy commented on GitHub (Oct 31, 2021):
So it seems it is not available from the public internet for some reason or another. Do you have mutliple instances of npm and could have mixed them up in the DNS record? Or maybe a different nginx instance?
I have created a PR which adds a button to test the connection to your server, could you please switch to the following version of the docker image:
jc21/nginx-proxy-manager:github-pr-1538and press the button to see what the result is?@C-Fu commented on GitHub (Nov 2, 2021):
Same here. Renewing just won't work with some if not all expired certs.
Example from docker-compose logs:
@chaptergy commented on GitHub (Nov 2, 2021):
@C-Fu Your problem is definitely something different than the original issue the author reported, please open a new issue for that.
@Apollon77 commented on GitHub (Nov 2, 2021):
@chaptergy Will do the check tomorrow ... but in fact the services are all reachable from external via theirs domains and "al lot of traffic" goes to them and no other nginx is in between.
@Apollon77 commented on GitHub (Nov 2, 2021):
I was also able to check the URL from error message and always got an 404 from "OpenResty" (and I have nothing else then nginx-proxy-manager which should use that
@chaptergy commented on GitHub (Nov 4, 2021):
Yeah the url should always return 404 and only return actual data for the short period the check is running. This means both when renewing certificates and when clicking on the test domains button.
Have you tried using the different image and clicking the test button? If so, what was the result?
@Apollon77 commented on GitHub (Nov 4, 2021):
I did ... result was all good ...

trying exactly this host directly after the check gave ...
Letsencrypt Log
@chaptergy commented on GitHub (Nov 4, 2021):
Hm, I don't really have any more ideas what the issue could be then... Would just creating new certificates be an option for you?
@Apollon77 commented on GitHub (Nov 4, 2021):
Yes shure ... I think I will simply do that ... maybe next renewals then works better ... no idea too.
btw: like that test button! Can you give me a pung when it is in latest then I can update image from there
@Apollon77 commented on GitHub (Nov 4, 2021):
PA: creating new works
@chaptergy commented on GitHub (Nov 4, 2021):
Let's hope so, sometimes those errors just never occur again. If I remember I can ping you, you could also use the watch button at the top to watch for new releases with watch > custom > releases. Then you will also be notified about future releases
Great that creating new certificates work! Should I close the issue for now then?
@Apollon77 commented on GitHub (Nov 4, 2021):
it seems that we was lucky to renew one cert some days ago ... currently try to renew that one - should know more in 5 mins ( that random delay is a strange when trigger renewal "Now" - this very often makes the UI display "timeout")
@Apollon77 commented on GitHub (Nov 4, 2021):
PS: Good news ... new renewal worked ... so can be closed from my perspective - should I create a new issue for thet "delay /Timeout" issue?
@chaptergy commented on GitHub (Nov 4, 2021):
Yeah, that would be a different thing.