[GH-ISSUE #1859] Access Lists not working

kerem commented

2026-02-26 07:30:40 +03:00

Owner

Originally created by @smarteshome2020 on GitHub (Feb 15, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1859

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
Have you searched for similar issues (both open and closed)?
- Yes

Describe the bug
If i using Access List and im 100% sure that the Password are correct i recieved

{ "message": "invalid username or password" }

The nginx prozess was reloaded correctly.

[2/15/2022] [9:11:00 PM] [Access ] › ✔ success Built Access file #6 for: smarteshome
[2/15/2022] [9:11:24 PM] [Nginx ] › ℹ info Reloading Nginx
[2/15/2022] [9:11:56 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[2/15/2022] [9:11:58 PM] [Nginx ] › ℹ info Reloading Nginx

Nginx Proxy Manager Version
V 2.9.15

To Reproduce
Steps to reproduce the behavior:

create Access List with "Satisfy any", Pass Auth to host" enabled and one User (test/test)
add Access List to Proxy Host
open Link and type User = test and Password=test in the popup
See error
If im using a wrong user or password the popup will cleared and ask again for user/password

Expected behavior

Screenshots

Operating System
Ubuntu 21.10 Docker

Additional context

Originally created by @smarteshome2020 on GitHub (Feb 15, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1859  **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 - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** If i using Access List and im 100% sure that the Password are correct i recieved `{ "message": "invalid username or password" }` The nginx prozess was reloaded correctly. [2/15/2022] [9:11:00 PM] [Access ] › ✔ success Built Access file #6 for: smarteshome [2/15/2022] [9:11:24 PM] [Nginx ] › ℹ info Reloading Nginx [2/15/2022] [9:11:56 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [2/15/2022] [9:11:58 PM] [Nginx ] › ℹ info Reloading Nginx **Nginx Proxy Manager Version** V 2.9.15 **To Reproduce** Steps to reproduce the behavior: 1. create Access List with "Satisfy any", Pass Auth to host" enabled and one User (test/test) 2. add Access List to Proxy Host 3. open Link and type User = test and Password=test in the popup 4. See error 5. If im using a wrong user or password the popup will cleared and ask again for user/password **Expected behavior**  **Screenshots** ![image](https://user-images.githubusercontent.com/97242825/154150573-69660fc9-9466-45f2-8636-95f56244a899.png) **Operating System** Ubuntu 21.10 Docker **Additional context**

kerem

2026-02-26 07:30:40 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@hoiber commented on GitHub (Feb 15, 2022):

Hey, Was it an exisiting access list that you modified? if so have you re-opened and saved the related proxy host? Its a known issue where you need to re-save the host as well as setting the access list.

@hoiber commented on GitHub (Feb 15, 2022): Hey, Was it an exisiting access list that you modified? if so have you re-opened and saved the related proxy host? Its a known issue where you need to re-save the host as well as setting the access list.

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@smarteshome2020 commented on GitHub (Feb 16, 2022):

Hi, first i create the Access List and than i change the Proxy Host. Same error.I aso create an new proxy host and select the existing Access List, same error

@smarteshome2020 commented on GitHub (Feb 16, 2022): Hi, first i create the Access List and than i change the Proxy Host. Same error.I aso create an new proxy host and select the existing Access List, same error

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@VTFLAB commented on GitHub (Feb 18, 2022):

I'm the same.
In my case, I get 403 Forbidden when I enable it.
I've added my own IP to the permissions, of course.

@VTFLAB commented on GitHub (Feb 18, 2022): I'm the same. In my case, I get 403 Forbidden when I enable it. I've added my own IP to the permissions, of course.

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@aphroti commented on GitHub (Mar 4, 2022):

I had the same exact issue here. If check "satisfy any", I'll be repeatedly asking for login info. If I uncheck "satisfy any", I'll get 404 error.

@aphroti commented on GitHub (Mar 4, 2022): I had the same exact issue here. If check "satisfy any", I'll be repeatedly asking for login info. If I uncheck "satisfy any", I'll get 404 error.

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@istefy92 commented on GitHub (Mar 6, 2022):

Same here - 403 Forbidden

@istefy92 commented on GitHub (Mar 6, 2022): Same here - 403 Forbidden

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@4smarthome68 commented on GitHub (Jun 29, 2022):

Same here - 403 Forbidden

@4smarthome68 commented on GitHub (Jun 29, 2022): Same here - 403 Forbidden

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@jadsy2107 commented on GitHub (Nov 17, 2022):

me too

@jadsy2107 commented on GitHub (Nov 17, 2022): me too

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@viseshrp commented on GitHub (Dec 21, 2022):

Same here. Following this issue.

@viseshrp commented on GitHub (Dec 21, 2022): Same here. Following this issue.

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@viseshrp commented on GitHub (Dec 21, 2022):

Check this out for workarounds: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/383
Also, I had these in Custom Configuration:

real_ip_header CF-Connecting-IP;
#real_ip_header X-Forwarded-For;

Commenting them out helped solve the problem.

@viseshrp commented on GitHub (Dec 21, 2022): Check this out for workarounds: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/383 Also, I had these in Custom Configuration: ``` real_ip_header CF-Connecting-IP; #real_ip_header X-Forwarded-For; ``` Commenting them out helped solve the problem.

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@lacrima08 commented on GitHub (Apr 28, 2023):

Hi, same here, asking repeatedly for password, even with password copy/paste

Edit : I got it working but only if I create the access rule on 1st try. If I edit the rule, it breaks it

@lacrima08 commented on GitHub (Apr 28, 2023): Hi, same here, asking repeatedly for password, even with password copy/paste Edit : I got it working but only if I create the access rule on 1st try. If I edit the rule, it breaks it

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@mxbchr commented on GitHub (Sep 12, 2023):

I tried every possible combination of configurations in the last two hours.
What reliably fixed it for me is this:

Creating a "Allow 0.0.0.0/0" rule in the Access List Tab
Deactivating "Satisfy Any" in ACL Tab
Create a NEW Proxy Host.
Deactivating HTST, HTST Subdomains and HTTP/2 in the Proxy Host Tab. Force SSL works for me when everything else is off.

And yes. It is crucial to first create the ACL and then create a NEW Proxy Host. Adding the ACL to an existing proxy host will result in 403 error, or in logging in having no effect and login window showing over and over again.

Note: When I misconfigured it i had to "clear the site data" in the browser for it to work again once it was configured right.

And just in case someone doesn't know (as I did 2h ago). You can auto login if you use this url scheme:
https.//username:password@example.com/
Hope this helps.

@mxbchr commented on GitHub (Sep 12, 2023): I tried every possible combination of configurations in the last two hours. What reliably fixed it for me is this: 1. Creating a "Allow 0.0.0.0/0" rule in the Access List Tab 2. Deactivating "Satisfy Any" in ACL Tab 3. Create a NEW Proxy Host. 4. Deactivating HTST, HTST Subdomains and HTTP/2 in the Proxy Host Tab. Force SSL works for me when everything else is off. And yes. It is crucial to first create the ACL and then create a NEW Proxy Host. Adding the ACL to an existing proxy host will result in 403 error, or in logging in having no effect and login window showing over and over again. Note: When I misconfigured it i had to "clear the site data" in the browser for it to work again once it was configured right. And just in case someone doesn't know (as I did 2h ago). You can auto login if you use this url scheme: https.//username:password@example.com/ Hope this helps.

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 4, 2024):

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

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

kerem commented

2026-02-26 07:30:41 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 17, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Jun 17, 2025): Issue was closed due to inactivity.

Rows
Columns

[GH-ISSUE #1859] Access Lists not working #1360