mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #2867] Why Basic Auth Loop ? #1967
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#1967
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 @Jamyz on GitHub (Apr 28, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2867
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
With Basic Auth i have a loop everytime to npm.domain.com asking user/pass.
Others services too ex. container.domain.com, etc....
Nginx Proxy Manager Version
v2.10.2
Expected behavior
Only ask one time please!
Operating System
Raspberry Pi4, Docker, Debian GNU/Linux 11 (bullseye)
Additional context
All works fine with IP Address Whitelist/Blacklist via [Nginx HTTP Access]
I have my raspberry pi with ip 192.168.0.112.
nginx-proxy-manager is on port 81. Destination ->http://192.168.0.112:81
portainer is on port 9000. Destination ->http://192.168.0.112:9000
After login 2 times with Basic Auth:
[4/28/2023] [11:09:55 AM] [Express ] › ⚠ warning Existing token contained invalid user data
Thanks
@github-actions[bot] commented on GitHub (Jan 21, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@xvvvyz commented on GitHub (Apr 11, 2024):
👍
@github-actions[bot] commented on GitHub (Nov 9, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Nov 30, 2025):
Issue was closed due to inactivity.