nginx-proxy-manager: Upgrading from 2.10.4 to 2.11.0 causes 502 for API endpoints

Checklist

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

Describe the bug

When I run docker compose pull, then docker compose up -d on my NPM instance and then go to the login page and try to login, it responds with a 502 error. The login page loads and all proxy hosts seem to be online, it’s just the API endpoints.

I viewed the logs using docker compose logs and it stops at:

[1/19/2024] [5:15:29 AM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite
[1/19/2024] [5:15:29 AM] [Migrate  ] › ℹ  info      Current database version: none

I tried booting up a brand new instance of 2.11.0 and it works fine.

Nginx Proxy Manager Version

Upgrading from 2.10.4 to 2.11.0

To Reproduce Steps to reproduce the behavior:

Have an existing NPM instance on 2.10.4 with some proxy hosts
Attempt to upgrade it to 2.11.0
See 502 Bad Gateway error on login screen

Expected behavior

I expected to be able to login and for the app to load properly.

Screenshots

Operating System

Ubuntu 22 LTS 64-bit

Additional context

About this issue

Original URL
State: closed
Created 5 months ago
Reactions: 19
Comments: 33 (1 by maintainers)

Most upvoted comments

I’m getting insanely frustrated with how consistently this project breaks between updates, I’ve had to recreate my proxy setup on several occasions because of breakages between versions. I’m getting really fed up, this is probably the 4th time in about a year of using this I’ve had to downgrade to solve a bug.

+17

CorneliusCornbread on Jan 19, 2024

hi,

i have the Same Problem. Update to 2.11.0 an can Not login. I think we Need a Version 2.11.1 😂

+12

skipperkm on Jan 19, 2024

same here, downgrade to 2.10.4 fixes the problem

bazziebaz on Jan 19, 2024

Same issue.

MiRen76 on Jan 19, 2024

same here, downgrade to 2.10.4 fixes the problem

That’s what I’ve done for now, but I would like to see a solution or fix for this still.

wdhdev on Jan 19, 2024

I posted a bug fix for implementation in #3475

ToxicToxster on Jan 21, 2024

The same problem here. I have also tried a new installation. The initial login works, but when you log out and try to log in again, all you get is “Bad Gateway”.

Momentum6890 on Jan 20, 2024

Same problem here… how do you downgrade tho ?

In my case: i changed ‘latest’ to ‘2.10.4’ in my docker compose file. Restarted the thing.

version: ‘3’ services: app: image: ‘jc21/nginx-proxy-manager:2.10.4’ restart: unless-stopped ports: - 80:80 - 40000:81 - 443:443 volumes: - data:/data - letsencrypt:/etc/letsencrypt volumes: data: letsencrypt:

bazziebaz on Jan 19, 2024

Same here, using external mariadb (latest version with auto upgrade on) hangs, it’s been like this for 1 hour, so no errors, no progress on db migration

version: "3.9"

secrets:
  mariadb_labo_pwd:
    file: /home/labo/docker/.secrets/mariadb_labo_pwd.txt

services:
  nginx_proxy_manager:
    container_name: NginxProxyManager
    image: jc21/nginx-proxy-manager:latest
    restart: unless-stopped
    networks:
      - bridge_labo
    ports:
      # Public HTTP Port:
      - 80:80
      # Public HTTPS Port:
      - 443:443
      - 443:443/udp
      # Admin Web Port:
      - 81:81
    environment:
      PUID: 1000
      PGID: 1000
      TZ: Europe/Rome
      # These are the settings to access your db
      DB_MYSQL_HOST: mariadb
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: redacted
      DB_MYSQL_PASSWORD__FILE: /run/secrets/mariadb_labo_pwd
      DB_MYSQL_NAME: npm
      DISABLE_IPV6: "true"
    volumes:
      - /home/labo/docker/npm/data:/data
      - /home/labo/docker/npm/letsencrypt:/etc/letsencrypt
    secrets:
      - mariadb_labo_pwd
    logging:
      options:
        max-size: 10m
        max-file: "5"
    healthcheck:
      test: ["CMD", "/bin/check-health"]
      interval: 10s
      timeout: 3s

networks:
  bridge_labo:
    external: true

labodj on Jan 19, 2024

Using mariadb the migration of the database hangs.

JBlond on Jan 19, 2024