nginx-proxy-manager: Error: Can't login to NPM-Dashboard "Bad Gateway" - v2.11.0 (latest)
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image?- Yes
- Are you sure you’re not using someone else’s docker image?
- Yes
- Have you searched for similar issues (both open and closed)?
- Yes
Describe the bug
After I’ve upgraded to the latest version v2.11.0, the login to the NPM-Dashboard no longer works (npm-ip:81). As a side note, the upgrade was performed automatically on my server because I always use the “latest” version of the Docker image.
The log shows that no further entries follow the block below:
-------------------------------------
_ _ ____ __ __
| \ | | _ \| \/ |
| \| | |_) | |\/| |
| |\ | __/| | | |
|_| \_|_| |_| |_|
-------------------------------------
User: npm PUID:0 ID:0 GROUP:0
Group: npm PGID:0 ID:0
-------------------------------------
❯ Starting nginx ...
❯ Starting backend ...
[1/19/2024] [12:07:04 PM] [Global ] › ℹ info Using MySQL configuration
[1/19/2024] [12:07:05 PM] [Migrate ] › ℹ info Current database version: 20211108145214
When rolling back to the previous version v2.10.4, the problem could be “fixed”, a login in the dashboard was possible again.
Nginx Proxy Manager Version v2.11.0 (latest, as of date 19.01.2024)
To Reproduce Steps to reproduce the behavior:
- Go to npm-ip:81
- Insert credentials
- Click on “Sign in”
- Error message “Bad Gateway” appears
Expected behavior
Login should be possible, as it was in the previous version.
Screenshots
Operating System
Ubuntu Server 22.04.3 LTS
Additional context
/None/
About this issue
- Original URL
- State: closed
- Created 5 months ago
- Reactions: 26
- Comments: 41 (1 by maintainers)
As @ToxicToxster has identified, yes this only affects startup where there are certs but none of them have DNS challenges.
I’ve pushed a fix to
developbranch, just waiting for a build and I can run a full test of the circumstance.I found the solution. Problem is when no certificates have dns-challenge. setup.js would need this small code:
if (!plugins.length) return;added before:return certbot.installPlugins(plugins);I have this problem as well. If you downgrade to the last version it works again with your normal login/configurations still working. Just change the image line in your docker compose from
image: 'jc21/nginx-proxy-manager:latest'toimage: 'jc21/nginx-proxy-manager:2.10.4'and re-deploy. Hopefully it’s possible to find a real fix to this issue so we can update nginx proxy manager.downgrading to :2.10.4 solved this issue for me to.
I would like to remind people that “same issue” posts aren’t really helpful, they just spam the inbox of people who are subscribed to this issue. I think it’s pretty clear by now that upgrading from 2.10.4 to 2.11.0 introduces a bug.
An update on my situation:
I downgraded to 2.10.3 and removed the NODE_OPTIONS=–openssl-legacy-provider environment variable. The container came up fine and I was able to log in. I restarted the container multiple times and was able to log in after each restart.
I upgraded to 2.10.4. As before, container came up good and was able to restart/login with no issues.
I upgraded to 2.11.0 (this time using the latest tag) and saw the following in the console:
Configuring npm user ... useradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range.It appears that TheUntouchable commented on this earlier. Now I am unable to log in.From here, I downgraded back to 2.10.4 and removed the NODE_OPTIONS=–openssl-legacy-provider environment variable again. BOOM. I’m able to log back in.
I still have no clue why my intranet NPM container on 2.11.0 is working fine, even after a restart.
I get also the “Bad Gateway” message and additionally the Docker health status says:
parse error: Invalid numeric literal at line 1, column 7 NOT OKAlso, I had this in the log after first start with the new container:
❯ Configuring npm user ... useradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range.Second start seems to be ok, but still unhealthy and the “Bad gateway” error.
❯ Configuring npm user ... 0 usermod: no changesI have the same problem.
“Current database version: none” is normal when using the internal Sqlite
I have the same problem.
same problem as op for me on 2 different installation
Login again possible with Docker image 2.11.1 - thank you jc21! Status also “Healthy” now
Hi all, same for me.
As far as i can see, starting logs with 2.10.4 are:
vs 2.11.0:
Obviously services are not launching on the new version of the image.
same here…
change in docker compose
image: 'jc21/nginx-proxy-manager:2.10.4'solve issue, but use old version (of course)
thank you
Same problem. Beside that database version shows none, but not sure if this was always the case with sqlite.
[1/19/2024] [9:26:27 PM] [Global ] › ℹ info Using Sqlite: /data/database.sqlite [1/19/2024] [9:26:28 PM] [Migrate ] › ℹ info Current database version: none