NPM not connected to database, but still working #2732
-
Hi! I want to start to say that all of my proxied sites are working as intentional. However, when I login to the Nginx Proxy Manager Admin GUI it is connected to the wrong database. The logs are posted below:
The logs tell me there is Below is my configuration via docker-compose:
I also use adminer and can access the database just fine with it. This got me very confused, because the reverse proxy is working for all sites and at the same time I can only login to the NPM Admin GUI via the default credentials. I have tried to restart NPM several times without any success. Can someone help me to understand what is going on? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
I am having a similar behavior, difference is that this is a totally new setup. From the run:
It looks those 2 scripts have the wrong perms. NPM seems to be running, but not responding
So I would also like to know how to fix this |
Beta Was this translation helpful? Give feedback.
-
@Isgleas Thanks for your response. I think I've figured this one out now. The problem is with the secrets. Everything works as expect if I change the secrets from:
To:
In the latest release @jc21 said that they've removed some leftover scripts from s6-overlay v2 that, while still supported by s6-overlay v3, are no longer required. (link) If I look in the logs I can see this in the beginning:
My best guess is that this broke something with the secrets, but I am not entirely sure. @jc21 What do you think? |
Beta Was this translation helpful? Give feedback.
-
This works again in version 2.10.0. Closing the discussion/issue. |
Beta Was this translation helpful? Give feedback.
This works again in version 2.10.0. Closing the discussion/issue.