mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #194] Access lists result in 401 Authorization Required #171
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#171
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 @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:
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
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
@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.
@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.
@chaptergy commented on GitHub (Jan 14, 2022):
@FlyingPersian The issue is probably with the Authorization headers.
@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.