[GH-ISSUE #194] Access lists result in 401 Authorization Required #171

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

Originally created by @mcinnes01 on GitHub (Aug 30, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/194

When I use the access list with a username and password, assigned to a proxy host, I get:
401 Authorization Required

To Reproduce
Steps to reproduce the behavior:

  1. Create a new access list
  2. Add a username and password
  3. Assign the access list to a proxy host
  4. Navigate to the proxy host url
  5. Enter the username and password in the challenge

It won't authenticate and will re-display the challenge.

Expected behavior
When I enter the username and password it should display the site attached that proxy host

Operating System

  • Using on Ubuntu 18.04 host in a docker container as part of hassio (Home Assistant)

Additional context
Using chrome latest, also tried on edge latest. Using the home assistant hassio addon of this library, basically just pulls your docker image for management through the HassIO addon store: https://github.com/hassio-addons/addon-nginx-proxy-manager

Originally created by @mcinnes01 on GitHub (Aug 30, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/194 When I use the access list with a username and password, assigned to a proxy host, I get: 401 Authorization Required **To Reproduce** Steps to reproduce the behavior: 1. Create a new access list 2. Add a username and password 3. Assign the access list to a proxy host 4. Navigate to the proxy host url 5. Enter the username and password in the challenge It won't authenticate and will re-display the challenge. **Expected behavior** When I enter the username and password it should display the site attached that proxy host **Operating System** - Using on Ubuntu 18.04 host in a docker container as part of hassio (Home Assistant) **Additional context** Using chrome latest, also tried on edge latest. Using the home assistant hassio addon of this library, basically just pulls your docker image for management through the HassIO addon store: https://github.com/hassio-addons/addon-nginx-proxy-manager
kerem 2026-02-26 06:31:06 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

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

As this issue is very old please verify that this issue still persists. If it does let me know, I will reopen this issue.

<!-- gh-comment-id:838877346 --> @chaptergy commented on GitHub (May 11, 2021): As this issue is very old please verify that this issue still persists. If it does let me know, I will reopen this issue.
Author
Owner

@FlyingPersian commented on GitHub (Jan 14, 2022):

To me it still exists! I'm running everything on Home Asssitant as addons. I restarted the addon after changing the access list and proxy settings to use the ACL. Every time I try to load the page, the login window pops back up and the log says 401 even though the username and password are corect.

<!-- gh-comment-id:1013433288 --> @FlyingPersian commented on GitHub (Jan 14, 2022): To me it still exists! I'm running everything on Home Asssitant as addons. I restarted the addon after changing the access list and proxy settings to use the ACL. Every time I try to load the page, the login window pops back up and the log says 401 even though the username and password are corect.
Author
Owner

@chaptergy commented on GitHub (Jan 14, 2022):

@FlyingPersian The issue is probably with the Authorization headers.

<!-- gh-comment-id:1013504766 --> @chaptergy commented on GitHub (Jan 14, 2022): @FlyingPersian The issue is probably [with the Authorization headers](https://nginxproxymanager.com/faq/#when-adding-username-and-password-access-control-to-a-proxy-host-i-can-no-longer-login-into-the-app).
Author
Owner

@GEkuL commented on GitHub (Nov 1, 2023):

I've got into the trap with it, setting the Access List for NPM, which itself uses the Autorization headers to let user in.

It would be great if this behavior (for NPM login) would be fixed.

<!-- gh-comment-id:1789598533 --> @GEkuL commented on GitHub (Nov 1, 2023): I've got into the trap with it, setting the Access List for NPM, which itself uses the Autorization headers to let user in. It would be great if this behavior (for NPM login) would be fixed.
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#171
No description provided.