#Nginx Proxy Manager gives 502 Bad Gateway when logging in

1 messages · Page 1 of 1 (latest)

rare coral
#

I haven't visited the dashboard in a while, so I have no idea when this became a problem. Whenever I click login details I get a 502 Bad Gateway response. It doesn't matter if the login details are correct or not.
In the add-on logs I get this error when sending the login request:
2024/12/08 21:19:36 [error] 6393#6393: *6932 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.178.32, server: nginxproxymanager, request: "POST /api/tokens HTTP/1.1", upstream: "http://127.0.0.1:3000/tokens", host: "homeassistant.local:81", referrer: "http://homeassistant.local:81/login"
I also see that the add-on restarts itself incredibly often for an unknown reason:

[21:39:37] INFO: Starting the Manager...
[12/8/2024] [9:39:49 PM] [Global   ] › ℹ  info      Using Sqlite: /config/database.sqlite
[21:40:18] INFO: Service Nginx Proxy Manager exited with code 256 (by signal 9)
[21:40:21] INFO: Starting the Manager...
[12/8/2024] [9:40:32 PM] [Global   ] › ℹ  info      Using Sqlite: /config/database.sqlite
[21:41:17] INFO: Service Nginx Proxy Manager exited with code 256 (by signal 9)
[21:41:20] INFO: Starting the Manager...
[12/8/2024] [9:41:28 PM] [Global   ] › ℹ  info      Using Sqlite: /config/database.sqlite
[21:41:44] INFO: Service Nginx Proxy Manager exited with code 256 (by signal 9)
[21:41:46] INFO: Starting the Manager...
[12/8/2024] [9:41:52 PM] [Global   ] › ℹ  info      Using Sqlite: /config/database.sqlite
[21:42:38] INFO: Service Nginx Proxy Manager exited with code 256 (by signal 9)
[21:42:40] INFO: Starting the Manager...```
I also don't see a way to increase the logging level for the add-on to possible get some more useful info on the error. If anybody could push me into a possible helpful direction, that'd be great.
jolly spear
#

It seems sqlite database is not initiated or readable. Do you have the correct permissions to the database? Can you try running NPM as standalone container or reinstall NPM again? In both cases, you might lose data.