mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #2754] Logging into the admin interface no longer works. Mistake: Internal Error #1892
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#1892
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 @AnID-Aux on GitHub (Mar 27, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2754
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Logging into the admin interface no longer works. Mistake: Internal Error and sporadically Bad Gateway. Standard Username and Password don't work as well. Misstake: No relevant user found. Going back to 2.9.22 is working.
Nginx Proxy Manager Version
v2.10.0
To Reproduce
Steps to reproduce the behavior:
@Bark33p3r commented on GitHub (Mar 27, 2023):
I get the same error at first. Few seconds later ist shows: "No relevant user found".
Reverted to v2.9.22 and I can login again.
@JamesMCL44 commented on GitHub (Mar 27, 2023):
Just to confirm the same error on my side at my fresh install and the temporary "fix" is to downgrade to v2.9.22
@shepherds-git commented on GitHub (Mar 27, 2023):
I had the same problem, but I found out that I could login with the default credentials (admin@example.com...). Afterwards I saw an empty configuration in the dashboard, with 0 proxy hosts. But in the background the existing configuration was running in the nginx proxy. I could access my hosts from the web. Fir me it seems that the running configuration and the web-interface aren't synchronized. Maybe this helps to find the issue.
@stanthewizzard commented on GitHub (Mar 27, 2023):
give right to the data and letsencrypt folder
it's 911 now (without puid or guid)
chown 0777
worked for me
@Bark33p3r commented on GitHub (Mar 27, 2023):
Thanks for the advise
When I change owner and group to 0777
and run "docker-compose up -d" it will change to 911 again and I'm getting the same error.
(name and password removed for the screenshot)
@Nessiroj commented on GitHub (Mar 28, 2023):
Thanks for this, this fixed my issues aswell after trying to troubleshoot it for 3 hours
This is the next issue after the chown 0777
thankfully my hosts are working again, just can't access the npm to configure them
@stanthewizzard commented on GitHub (Mar 28, 2023):
In your case the databse is empty ...
try to access it with phpmyadmin or if you are a warrior (I'm tired today) with command line
@meistermopper commented on GitHub (Mar 28, 2023):
However, I see a security problem there with 0777. Before the update the folders data and letsencrypt have the rights
drwxr-xr-x 755 root root data.For me, in any case, the version 2.10.0 is not usable.
@meistermopper commented on GitHub (Mar 29, 2023):
With version 2.10.1 access to the MariaDb 10.9.3 database is not possible.
With version 2.9.21 it still works fine.
Here is the log from npm:
Log from MariaDb:
Portainer stack:
@purpletoad2020 commented on GitHub (Mar 30, 2023):
Same issue here
after upgraded to 2.10.1, no longer be able to login
got Bad Gateway error
However, the actual proxy is still function, all proxied website still be able to access
@AlexKusnezov commented on GitHub (Mar 30, 2023):
same here
No relevant user found@Bark33p3r commented on GitHub (Mar 31, 2023):
Just installed 2.10.2 . Still the same problem.
@popallo commented on GitHub (Mar 31, 2023):
if you use a mysql database and the configuration of this one is in the file "npm-config.json" then it is normal that it does not work, this file is not used any more and it is necessary to pass by the environment variables.
@Bark33p3r commented on GitHub (Mar 31, 2023):
Great, Thanks a lot for the advise!!!
Now it works.
nobrainer instruction for people like me:
Update your docker
Loginin with:
fill out your name and mail in the pop-up
change the password in the next upcoming pop-up (old pw, 2x new pw)
Thanks a lot @popallo
@AlexKusnezov commented on GitHub (Mar 31, 2023):
@Bark33p3r
did that and it worked, however the hosts are not showing up:
How to deal with that? They're still working though
@popallo commented on GitHub (Mar 31, 2023):
Your docker instance is probably using an sqlite database while I imagine you were on mysql before? If so, read my previous comment, it may help you.
@AlexKusnezov commented on GitHub (Mar 31, 2023):
@popallo
Are you refring to this?
What do I have to do in my sepcific case, please take a look at my config:
@popallo commented on GitHub (Mar 31, 2023):
This configuration's file is not used anymore. You need to add "environment:" with some specifics variables under "app:" like in this example :
https://nginxproxymanager.com/setup/#using-mysql-mariadb-database
@AlexKusnezov commented on GitHub (Mar 31, 2023):
@popallo thanks, change my config to the following:
still can't see my hosts, but they're still working, any idea how to display them?
@AlexKusnezov commented on GitHub (Mar 31, 2023):
@popallo nevermid, I solved this now:
Since I had to change
/mnt/nginx-proxy-manager/data/mysql:/var/lib/mysqlto/mnt/nginx-proxy-manager/mysql:/var/lib/mysql(otherwise I would get Bad Gateway), I just copied manually the mysql fodler over and now it shows my host:@SSpt1978 commented on GitHub (Apr 1, 2023):
Hi, i have this docker compose and after update to 2.10.2 can't login. Anything wrong?
Reverted to version 2.9.22
version: "3.8"
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
# These ports are in format :
- '80:80' # Public HTTP Port
- '443:443' # Public HTTPS Port
- '81:81' # Admin Web Port
# Add any other Stream port you want to expose
# - '21:21' # FTP
# - '22:22' # SFTP
environment:
DB_MYSQL_HOST: "db"
DB_MYSQL_PORT: 3306
DB_MYSQL_USER: "XXXXXXXXXXXX"
DB_MYSQL_PASSWORD: "XXXXXXXXXXXX"
DB_MYSQL_NAME: "npm"
# Uncomment this if IPv6 is not enabled on your host
# DISABLE_IPV6: 'true'
volumes:
- ./_hsts.conf:/app/templates/_hsts.conf:ro
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
depends_on:
- db
db:
image: 'jc21/mariadb-aria:latest'
restart: unless-stopped
environment:
MYSQL_ROOT_PASSWORD: 'XXXXXXXXXXXXXX'
MYSQL_DATABASE: 'npm'
MYSQL_USER: 'XXXXXXXXXXXXX'
MYSQL_PASSWORD: 'XXXXXXXXXXXXXXXXX'
volumes:
- ./data/mysql:/var/lib/mysql
@AlexKusnezov commented on GitHub (Apr 1, 2023):
@SSpt1978 the mysql folder has to be outside of the data folder see my last comment
@stanthewizzard commented on GitHub (Apr 1, 2023):
In my case it’s inside data
Rebuild with docker-compose
Restarted
Works
Reverse proxy and administration pages
@SSpt1978 commented on GitHub (Apr 2, 2023):
Thanks, it worked
@poltrian commented on GitHub (Apr 15, 2023):
I use MaraDB Docker with Nginx Proxy Manager. When i use admin@example.com i got also No relevant user found
@kosymodo commented on GitHub (Apr 21, 2023):
I too am having issues - updated to v2.10.2, proxies are working, but can't administer them
I've followed all the above advice, but still have a blank list :(
@AlexKusnezov @Bark33p3r @popallo can any of you help me?
@funky123 commented on GitHub (May 27, 2023):
i have same issue. can login with default creds but cant mange my hosts etc.
Upgraded from Version v2.9.18 to v2.10.3
@wodan66 commented on GitHub (Jul 4, 2023):
mv mysql out of data and adjust the docker compose file accordingly solved my issues as well.
Thanks
@github-actions[bot] commented on GitHub (Jan 24, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@Eremar87 commented on GitHub (Mar 25, 2024):
I have the same problem. After update, i can't manage my hosts (which works at moment...).
I tried to move db outside data, chmod 777 but nothing works.
Can you help me? I'm not expert so pls be more clear. I tried to adjust my docker configuration, but I'm doing wrong.
I use portainer to manage everything on a raspy.
The db and nginx app seems working...
@github-actions[bot] commented on GitHub (Nov 12, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Dec 1, 2025):
Issue was closed due to inactivity.