mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #890] Access List + Restart = invalid Cert on all endpoints with access list applied #753
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#753
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 @JohnGalt1717 on GitHub (Feb 12, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/890
Checklist
jc21/nginx-proxy-manager:latestdocker image?yes
yes
na
Describe the bug
Per Title
To Reproduce
Create an access list that has an internal subnet white listed (i.e. 10.0.0.0/8).
Apply it to endpoints and save with let's encrypt certificate.
Save.
Verify that it works without issue
Restart nginx proxy manager docker container
Close browser, open it again and go to same url
-- Results in invalid certificate and inspection shows that it's the dummy certificate.
Go into the endpoint
Save the endpoint without changes
Refresh browser
Works fine again.
Note that all endpoints that do not have an access list assigned work fine.
Expected behavior
Should survive restarts properly and apply the certs correctly without having to save the endpoints individually every time.
Operating System
Ubuntu 20.10
@Kareltje1980 commented on GitHub (Feb 21, 2021):
I can confirm this. As so far that the issue I am seeing is very similar.
(I am on the latest docker version 2.7.3)
Change an access list, by adding/removing an IP range on the access tab. Then all the proxies using that end point have invalid certificates. It appears this is because the region
# Let's Encryptin thedata/nginx/proxy_host/00.confis missing. Opening and saving the proxy restores the missing data.@apainter2 commented on GitHub (Apr 26, 2021):
Also confirmed that this bug still exists. I am using NPM version 2.8.1 from the jc21 docker image.
@Kareltje1980 solution was a fix for it, but I had to open 20+ proxies to fix it. But its not ideal.
@tgrimminger commented on GitHub (Aug 6, 2021):
I can confirm that this bug still exists in NPM version 2.9.6 hosted via docker.
@Kareltje1980 solution still works but is not ideal obviously.
@SteveGBuck commented on GitHub (Aug 13, 2021):
Confirmed, I've got this issue too with ubuntu 20.04.2 LTS server as the docker host.
Upgraded to 2.9.7 and still experiencing the issue.
@AlfaJackal commented on GitHub (Oct 11, 2021):
Upgraded to 2.9.9, issue still exists.
@kffl commented on GitHub (Nov 27, 2021):
Still experiencing this issue in version 2.9.12. After editing an access list, all of the proxy hosts with that access list selected start using a self-signed certificate instead of the Let's Encrypt one. The workaround described by @Kareltje1980 appears to be working.
@exgame commented on GitHub (Jan 17, 2022):
It still persist to this date. Latest docker image.
@gmaurice commented on GitHub (Jan 20, 2022):
Hello, I faced to the same issue too with the version v2.9.14.
@OnkelKeule commented on GitHub (Jan 29, 2022):
Same in v2.9.15
@sethiele commented on GitHub (Apr 19, 2022):
And Still in v2.9.18
@kroese commented on GitHub (Jun 9, 2022):
Also experienced this issue in v2.9.18
I don't understand why this is still not fixed after a year?
@TopBanana123 commented on GitHub (Oct 3, 2022):
Well I'm glad its not just me, v2.9.18, same problem!
@jonathanhoskin commented on GitHub (Oct 17, 2022):
Same here in v2.9.18. Thought I was loosing my mind!
@NeitherSound commented on GitHub (Dec 15, 2022):
At least it is not me alone having this issue. Is a fix ever coming out for this? I am on the latest version of Nginx, no issues other than this one known bug
@ukewea commented on GitHub (Dec 29, 2022):
Same here in v2.9.19, any help would be appreciated, thanks.
@joaquinvacas commented on GitHub (Mar 19, 2023):
Hey! Any news on this?
@Realmagnum commented on GitHub (Mar 21, 2023):
nope.
still have problem, I think It is time to learn something else traefik for example.
@iveney commented on GitHub (Mar 29, 2023):
wow this just happened to me. Debugged for quite a while. I have to manually go through each proxy_host and edit save to let the cert populate in the actual proxy host conf.
@AustinLeath commented on GitHub (Jul 4, 2023):
Can confirm, this is still happening in 2.9.19. Affected all 18 hosts. had to remove each host from the access list and add them all back in.
@github-actions[bot] commented on GitHub (Mar 19, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 30, 2025):
Issue was closed due to inactivity.