mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #2890] Access control issue when assigning ip only #1983
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#1983
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 @piraterx on GitHub (May 5, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2890
I tried using access control so certain websites are only accessed from certain ip, but somehow it doesn't work with allowed ips.
Under access list, I list ip as
publicip/32
and when I try to access that website from that ip, I get 403 error. I have another instance working on different system and it works fine. I did clean install on system not working and same issue. They both have same .yml file.
Where do I look for issue to fix, because two system and one works and another doesn't.
@dezza commented on GitHub (Oct 22, 2023):
Try to check(box) "Satisfy any" [x]
I had issues with HTTP Basic Auth as well, but this made sure it satisfied on IP-restrictions only.
@github-actions[bot] commented on GitHub (Jun 6, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Jun 9, 2025):
Issue was closed due to inactivity.