mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 09:55:51 +03:00
[GH-ISSUE #2046] acces list and ssl #1479
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#1479
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 @darkstudio on GitHub (May 10, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2046
Hi,
When we try to use "acces list" AND "ssl", we have 2 issues:
Regards,
@jtrosper commented on GitHub (May 12, 2022):
Also encountering this issue. However, I cannot reproduce the circumstances on demand. It just seems to randomly occur that I go to access one of my proxy hosts and I get the cert invalid error. My fix to date has been to disable "force SSL" and the other SSL options, save, then re-enable and save. But that only lasts for a while.
@PiekJ commented on GitHub (May 22, 2022):
Had this problem today too while enabling ipv6 for my services and updating the access list.
It seems that updating the access list causes SSL related settings on ALL proxy hosts to be removed.
Took me a while to realize what was causing it.
@evanlabs commented on GitHub (May 24, 2022):
I also had the same problem.
Adding new content to an access list will cause all proxy configurations that enable this access list to lose the ssl certificate configuration.
@radoman93 commented on GitHub (May 31, 2022):
Same. Still an issue.
@github-actions[bot] commented on GitHub (Feb 17, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 2, 2025):
Issue was closed due to inactivity.