mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #3460] Apply access list to specific location of proxy host #2310
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#2310
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 @Alanimdeo on GitHub (Jan 16, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3460
Is your feature request related to a problem? Please describe.
I'm using Vaultwarden, which has a publicly accessible admin page via the /admin address, so I want to use a specific Access List when accessing the /admin location.
Describe the solution you'd like
Allows specifying an Access List for a custom location on the proxy host.
Describe alternatives you've considered
Additional context
@joser93 commented on GitHub (Aug 8, 2024):
+1 I want to have a pastebin with login to allow posting a file, when the file is posted, is allowed to view in public. I want to handle the credentials using the access list with locations, maybe someone else has an use case for this feature as well
@github-actions[bot] commented on GitHub (Feb 23, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@scharez commented on GitHub (Jul 18, 2025):
+1
@Bahama03 commented on GitHub (Aug 11, 2025):
+1
@github-actions[bot] commented on GitHub (Feb 15, 2026):
Issue is now considered stale. If you want to keep it open, please comment 👍
@Bahama03 commented on GitHub (Feb 17, 2026):
+1