nginx-proxy-manager: Logging into the admin interface no longer works. Mistake: Internal Error

give right to the data and letsencrypt folder it’s 911 now (without puid or guid) chown 0777 worked for me

Thanks for this, this fixed my issues aswell after trying to troubleshoot it for 3 hours

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.

This is the next issue after the chown 0777 thankfully my hosts are working again, just can’t access the npm to configure them

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.

Great, Thanks a lot for the advise!!! Now it works.

nobrainer instruction for people like me: Update your docker Loginin with:

• Email: admin@example.com
• Password: changeme

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

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.

@popallo nevermid, I solved this now:

Since I had to change /mnt/nginx-proxy-manager/data/mysql:/var/lib/mysql to /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:

volumes: - /mnt/nginx-proxy-manager/config.json:/app/config/production.json

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

same here No relevant user found

Just installed 2.10.2 . Still the same problem.

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.

same here No relevant user found

give right to the data and letsencrypt folder it’s 911 now (without puid or guid) chown 0777 worked for me

Thanks for this, this fixed my issues aswell after trying to troubleshoot it for 3 hours

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.

This is the next issue after the chown 0777 thankfully my hosts are working again, just can’t access the npm to configure them

give right to the data and letsencrypt folder it’s 911 now (without puid or guid) chown 0777 worked for me