mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #2304] Unable to login to Admin UI #1633
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#1633
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 @skirven4 on GitHub (Oct 4, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2304
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
On version 2.9.18, I am unable to login to the NPM UI. Yes, I can downgrade to 2.9.14 and get it to work, sort of.
Nginx Proxy Manager Version
2.9.18
To Reproduce
Steps to reproduce the behavior:
2.168.0.196, server: nginxproxymanager, request: "POST /api/tokens HTTP/1.1", upstream: "http://127.0.0.1:3000/tokens", host: "nettools.local:81", referrer: "http://nettools.local:81/login"Expected behavior
User should be able to login to the system
Screenshots
Operating System
Raspian OS
Additional context
I find this token api error strange. I'm also getting a "Bad Gateway" nginx message on url :81/api, as I tried that after finding an older issue that seemed similar. I also rebuilt my docker-compse.yml. Additionally, the port 3000 is not open in my installation, either at the host, or inside the container.
@pennyloafers commented on GitHub (Feb 10, 2023):
having this same issue, on a fresh install it works fine, but i found that any change to the docker network of nginx causes this issue and it is not resolved by undoing network changes.
@pennyloafers commented on GitHub (Feb 11, 2023):
So looking at the docker log in the container, I found an issue with certbot.
going into container and resolving the install errors by getting a few dependencies to get a successful install, restarting the container i'm now able to login again.
@johncaipa commented on GitHub (Apr 12, 2023):
I have solved it by entering the mysql container shell and executing the following:
sudo chown -R mysql:mysql /usr/local/mysql/
sudo chmod -R 755 /usr/local/mysql/
@github-actions[bot] commented on GitHub (Feb 8, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 24, 2025):
Issue was closed due to inactivity.