mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #4705] Access Lists on custom location paths #2989
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#2989
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 @Bahama03 on GitHub (Aug 11, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4705
Hello,
While implementing Proxy Manager and migrating from Apache Reversed Proxy (which are all configuration files built and referred to in sites files) I came across the following configuration I use and miss in Nginx Proxy Manager;
Most of the websites are public, while others have the need to use basic HTTP Auth or an access list. This is already possible on a domain and works like a charm.
Now there are some websites which are public, but some subdirectories or subfiles on a website should be protected by auth or acl. Simple example: Wordpress websites should be public, but the wp-admin and/or wp-login.php sub url should be restricted by IP. In Apache I named a separate location and defined the allowed IP ACL.
In proxy manager this is not yet possible, since I can't define a proxy host (e.g. example.com/wp-admin), I can only define domain names (e.g. domain.com (without something after the /)). I can define custom locations for various paths but it is not possible to define a ACL for the specific path.
I am not a programmer, but I would very much like to have the option to be able to select a ACL list on a custom location (subdirectory).
Does anyone have any input?
Thanks
Regards,
Thomas
@aerickt commented on GitHub (Aug 17, 2025):
I currently add a custom location and specify whatever access control I need. Here's an example:
However, I don't like this approach. I would much prefer the ability to use access lists on subdirectories. as @Bahama03 describes.
@fvultee commented on GitHub (Aug 19, 2025):
How are you seeing the window at the bottom of the custom locations tab where you can enter allow/deny rules? I'm on the most current version of NPM and I don't have that field?
@aerickt commented on GitHub (Aug 20, 2025):
@fvultee Press the gear icon.
@fvultee commented on GitHub (Aug 20, 2025):
Wow, I must have been tired, it's literally right in front of me...
@BenoitSafari commented on GitHub (Nov 10, 2025):
I had to do some research and came across this issue to see this icon as well. You’re not alone.
However, being able to use the access list from there would be a great addition.
@fvultee commented on GitHub (Nov 10, 2025):
Well at least we can put the details of an ACL under the icon and get the same effect, but you're right it would nice to just be able to select a predefined ACL.