starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #3785] Bad Gateway #2492

New issue

Closed

opened 2026-02-26 07:35:46 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 07:35:46 +03:00

Owner

Originally created by @smnhdy on GitHub (May 30, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3785

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker 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

Following a reboot today, when logging into the portal i get the "Bad Gateway" error after clicking signin.

2.11.2 version

To Reproduce
Sign in.

Originally created by @smnhdy on GitHub (May 30, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3785 - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker 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 Following a reboot today, when logging into the portal i get the "Bad Gateway" error after clicking signin. 2.11.2 version **To Reproduce** Sign in.

kerem

2026-02-26 07:35:46 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:35:46 +03:00

Author

Owner

@lukasztomalczyk commented on GitHub (Jun 2, 2024):

I have the same problem. This is my docker-compose:

version: '3.3'
services:
nginx-proxy-manager:
image: 'jc21/nginx-proxy-manager:latest'
restart: always
ports:
- '80:80' # HTTP
- '81:81' # Web UI
- '443:443' # HTTPS
environment:
DB_MYSQL_HOST: "db"
DB_MYSQL_PORT: 3306
DB_MYSQL_USER: "npm"
DB_MYSQL_PASSWORD: "npm"
DB_MYSQL_NAME: "npm"
depends_on:
- mariadb-aria
volumes:
- C:\Users\lukas\source\repos\DevOps\docker-compose\nginx-proxy-manager\data:/data
- C:\Users\lukas\source\repos\DevOps\docker-compose\nginx-proxy-manager\certificates:/etc/letsencrypt
mariadb-aria:
image: 'jc21/mariadb-aria:latest'
restart: always
environment:
MYSQL_ROOT_PASSWORD: 'npm'
MYSQL_DATABASE: 'npm'
MYSQL_USER: 'npm'
MYSQL_PASSWORD: 'npm'
volumes:
- C:\Users\lukas\source\repos\DevOps\docker-compose\nginx-proxy-manager\sql-data:/var/lib/mysql

@lukasztomalczyk commented on GitHub (Jun 2, 2024): I have the same problem. This is my docker-compose: version: '3.3' services: nginx-proxy-manager: image: 'jc21/nginx-proxy-manager:latest' restart: always ports: - '80:80' # HTTP - '81:81' # Web UI - '443:443' # HTTPS environment: DB_MYSQL_HOST: "db" DB_MYSQL_PORT: 3306 DB_MYSQL_USER: "npm" DB_MYSQL_PASSWORD: "npm" DB_MYSQL_NAME: "npm" depends_on: - mariadb-aria volumes: - C:\Users\lukas\source\repos\DevOps\docker-compose\nginx-proxy-manager\data:/data - C:\Users\lukas\source\repos\DevOps\docker-compose\nginx-proxy-manager\certificates:/etc/letsencrypt mariadb-aria: image: 'jc21/mariadb-aria:latest' restart: always environment: MYSQL_ROOT_PASSWORD: 'npm' MYSQL_DATABASE: 'npm' MYSQL_USER: 'npm' MYSQL_PASSWORD: 'npm' volumes: - C:\Users\lukas\source\repos\DevOps\docker-compose\nginx-proxy-manager\sql-data:/var/lib/mysql

kerem commented

2026-02-26 07:35:46 +03:00

Author

Owner

@lukasztomalczyk commented on GitHub (Jun 2, 2024):

Ok I found the problem... by mistake, the web interface connected to the sql service via the domain name "db". However, I changed the name of the service to a different one "mariadb-aria".

@smnhdy check your docker-compose

@lukasztomalczyk commented on GitHub (Jun 2, 2024): Ok I found the problem... by mistake, the web interface connected to the sql service via the domain name "db". However, I changed the name of the service to a different one "mariadb-aria". @smnhdy check your docker-compose

kerem commented

2026-02-26 07:35:46 +03:00

Author

Owner

@smnhdy commented on GitHub (Jun 3, 2024):

I gave up in the ends I respired from a backup from a few weeks back and it's all back up and running again.

I didn't make any changes to anything so unsure what happened.

@smnhdy commented on GitHub (Jun 3, 2024): I gave up in the ends I respired from a backup from a few weeks back and it's all back up and running again. I didn't make any changes to anything so unsure what happened.

kerem commented

2026-02-26 07:35:46 +03:00

Author

Owner

@TheDogHusky commented on GitHub (Jun 11, 2024):

I gave up in the ends I respired from a backup from a few weeks back and it's all back up and running again.

I didn't make any changes to anything so unsure what happened.

I had this issue, just had to wait until NPM fully started.

@TheDogHusky commented on GitHub (Jun 11, 2024): > I gave up in the ends I respired from a backup from a few weeks back and it's all back up and running again. > > I didn't make any changes to anything so unsure what happened. I had this issue, just had to wait until NPM fully started.

kerem commented

2026-02-26 07:35:46 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 26, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Dec 26, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:35:46 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 17, 2026):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Jan 17, 2026): Issue was closed due to inactivity.

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#2492

No description provided.

Rows
Columns