Bad Gateway

[smnhdy]

• 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.

[lukasztomalczyk]

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]

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

[smnhdy]

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.

[TheDogHusky]

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.

[github-actions[bot]]

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