starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #420] Access list "Satisfy All" requiring BasicAuth on trusted subnet. #353

New issue

Closed

opened 2026-02-26 06:32:31 +03:00 by kerem · 7 comments

kerem commented

2026-02-26 06:32:31 +03:00

Owner

Originally created by @Chewza on GitHub (May 24, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/420

UPDATE NOTE: Having thought about this a little more I've identified the issue. The redirected hosts are currently being proxied by cloudflare. As I am running all DNS through cloudflare and don't have any of these addresses defined in my local dns server even though I'm home, I'm going out to cloudflare to come back in. Thus I think the only way to accomplish what I'm after would be to define the local dns entries I need. While it would be nice to not have to do this I understand why it's happening.

Unless I'm missing something as to a way Nginx PM can read my local IP address even coming through cloudflare when I'm here at home, this issue can be closed.

Checklist

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

Describe the bug
Selecting "satisfy any" on an access list with both authorization and ip range entered, browsing from a machine on the 10.1.1.0/24 subnet which is defined in the access tab of the access list settings still prompts me for authorization.

What version of Nginx Proxy Manager is reported on the login page?
2.2.4

To Reproduce

Define authorization user
Define allowed ip range (I'm using 10.1.1.0/24)
Select satisfy any on main tab.
Attach access list to redirected host
Attempt to access redirected host from machine on 10.1.1.0/24 subnet
Prompted for username and password.

Expected behavior
When satisfy any for the access list is selected, and I'm browsing from an allowed subnet, in this case 10.1.1.0/24 I would expect NOT to be prompted for login.

Screenshots

Operating System
Docker image running on ubuntu 20.04

Additional context
N/A

Originally created by @Chewza on GitHub (May 24, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/420 UPDATE NOTE: Having thought about this a little more I've identified the issue. The redirected hosts are currently being proxied by cloudflare. As I am running all DNS through cloudflare and don't have any of these addresses defined in my local dns server even though I'm home, I'm going out to cloudflare to come back in. Thus I think the only way to accomplish what I'm after would be to define the local dns entries I need. While it would be nice to not have to do this I understand why it's happening. Unless I'm missing something as to a way Nginx PM can read my local IP address even coming through cloudflare when I'm here at home, this issue can be closed. **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? Yes - Are you sure you're not using someone else's docker image? Yes - If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? Not an LE issue. **Describe the bug** Selecting "satisfy any" on an access list with both authorization and ip range entered, browsing from a machine on the 10.1.1.0/24 subnet which is defined in the access tab of the access list settings still prompts me for authorization. - What version of Nginx Proxy Manager is reported on the login page? 2.2.4 **To Reproduce** 1) Define authorization user 2) Define allowed ip range (I'm using 10.1.1.0/24) 3) Select satisfy any on main tab. 4) Attach access list to redirected host 5) Attempt to access redirected host from machine on 10.1.1.0/24 subnet 6) Prompted for username and password. **Expected behavior** When satisfy any for the access list is selected, and I'm browsing from an allowed subnet, in this case 10.1.1.0/24 I would expect NOT to be prompted for login. **Screenshots** ![image](https://user-images.githubusercontent.com/8115774/82744009-0cb75d00-9d41-11ea-8cc9-7fa40c7667de.png) ![image](https://user-images.githubusercontent.com/8115774/82744017-1ccf3c80-9d41-11ea-9433-7443df6cbbc3.png) ![image](https://user-images.githubusercontent.com/8115774/82744001-f27d7f00-9d40-11ea-9297-a7ee7b76b745.png) **Operating System** Docker image running on ubuntu 20.04 **Additional context** N/A

kerem

2026-02-26 06:32:31 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 06:32:31 +03:00

Author

Owner

@Chewza commented on GitHub (May 24, 2020):

Please see update note at top of original issue submission.

@Chewza commented on GitHub (May 24, 2020): Please see update note at top of original issue submission.

kerem commented

2026-02-26 06:32:31 +03:00

Author

Owner

@R0GGER commented on GitHub (Jun 1, 2020):

Exact same issue here...
I also use Cloudflare DNS, but not using setting "Proxied" but just "DNS only".
I don't think it has anything to do with using Cloudflare...

@R0GGER commented on GitHub (Jun 1, 2020): Exact same issue here... I also use Cloudflare DNS, but not using setting "Proxied" but just "DNS only". I don't think it has anything to do with using Cloudflare...

kerem commented

2026-02-26 06:32:31 +03:00

Author

Owner

@R0GGER commented on GitHub (Jun 10, 2020):

Version 2.3.1 solved my issue. What about you @Chewza ?

@R0GGER commented on GitHub (Jun 10, 2020): Version 2.3.1 solved my issue. What about you @Chewza ?

kerem commented

2026-02-26 06:32:31 +03:00

Author

Owner

@Chewza commented on GitHub (Jun 10, 2020):

Unfortunately I haven't had a chance to test recent updates myself. I had to work around the issue by managing split brain DNS.

@Chewza commented on GitHub (Jun 10, 2020): Unfortunately I haven't had a chance to test recent updates myself. I had to work around the issue by managing split brain DNS.

kerem commented

2026-02-26 06:32:31 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 29, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Mar 29, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:32:31 +03:00

Author

Owner

@beer73 commented on GitHub (Feb 22, 2025):

Hi, just to comment that I had exactly the same problem with version 2.12.1, but after updating to version 2.12.3 the problem has disappeared and the Access Lists now work as they should.

@beer73 commented on GitHub (Feb 22, 2025): Hi, just to comment that I had exactly the same problem with version 2.12.1, but after updating to version 2.12.3 the problem has disappeared and the Access Lists now work as they should.

kerem commented

2026-02-26 06:32:31 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 12, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Nov 12, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

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#353

No description provided.

Rows
Columns