mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2267] All certificate renewals suddenly fail. Has worked for months if not years. #1615
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#1615
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 @Waldorf3 on GitHub (Sep 15, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2267
After using this container for months, if not years, with minimal interaction necessary, suddenly certificates are no longer automatically updated. Nothing changed in my environment so I'm a bit at a loss what happened.
From the log:
@the1ts commented on GitHub (Sep 15, 2022):
@Waldorf3 There is a problem with renewing if force SSL is turned on, if that is true for you, turn off force SSL, renew then turn back on.
Its awaiting a fix to be merged #2038
@huntitus commented on GitHub (Sep 15, 2022):
We have the same symptoms. The certificates not renewed by automatically. When I try to renew manually on the GUI, it provide an "internal error" message (without any error code, or details). Sadly this solution is not reliable :/
Edit:
Looks like this problem is very old :/ and still exist.
@Waldorf3 commented on GitHub (Sep 15, 2022):
I already tried the "uncheck force ssl and reissue cert", it just throws an "internal error".
I'm running NPM in docker, not sure how to start fiddling with a script to fix this. Would be better if the author would acknowledge the bug and offer a proper solution.
@Waldorf3 commented on GitHub (Sep 17, 2022):
I'm just realizing I might be barking up the wrong tree. Is jc21 the actual developer/maintainer of this code, or just the docker-packager? If not, who is responsible for the code, who can fix this bug?
I actually find the NPM SSL subsystem to be quite fragile. If for example you try to enable SSL for a site that does not have a root directory, such as for example ubooquity (requires http://ubooquity/ubooquity) it will also fail with a nondescript "internal error", and only way to fix is manually cleaning up the database. That's a viable solution for a single failed certificate, not for a system with 30 or more proxy hosts with failed certs.
@the1ts commented on GitHub (Sep 17, 2022):
JC21 is the developer and the only fragility at the moment that I see is the renew issue outstanding a merge.
I simply don't see how NPM fronting for ubooquity results in an internal error that requires DB cleanup. The application isn't even hit for letsencrypt SSL certs to be created via the HTTP auth method.
Also picking a pretty broken by modern standards application like ubooquity to measure success is odd. It has, as you say, no root directory so requires special measures and also a different port for admin so requires special measures again, no tool calling itself easy to use can be expected to handle both those broken by modern standards decisions.
Often internal errors are after people remove active SSL certs breaking Nginx config i.e. ignoring the warning. What specific errors are you still getting?
@EDIflyer commented on GitHub (Oct 7, 2022):
Just to confirm that PR #2038 by @the1ts seems to be doing the trick for me.
@github-actions[bot] commented on GitHub (Feb 9, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@Saibamen commented on GitHub (Feb 9, 2024):
👍
@jdhorner commented on GitHub (Nov 7, 2024):
👍
@e1ke commented on GitHub (Jan 10, 2025):
👍
have the same issue with jc21/nginx-proxy-manager:2.12.2
turning off 'force SSL', renewing the certificates by hand and turning 'force SSL' on again worked for me but this will be pretty annoying if that is the only workaround for this issue and not a permanent solution.
Strange that it worked for years and now suddenly stopped working. I migrated to another server by copying the data volume, maybe there is an issue with file permission or sth? I can't figure it out
edit
mh, after ignoring the HSTS settings, it worked even with 'force SSL' activated:
I think that works as a permament solution for me
@EDIflyer commented on GitHub (Jan 10, 2025):
@e1ke if you want a more permanent solution that allows HSTS to be turned on then feel free to use
nginxproxymanager/nginx-proxy-manager-dev:pr-3121from my PR at #3121 - I live in hope that it'll be merged one of these days!@HarryVasanth commented on GitHub (Jan 11, 2025):
@e1ke I second this. I am not sure why this PR hasn't been merged yet. It helped me and so many others afterwards.
@github-actions[bot] commented on GitHub (Jul 16, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@EDIflyer commented on GitHub (Jul 16, 2025):
Not fixed yet, PR still needs merged in
@github-actions[bot] commented on GitHub (Feb 19, 2026):
Issue is now considered stale. If you want to keep it open, please comment 👍
@EDIflyer commented on GitHub (Feb 19, 2026):
Still needs #3121 merged in