mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #2487] No Authorization, passwors stored in "Hints" not in "Passwords" #1737
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#1737
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 @ostenax on GitHub (Dec 18, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2487
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Authorization passwords are stored in "Hint" not in "Password" and so the Authorzation don't work
Nginx Proxy Manager Version
2.9.19
To Reproduce
under "Audit Log" open the last "Created Access list " will show in details:
{
"name": "test",
"satisfy_any": true,
"pass_auth": false,
"items": [
{
"username": "test",
"password": "",
"hint": "t***"
}
],
"clients": [],
"id": 7,
"meta": {}
}
Expected behavior
Password should stored in the right location to bring up Authorization
Screenshots

Operating System
Proxmox 7.3, installed with the Proxmox script
Additional context
System installed in LXC Container witg the Proxmox script. Reverse Proxy works without authentikation
@rijnhard commented on GitHub (Jan 26, 2023):
Oh my word....
@sephit commented on GitHub (Jun 11, 2023):
Any news about this bug, could it be resolved?
@github-actions[bot] commented on GitHub (Feb 2, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 19, 2025):
Issue was closed due to inactivity.