mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 09:55:51 +03:00
[GH-ISSUE #4595] Feature Request: Let locations assign Access Lists #2933
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#2933
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 @eigenphase on GitHub (Jun 23, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4595
Is your feature request related to a problem? Please describe.
It is very common to use locations instead of hosts, for example, /owntracks instead of owntracks.example.com.
For these cases it would be great if we can assign access lists to locations as well. Because the access control for the locations may be different from the underlying host.
Describe the solution you'd like
Add this:
to here:
Describe alternatives you've considered
Currently I use the extended settings to paste the access control lines manually. But this is not elegant and very error prone. Especially when I change a list, it won't be updated for these cases.
@Bahama03 commented on GitHub (Aug 11, 2025):
+1
@github-actions[bot] commented on GitHub (Feb 26, 2026):
Issue is now considered stale. If you want to keep it open, please comment 👍