mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #2895] Allow Access List to be assigned for individual Custom Locations #1986
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#1986
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 @carlos-algms on GitHub (May 7, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2895
Is your feature request related to a problem? Please describe.
It seems only possible to assign
Access Listsfor the main domain, not for thecustom locations.So, I'm not able to restrict a specific subpath, while leaving others publicly available.
Describe the solution you'd like
It would be great to have the possibility of adding an
access listper individualcustom location.Maybe include a dropdown like this:
Describe alternatives you've considered
I'm manually copying/pasting a snippet on each
custom domain, and if something changes, I have to change everything manually once more.@amraerakit commented on GitHub (Aug 22, 2023):
Yes. This is needed feature.
@github-actions[bot] commented on GitHub (Apr 13, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@carlos-algms commented on GitHub (Apr 13, 2024):
I still think it is relevant.
@github-actions[bot] commented on GitHub (Jan 11, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@carlos-algms commented on GitHub (Jan 11, 2025):
I still think it's relevant. 👍🏻
@scharez commented on GitHub (Jul 18, 2025):
+1
@Bahama03 commented on GitHub (Aug 11, 2025):
+1
@github-actions[bot] commented on GitHub (Feb 17, 2026):
Issue is now considered stale. If you want to keep it open, please comment 👍
@Bahama03 commented on GitHub (Feb 17, 2026):
+1
@carlos-algms commented on GitHub (Feb 17, 2026):
I still think it's a nice to have.