mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1199] 2.9.4 Breaks Certbot Auto-Renewal and Certificate Verification #980
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#980
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 @eroc1990 on GitHub (Jun 22, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1199
Upon upgrading to 2.9.4, I discovered that anything I'm reverse proxying no longer loads and Cloudflare throws a 520 error. I'm not sure what directory 2.9.3 and older looked for, but NPM isn't finding ant certs in what it's expecting, which is /etc/letsencrypt/renewal. As a result none of my sites appear to be loading.
Here's a snip of my tailing the letsencrypt log after attempting to force a renewal of one of my existing certs:
Anything you can do to help resolve this would be greatly appreciated. It wouldn't be a ton of trouble to rebuild it if need be but I'm curious if I'm the only one running into this issue.
@eroc1990 commented on GitHub (Jun 22, 2021):
For the record this can be fixed by simply requesting a new cert through the GUI but as is, it did break my setup.
Should have included this earlier: Running Docker on Unraid ver. 6.9.2,
@focher commented on GitHub (Aug 11, 2021):
Same issue here. Using Route 53 with DNS validation configured. The initial certificate is created fine.
Logs
@jc21 commented on GitHub (Aug 11, 2021):
I found this article on the subject:
https://charles-stover.medium.com/fixing-certbots-parsefail-error-during-certificate-renewal-1e7718f8a492
Could it be that your
letsencryptfolder is not happy? This could be no fault of your own. There was a certbot update very recently that may have impacted how it wants the folder to be structured. I haven't had this problem myself, yet.@focher commented on GitHub (Aug 11, 2021):
I suspect you are correct. When I checked the article and compared to my local certbot "live" folder, it was not using the symlinks to the archive folder per the article. I then deleted a cert and just recreated, and now the entries in the live folder were proper symlinks to archive.
For anyone encountering this issue, it appears you will either need to delete and recreate the certs or manually create the symlinks between the live folder and archive. I tried to manually recreate the symlinks per the article but it never completed cleanly, despite the logs showing it did create new cert files and link them properly. But the nginx web ui still shows the old dates.
@jc21 commented on GitHub (Aug 11, 2021):
The dates thing is an inspection only, and only happens after a successful "renewal" command is run from within the app. Something to fix later, but minor.
@github-actions[bot] commented on GitHub (Mar 9, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 21, 2025):
Issue was closed due to inactivity.