[GH-ISSUE #304] Access Restriction not applied when custom locations are used #269

Closed
opened 2026-02-26 06:31:52 +03:00 by kerem · 6 comments
Owner

Originally created by @lekoOwO on GitHub (Feb 22, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/304

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Are you sure you're not using someone else's docker image?
  • If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?

Describe the bug

  • When a "/" custom location is used in order to add CORS headers, the Access List setting will not be applied.
  • What version of Nginx Proxy Manager is reported on the login page? v2.1.1

To Reproduce
Steps to reproduce the behavior:

  1. Create a proxy host.
  2. Add a custom location, which the Define location field == / and fields else is as same as the one in Details tab.
  3. Set up an Access List for this proxy host in Details tab.
  4. Check that no access list is applied to the whole website.

Expected behavior
Access list should work.

Operating System

  • docker on linux
Originally created by @lekoOwO on GitHub (Feb 22, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/304 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Are you sure you're not using someone else's docker image? - If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? **Describe the bug** - When a "/" custom location is used in order to add CORS headers, the Access List setting will not be applied. - What version of Nginx Proxy Manager is reported on the login page? v2.1.1 **To Reproduce** Steps to reproduce the behavior: 1. Create a proxy host. 2. Add a custom location, which the `Define location` field == `/` and fields else is as same as the one in `Details` tab. 3. Set up an Access List for this proxy host in `Details` tab. 4. Check that no access list is applied to the whole website. **Expected behavior** Access list should work. **Operating System** - docker on linux
kerem 2026-02-26 06:31:52 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@lekoOwO commented on GitHub (Feb 22, 2020):

I think adding a location / block for user to edit is a good idea in order to add CORS header which prevents overriding the access list settings.

<!-- gh-comment-id:589973382 --> @lekoOwO commented on GitHub (Feb 22, 2020): I think adding a `location /` block for user to edit is a good idea in order to add CORS header which prevents overriding the access list settings.
Author
Owner

@netcop82 commented on GitHub (Feb 23, 2020):

I don't know if this is related, but after version 2.1.1 all my proxies just stopped working. They show as active (green light), but don't work. I have custom location / set on all of them.

<!-- gh-comment-id:590029219 --> @netcop82 commented on GitHub (Feb 23, 2020): I don't know if this is related, but after version 2.1.1 all my proxies just stopped working. They show as active (green light), but don't work. I have custom location `/` set on all of them.
Author
Owner

@lekoOwO commented on GitHub (Feb 23, 2020):

I don't know if this is related, but after version 2.1.1 all my proxies just stopped working. They show as active (green light), but don't work. I have custom location / set on all of them.

Mine works as well, might not related. :hmm:

<!-- gh-comment-id:590058175 --> @lekoOwO commented on GitHub (Feb 23, 2020): > I don't know if this is related, but after version 2.1.1 all my proxies just stopped working. They show as active (green light), but don't work. I have custom location `/` set on all of them. Mine works as well, might not related. :hmm:
Author
Owner

@jc21 commented on GitHub (Feb 23, 2020):

@netcop82 if you suspect it's 2.1.1, downgrade to the 2.0.14 tag and see if things are magically working agian.

<!-- gh-comment-id:590126763 --> @jc21 commented on GitHub (Feb 23, 2020): @netcop82 if you suspect it's 2.1.1, downgrade to the `2.0.14` tag and see if things are magically working agian.
Author
Owner

@wtf911 commented on GitHub (Apr 15, 2020):

@jc21 not to piggy back off this but I feel the problem is a larger any custom locations aren't have the access list applied to them. If I have an access list applied and go to www.test.com I get prompted for a password. But if I go to www.test.com/qbittorrent/ it takes me right to it without asking for a password.

image

<!-- gh-comment-id:614322415 --> @wtf911 commented on GitHub (Apr 15, 2020): @jc21 not to piggy back off this but I feel the problem is a larger any custom locations aren't have the access list applied to them. If I have an access list applied and go to www.test.com I get prompted for a password. But if I go to www.test.com/qbittorrent/ it takes me right to it without asking for a password. ![image](https://user-images.githubusercontent.com/5151430/79397310-c99ce980-7f4b-11ea-8a78-ee4fde045219.png)
Author
Owner

@chaptergy commented on GitHub (May 11, 2021):

Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/148

<!-- gh-comment-id:839056410 --> @chaptergy commented on GitHub (May 11, 2021): Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/148
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#269
No description provided.