[GH-ISSUE #1272] Bad Gateway Bug in 2.9.x tried everything now what? #1027

New issue

Closed

opened 2026-02-26 06:35:29 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:35:29 +03:00

Owner

Originally created by @jackwan1 on GitHub (Jul 28, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1272

I am at the end of the rope, need help on Bad Gateway issues
[
docker-compose - Copy.txt
](URL)
Attached docker compose yaml has all my compose version, error log(as comment in the beginning and the latest yaml

I have rolledback proxy manager version to 2.9.4 as some poster suggested
I have put in the IP address for the SQL database instead of db
I have disabled IP v6
I have changed mariadb designation several times

What should I do now? I read somewhere that the proxy manager coding pointing 80 traffic to 443 but I do not know where to find and how to recompile? I also read to delete json file, but I cannot find it.

Please advise.

Originally created by @jackwan1 on GitHub (Jul 28, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1272 I am at the end of the rope, need help on Bad Gateway issues [ [docker-compose - Copy.txt](https://github.com/jc21/nginx-proxy-manager/files/6895429/docker-compose.-.Copy.txt) ](URL) Attached docker compose yaml has all my compose version, error log(as comment in the beginning and the latest yaml 1. I have rolledback proxy manager version to 2.9.4 as some poster suggested 2. I have put in the IP address for the SQL database instead of db 3. I have disabled IP v6 4. I have changed mariadb designation several times What should I do now? I read somewhere that the proxy manager coding pointing 80 traffic to 443 but I do not know where to find and how to recompile? I also read to delete json file, but I cannot find it. Please advise.

kerem

2026-02-26 06:35:29 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:35:29 +03:00

Author

Owner

@jackwan1 commented on GitHub (Jul 28, 2021):

I now have followed the comments in
https://github.com/jc21/nginx-proxy-manager/issues/310#issuecomment-603552819
to add a config.json file with recommended contents and change all my yaml to corresponding environmental variables.
But it still does not work.

docker-compose error message as follows
[7/28/2021] [6:38:51 PM] [Global ] › ℹ info Generating MySQL db configuration from environment variables
[7/28/2021] [6:38:51 PM] [Global ] › ℹ info Wrote db configuration to config file: ./config/production.json
[7/28/2021] [6:38:59 PM] [Global ] › ✖ error ER_ACCESS_DENIED_ERROR: Access denied for user 'npm'@'172.21.0.3' (using password: YES)
[7/28/2021] [6:39:00 PM] [Global ] › ✖ error ER_ACCESS_DENIED_ERROR: Access denied for user 'npm'@'172.21.0.3' (using password: YES)
[7/28/20

@jackwan1 commented on GitHub (Jul 28, 2021): I now have followed the comments in https://github.com/jc21/nginx-proxy-manager/issues/310#issuecomment-603552819 to add a config.json file with recommended contents and change all my yaml to corresponding environmental variables. But it still does not work. docker-compose error message as follows [7/28/2021] [6:38:51 PM] [Global ] › ℹ info Generating MySQL db configuration from environment variables [7/28/2021] [6:38:51 PM] [Global ] › ℹ info Wrote db configuration to config file: ./config/production.json [7/28/2021] [6:38:59 PM] [Global ] › ✖ error ER_ACCESS_DENIED_ERROR: Access denied for user 'npm'@'172.21.0.3' (using password: YES) [7/28/2021] [6:39:00 PM] [Global ] › ✖ error ER_ACCESS_DENIED_ERROR: Access denied for user 'npm'@'172.21.0.3' (using password: YES) [7/28/20

kerem commented

2026-02-26 06:35:29 +03:00

Author

Owner

@jackwan1 commented on GitHub (Jul 28, 2021):

ok I got it fixed, see comment
https://github.com/jc21/nginx-proxy-manager/issues/1161#issuecomment-856167204
I took out everything and replaced my yaml to sql-lite and it worked

@jackwan1 commented on GitHub (Jul 28, 2021): ok I got it fixed, see comment https://github.com/jc21/nginx-proxy-manager/issues/1161#issuecomment-856167204 I took out everything and replaced my yaml to sql-lite and it worked

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#1027

No description provided.

Rows
Columns