nginx-proxy-manager icon indicating copy to clipboard operation
nginx-proxy-manager copied to clipboard
Published 3 weeks ago • verified publisher icon NginxProxyManager

[Solved?] After update from 2.9.19 to 2.10.4, "Bad gateway" on local port 81 login screen, but sites keep functioning

Open Moonbase59 opened this issue 2 years ago • 38 comments

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

I’m not much into docker yet but I succeeded to install NPM 2.9.19 a few months ago and now realized I must make manual updates. So I logged into my Proxmox LXC container and did a docker-compose pull, which apparently brought me to v2.10.4 (shown on port 81 local login screen).

But now on every login attempt, I get a little red "Bad gateway" shown on the login screen and cannot administer my hosts anymore! For the time being, I reverted to my full LXC backup and went back to 2.9.19, which works fine.

docker ps shows I’m running jc21/mariadb-aria:latest and jc21/nginx-proxy-manager:latest.

I don’t know how to diagnose this, or where the logs are kept, help urgently needed.

Nginx Proxy Manager Version

2.10.4

To Reproduce Steps to reproduce the behavior:

  1. Log into LXC using ssh.
  2. docker-compose pull, docker-compose down, docker-compose up -d
  3. Sites keep functioning.
  4. Port 81 login screen shows 2.10.4 and "Bad Gateway" upon login attempt.

Expected behavior

Local admin login working.

Screenshots

Auswahl_274

Operating System

Proxmox 7.4, unprivileged Ubuntu 22.04.3 LTS LXC

Additional context

Commands used to update:

root@proxy:/home/admin/npm# docker-compose pull
Pulling app ... done
Pulling db  ... done
root@proxy:/home/admin/npm# docker-compose down
Stopping npm-db-1  ... done
Stopping npm-app-1 ... done
Removing npm-db-1  ... done
Removing npm-app-1 ... done
Removing network npm_default
root@proxy:/home/admin/npm# docker-compose up -d
Creating network "npm_default" with the default driver
Creating npm_db_1  ... done
Creating npm_app_1 ... done
root@proxy:/home/admin/npm#

Docker version:

Client: Docker Engine - Community
 Version:           24.0.6
 API version:       1.43
 Go version:        go1.20.7
 Git commit:        ed223bc
 Built:             Mon Sep  4 12:31:44 2023
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          24.0.6
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.7
  Git commit:       1a79695
  Built:            Mon Sep  4 12:31:44 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.24
  GitCommit:        61f9fd88f79f081d64d6fa3bb1a0dc71ec870523
 runc:
  Version:          1.1.9
  GitCommit:        v1.1.9-0-gccaecfc
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker ps output:

root@proxy:/home/admin/npm# docker ps
CONTAINER ID   IMAGE                             COMMAND             CREATED         STATUS         PORTS                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          NAMES
6557ba6f70d7   jc21/nginx-proxy-manager:latest   "/init"             4 minutes ago   Up 3 minutes   0.0.0.0:70->70/tcp, :::70->70/tcp, 0.0.0.0:80-81->80-81/tcp, :::80-81->80-81/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 0.0.0.0:2022->2022/tcp, :::2022->2022/tcp, 0.0.0.0:3478->3478/tcp, :::3478->3478/tcp, 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp, 0.0.0.0:5222->5222/tcp, :::5222->5222/tcp, 0.0.0.0:5269->5269/tcp, :::5269->5269/tcp, 0.0.0.0:5280-5281->5280-5281/tcp, :::5280-5281->5280-5281/tcp, 0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 0.0.0.0:8005-8006->8005-8006/tcp, :::8005-8006->8005-8006/tcp, 0.0.0.0:8010->8010/tcp, :::8010->8010/tcp, 0.0.0.0:8015-8016->8015-8016/tcp, :::8015-8016->8015-8016/tcp, 0.0.0.0:8883->8883/tcp, :::8883->8883/tcp   npm_app_1
3f9778d06a3f   jc21/mariadb-aria:latest          "/scripts/run.sh"   4 minutes ago   Up 3 minutes   3306/tcp                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       npm_db_1

docker-compose.yml

version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    environment:
      DB_MYSQL_HOST: "db"
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: "npm"
      DB_MYSQL_PASSWORD: "(PASSWORD)"
      DB_MYSQL_NAME: "npm"
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
  db:
    image: 'jc21/mariadb-aria:latest'
    restart: unless-stopped
    environment:
      MYSQL_ROOT_PASSWORD: '(PASSWORD)'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'npm'
      MYSQL_PASSWORD: '(PASSWORD)'
    volumes:
      - ./data/mysql:/var/lib/mysql

docker-compose.override.yml

root@proxy:/home/admin/npm# cat docker-compose.override.yml 
# Add some radio ports to be handled by NGINX Proxy Manager.
# These will be forwarded as "streams" in NPM.
# Needs MyFritz-Freigabe to this proxy server!
services:
  app:
    ports:
      # BLOG
      - '70:70' # gopher
      # RADIO
      - '2022:2022' # SFTP
      # 8000 is in use by portainer, can't be bound here!
      - '8000:8000' # station 1 - listen
      - '8005:8005' # station 1 - DJ Stream Icecast
      - '8006:8006' # station 1 - DJ Stream Shoutcast
      - '8010:8010' # station 2 - listen
      - '8015:8015' # station 2 - DJ Stream Icecast
      - '8016:8016' # station 2 - DJ Stream Shoutcast
      # HOME ASSISTANT
      - '8883:8883' # HA MQTT
      # NEXTCLOUD
      - '3478:3478' # NextCloud Talk (TCP & UDP)
      # CHAT1 (Prosody)
      - '5000:5000' # Prosody file transfer proxy
      - '5222:5222' # Prosody client connections
      - '5269:5269' # Prosody server-to-server connections
      - '5280:5280' # Prosody HTTP
      - '5281:5281' # Prosody HTTPS

Moonbase59 avatar Oct 04 '23 12:10 Moonbase59

I found I can do a docker-compose logs app, which shows a lot of migration errors. Hope this helps:

2023-10-04 npm-log.log

Moonbase59 avatar Oct 04 '23 12:10 Moonbase59

Ah, I think I managed! I read in some other issue that due to ownership problems the MariaDB and NPM persistent volumes must be separate, so I moved my mysql folder out of the data folder into a separate folder.

Before

npm
|-- data
    |-- mysql
|-- letsencrypt

After

npm
|-- data
|-- letsencrypt
|-- mysql

These were the steps I did in the console:

cd ~/npm
docker-compose down
mv data/mysql mysql

Edit docker-compose.yml (change db persistent volume)

version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    environment:
      DB_MYSQL_HOST: "db"
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: "npm"
      DB_MYSQL_PASSWORD: "(PASSWORD)"
      DB_MYSQL_NAME: "npm"
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
  db:
    image: 'jc21/mariadb-aria:latest'
    restart: unless-stopped
    environment:
      MYSQL_ROOT_PASSWORD: '(PASSWORD)'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'npm'
      MYSQL_PASSWORD: '(PASSWORD)'
    volumes:
      #- ./data/mysql:/var/lib/mysql
      - ./mysql:/var/lib/mysql

Continue in console

docker-compose pull
docker-compose up -d

Result

I can now log in again using the local address and port 81. No "Bad Gateway" anymore.

The docker-compose logs shows no errors anymore:

Attaching to npm_app_1, npm_db_1
app_1  | ❯ Configuring npm user ...
app_1  | ❯ Configuring npm group ...
app_1  | ❯ Checking paths ...
app_1  | ❯ Setting ownership ...
app_1  | ❯ Dynamic resolvers ...
app_1  | ❯ IPv6 ...
app_1  | Enabling IPV6 in hosts in: /etc/nginx/conf.d
app_1  | - /etc/nginx/conf.d/include/proxy.conf
app_1  | - /etc/nginx/conf.d/include/block-exploits.conf
app_1  | - /etc/nginx/conf.d/include/ssl-ciphers.conf
app_1  | - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
app_1  | - /etc/nginx/conf.d/include/force-ssl.conf
app_1  | - /etc/nginx/conf.d/include/assets.conf
app_1  | - /etc/nginx/conf.d/include/ip_ranges.conf
app_1  | - /etc/nginx/conf.d/include/resolvers.conf
app_1  | - /etc/nginx/conf.d/default.conf
app_1  | - /etc/nginx/conf.d/production.conf
app_1  | Enabling IPV6 in hosts in: /data/nginx
app_1  | - /data/nginx/proxy_host/4.conf
app_1  | - /data/nginx/proxy_host/6.conf
app_1  | - /data/nginx/proxy_host/3.conf
app_1  | - /data/nginx/proxy_host/5.conf
app_1  | - /data/nginx/proxy_host/7.conf
app_1  | - /data/nginx/proxy_host/2.conf
app_1  | - /data/nginx/stream/4.conf
app_1  | - /data/nginx/stream/9.conf
app_1  | - /data/nginx/stream/6.conf
app_1  | - /data/nginx/stream/15.conf
app_1  | - /data/nginx/stream/10.conf
app_1  | - /data/nginx/stream/14.conf
app_1  | - /data/nginx/stream/12.conf
app_1  | - /data/nginx/stream/13.conf
app_1  | - /data/nginx/stream/5.conf
app_1  | - /data/nginx/stream/7.conf
app_1  | - /data/nginx/stream/11.conf
app_1  | - /data/nginx/stream/8.conf
app_1  | - /data/nginx/default_host/site.conf
app_1  | ❯ Docker secrets ...
app_1  | 
app_1  | -------------------------------------
app_1  |  _   _ ____  __  __
app_1  | | \ | |  _ \|  \/  |
app_1  | |  \| | |_) | |\/| |
app_1  | | |\  |  __/| |  | |
app_1  | |_| \_|_|   |_|  |_|
app_1  | -------------------------------------
app_1  | User:  npm PUID:0 ID:0 GROUP:0
app_1  | Group: npm PGID:0 ID:0
app_1  | -------------------------------------
app_1  | 
app_1  | ❯ Starting nginx ...
app_1  | ❯ Starting backend ...
app_1  | [10/4/2023] [1:14:08 PM] [Global   ] › ℹ  info      Using MySQL configuration
app_1  | [10/4/2023] [1:14:09 PM] [Migrate  ] › ℹ  info      Current database version: 20211108145214
app_1  | [10/4/2023] [1:14:09 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
app_1  | [10/4/2023] [1:14:09 PM] [Setup    ] › ℹ  info      Logrotate completed.
app_1  | [10/4/2023] [1:14:09 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
app_1  | [10/4/2023] [1:14:09 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
app_1  | [10/4/2023] [1:14:09 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
db_1   | 2023-10-04 13:13:40 0 [Note] /usr/bin/mysqld (mysqld 10.4.15-MariaDB) starting as process 1 ...
db_1   | [i] pre-init.d - processing /scripts/pre-init.d/01_secret-init.sh
db_1   | [i] mysqld not found, creating....
db_1   | [i] MySQL directory already present, skipping creation
db_1   | 2023-10-04 13:13:40 0 [Note] Plugin 'InnoDB' is disabled.
db_1   | 2023-10-04 13:13:40 0 [Note] Plugin 'FEEDBACK' is disabled.
db_1   | 2023-10-04 13:13:40 0 [Note] Server socket created on IP: '::'.
db_1   | 2023-10-04 13:13:40 0 [Warning] 'user' entry '@4cbbcd2cdde2' ignored in --skip-name-resolve mode.
db_1   | 2023-10-04 13:13:40 0 [Warning] 'proxies_priv' entry '@% root@4cbbcd2cdde2' ignored in --skip-name-resolve mode.
db_1   | 2023-10-04 13:13:40 0 [Note] Reading of all Master_info entries succeeded
db_1   | 2023-10-04 13:13:40 0 [Note] Added new Master_info '' to hash table
db_1   | 2023-10-04 13:13:40 0 [Note] /usr/bin/mysqld: ready for connections.
db_1   | Version: '10.4.15-MariaDB'  socket: '/run/mysqld/mysqld.sock'  port: 3306  MariaDB Server

I leave this open for others to find (for now) and kindly ask the developers or someone more knowledgeable to confirm that what I did is correct.

After all, NPM is a critical part of the infrastructure and needs to be secure and updatable.

Thanks for giving us this great piece of software!

Moonbase59 avatar Oct 04 '23 13:10 Moonbase59

Thanks a lot for sharing. It worked for me

🙏

conichonhaa avatar Oct 04 '23 16:10 conichonhaa

I was looking for a fix for month - this worked like a charm. Thank you so much...

not1q84-1 avatar Nov 03 '23 23:11 not1q84-1

thanks,it is really help me.

sleepystrigiformes avatar Nov 05 '23 09:11 sleepystrigiformes

confirm the fix worked for me- moving the db folder up one level

adamphetamine avatar Dec 06 '23 01:12 adamphetamine

I would assume that if the sqlite db file is located in the /data folder move it one up so mv xxx.slq ../

not1q84-1 avatar Dec 07 '23 13:12 not1q84-1

Thank you! This fixed it for me been running 2.9.19 forever.

boostedgti916 avatar Dec 12 '23 20:12 boostedgti916

I would assume that if the sqlite db file is located in the /data folder move it one up so mv xxx.slq ../

Doesn't work

caioolivv avatar Dec 21 '23 14:12 caioolivv

How to address this if one is using database.sqlite?

psychogun avatar Dec 25 '23 13:12 psychogun

I would assume that if the sqlite db file is located in the /data folder move it one up so mv xxx.slq ../

Doesn't work

Same here. Just upgraded npm to 2.11.0 from 2.10.4 and got hit by the Bad gateway-message - again. Luckily I had a snapshot of the vm running portainer and npm.

Also, moving database.sqlite up a level from data/ gives me a "no user related content" or some such at the login screen.

Checking the logs after starting up npm 2.11.0, the log output stops after [Migrate ].

...
app_1  | -------------------------------------
app_1  |  _   _ ____  __  __
app_1  | | \ | |  _ \|  \/  |
app_1  | |  \| | |_) | |\/| |
app_1  | | |\  |  __/| |  | |
app_1  | |_| \_|_|   |_|  |_|
app_1  | -------------------------------------
app_1  | User:  npm PUID:0 ID:0 GROUP:0
app_1  | Group: npm PGID:0 ID:0
app_1  | -------------------------------------
app_1  |
app_1  | ❯ Starting nginx ...
app_1  | ❯ Starting backend ...
app_1  | [1/19/2024] [9:44:55 AM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite
app_1  | [1/19/2024] [9:45:01 AM] [Migrate  ] › ℹ  info      Current database version: none

With npm 2.10.4 it continues with logrotate, ssl renewals etc.

adrianvg avatar Jan 19 '24 09:01 adrianvg

Same here with sqlite

Spillebulle avatar Jan 19 '24 11:01 Spillebulle

Если удалить полностью файлик database.sqlite тогда создается новая учетная запись и все работает. Если потом перезатереть опять не работает. Проблема в том, что после обновления не читает database.sqlite Как выйти с этой ситуации?

SX2-NAME avatar Jan 19 '24 11:01 SX2-NAME

Ah, I think I managed! I read in some other issue that due to ownership problems the MariaDB and NPM persistent volumes must be separate, so I moved my mysql folder out of the data folder into a separate folder.

Before

npm
|-- data
    |-- mysql
|-- letsencrypt

After

npm
|-- data
|-- letsencrypt
|-- mysql

These were the steps I did in the console:

cd ~/npm
docker-compose down
mv data/mysql mysql

Edit docker-compose.yml (change db persistent volume)

version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    environment:
      DB_MYSQL_HOST: "db"
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: "npm"
      DB_MYSQL_PASSWORD: "(PASSWORD)"
      DB_MYSQL_NAME: "npm"
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
  db:
    image: 'jc21/mariadb-aria:latest'
    restart: unless-stopped
    environment:
      MYSQL_ROOT_PASSWORD: '(PASSWORD)'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'npm'
      MYSQL_PASSWORD: '(PASSWORD)'
    volumes:
      #- ./data/mysql:/var/lib/mysql
      - ./mysql:/var/lib/mysql

Continue in console

docker-compose pull
docker-compose up -d

Result

I can now log in again using the local address and port 81. No "Bad Gateway" anymore.

The docker-compose logs shows no errors anymore:

Attaching to npm_app_1, npm_db_1
app_1  | ❯ Configuring npm user ...
app_1  | ❯ Configuring npm group ...
app_1  | ❯ Checking paths ...
app_1  | ❯ Setting ownership ...
app_1  | ❯ Dynamic resolvers ...
app_1  | ❯ IPv6 ...
app_1  | Enabling IPV6 in hosts in: /etc/nginx/conf.d
app_1  | - /etc/nginx/conf.d/include/proxy.conf
app_1  | - /etc/nginx/conf.d/include/block-exploits.conf
app_1  | - /etc/nginx/conf.d/include/ssl-ciphers.conf
app_1  | - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
app_1  | - /etc/nginx/conf.d/include/force-ssl.conf
app_1  | - /etc/nginx/conf.d/include/assets.conf
app_1  | - /etc/nginx/conf.d/include/ip_ranges.conf
app_1  | - /etc/nginx/conf.d/include/resolvers.conf
app_1  | - /etc/nginx/conf.d/default.conf
app_1  | - /etc/nginx/conf.d/production.conf
app_1  | Enabling IPV6 in hosts in: /data/nginx
app_1  | - /data/nginx/proxy_host/4.conf
app_1  | - /data/nginx/proxy_host/6.conf
app_1  | - /data/nginx/proxy_host/3.conf
app_1  | - /data/nginx/proxy_host/5.conf
app_1  | - /data/nginx/proxy_host/7.conf
app_1  | - /data/nginx/proxy_host/2.conf
app_1  | - /data/nginx/stream/4.conf
app_1  | - /data/nginx/stream/9.conf
app_1  | - /data/nginx/stream/6.conf
app_1  | - /data/nginx/stream/15.conf
app_1  | - /data/nginx/stream/10.conf
app_1  | - /data/nginx/stream/14.conf
app_1  | - /data/nginx/stream/12.conf
app_1  | - /data/nginx/stream/13.conf
app_1  | - /data/nginx/stream/5.conf
app_1  | - /data/nginx/stream/7.conf
app_1  | - /data/nginx/stream/11.conf
app_1  | - /data/nginx/stream/8.conf
app_1  | - /data/nginx/default_host/site.conf
app_1  | ❯ Docker secrets ...
app_1  | 
app_1  | -------------------------------------
app_1  |  _   _ ____  __  __
app_1  | | \ | |  _ \|  \/  |
app_1  | |  \| | |_) | |\/| |
app_1  | | |\  |  __/| |  | |
app_1  | |_| \_|_|   |_|  |_|
app_1  | -------------------------------------
app_1  | User:  npm PUID:0 ID:0 GROUP:0
app_1  | Group: npm PGID:0 ID:0
app_1  | -------------------------------------
app_1  | 
app_1  | ❯ Starting nginx ...
app_1  | ❯ Starting backend ...
app_1  | [10/4/2023] [1:14:08 PM] [Global   ] › ℹ  info      Using MySQL configuration
app_1  | [10/4/2023] [1:14:09 PM] [Migrate  ] › ℹ  info      Current database version: 20211108145214
app_1  | [10/4/2023] [1:14:09 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
app_1  | [10/4/2023] [1:14:09 PM] [Setup    ] › ℹ  info      Logrotate completed.
app_1  | [10/4/2023] [1:14:09 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
app_1  | [10/4/2023] [1:14:09 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
app_1  | [10/4/2023] [1:14:09 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
db_1   | 2023-10-04 13:13:40 0 [Note] /usr/bin/mysqld (mysqld 10.4.15-MariaDB) starting as process 1 ...
db_1   | [i] pre-init.d - processing /scripts/pre-init.d/01_secret-init.sh
db_1   | [i] mysqld not found, creating....
db_1   | [i] MySQL directory already present, skipping creation
db_1   | 2023-10-04 13:13:40 0 [Note] Plugin 'InnoDB' is disabled.
db_1   | 2023-10-04 13:13:40 0 [Note] Plugin 'FEEDBACK' is disabled.
db_1   | 2023-10-04 13:13:40 0 [Note] Server socket created on IP: '::'.
db_1   | 2023-10-04 13:13:40 0 [Warning] 'user' entry '@4cbbcd2cdde2' ignored in --skip-name-resolve mode.
db_1   | 2023-10-04 13:13:40 0 [Warning] 'proxies_priv' entry '@% root@4cbbcd2cdde2' ignored in --skip-name-resolve mode.
db_1   | 2023-10-04 13:13:40 0 [Note] Reading of all Master_info entries succeeded
db_1   | 2023-10-04 13:13:40 0 [Note] Added new Master_info '' to hash table
db_1   | 2023-10-04 13:13:40 0 [Note] /usr/bin/mysqld: ready for connections.
db_1   | Version: '10.4.15-MariaDB'  socket: '/run/mysqld/mysqld.sock'  port: 3306  MariaDB Server

I leave this open for others to find (for now) and kindly ask the developers or someone more knowledgeable to confirm that what I did is correct.

After all, NPM is a critical part of the infrastructure and needs to be secure and updatable.

Thanks for giving us this great piece of software!

well, i can see in newer versions that mysql folder is outside data by default, but still facing that same issue

KvizadSaderah avatar Jan 19 '24 12:01 KvizadSaderah

У меня SQLite а не MySQL!!! Путь менять не нужно. Проблем в том что если создать новый database.sqlite все работает. А вот старый нет.

SX2-NAME avatar Jan 19 '24 12:01 SX2-NAME

У меня SQLite а не MySQL!!! Путь менять не нужно. Проблем в том что если создать новый database.sqlite все работает. А вот старый нет.

Translation to english: "I have SQLite and not MySQL!!! There is no need to change the path. The problem is that if you create a new database.sqlite everything works. But the old one doesn't."

If I delete and recreate the sqlite-db, won't I lose all my sites and ssl-certificates?

adrianvg avatar Jan 19 '24 12:01 adrianvg

При создании новой базы, действующие сайты остаются, но управлять ими невозможно! Нужно понять почему после обновления proxy-manager не видит базу. Я надеюсь разработчики исправят это. Пока пришлось откатиться на с 2.11.0 на 2.10.4

Could you please write in English?

adrianvg avatar Jan 19 '24 12:01 adrianvg

When creating a new database, existing sites remain! But it is impossible to control them! You need to understand why after the update proxy-manager does not see the database. I hope the developers will fix this. So far I had to roll back from 2.11.0 to 2.10.4

SX2-NAME avatar Jan 19 '24 12:01 SX2-NAME

I think I was able to replicate this on 2.11.0 by letting the login timeout, clicking around the UI, then browser refresh. At the point, when you go to login again, it will give you a bad gateway error.

Note: My setup consists of the database.sqlite file

lowfoon avatar Jan 19 '24 14:01 lowfoon

When creating a new database, existing sites remain! But it is impossible to control them! You need to understand why after the update proxy-manager does not see the database. I hope the developers will fix this. So far I had to roll back from 2.11.0 to 2.10.4

This! This really is the only way to make it running again if you are using SQLite like me. Use the image jc21/nginx-proxy-manager:2.10.4, until the developers get it to work again with a newer version.

taffit avatar Jan 19 '24 16:01 taffit

When creating a new database, existing sites remain! But it is impossible to control them! You need to understand why after the update proxy-manager does not see the database. I hope the developers will fix this. So far I had to roll back from 2.11.0 to 2.10.4

This! This really is the only way to make it running again if you are using SQLite like me. Use the image jc21/nginx-proxy-manager:2.10.4, until the developers get it to work again with a newer version.

I had to remove the "NODE" env but else than that, rolling back to 2.10.4 worked for me too

Spillebulle avatar Jan 19 '24 19:01 Spillebulle

This! This really is the only way to make it running again if you are using SQLite like me. Use the image jc21/nginx-proxy-manager:2.10.4, until the developers get it to work again with a newer version.

Thank you! I had the same problem until I rolled back to 2.10.4

I've created a new fresh container on the latest version, and then restored table by table from my existing SQLite DB, restarting the container for each. It worked until the table "certificate" was restored, then it stopped working and the container log stopped after:

[1/19/2024] [8:02:44 PM] [Global   ] info      Using Sqlite: /data/database.sqlite
[1/19/2024] [8:02:45 PM] [Migrate  ] info      Current database version: none

Then I started another new container and added a hosts by hand, restarted container, and it was working. Requested a certificate (which worked), restarted, and it stopped working with the same logs as above.

baroumas avatar Jan 19 '24 19:01 baroumas

Same here, broke after this update. Rolling back to 2.10.4 fixed the issue for now.

iron-cc avatar Jan 20 '24 00:01 iron-cc

if you copy the old DB over the the new NGINX it will work. Just dont change any settings until its fixed

jhabers avatar Jan 20 '24 16:01 jhabers

if you copy the old DB over the the new NGINX it will work. Just dont change any settings until its fixed

I tried to do this. It didn't work for me! Rolled back.

SX2-NAME avatar Jan 20 '24 17:01 SX2-NAME

I had the same issue with SQLite and made it work again by rolling back to 2.10.4. Thank you.

saiful7 avatar Jan 21 '24 07:01 saiful7

Same issue here. Had to roll back to 2.10.4. Also removed NODE_OPTIONS --openssl-legacy-provider from ENV otherwise backend did not start

angeloschat avatar Jan 21 '24 10:01 angeloschat

I would assume that if the sqlite db file is located in the /data folder move it one up so mv xxx.slq ../

This way I lost all my data. I can login with default [email protected] only.

Interesting enough my sites are still working?! Would it be possible to transfer the data to new user account?

RodBelaFarin avatar Jan 21 '24 14:01 RodBelaFarin

Experiencing the same issue, attempted a bunch of fixes but nothing worked. Also in the reverted back to 2.10.4 camp till a patch is released, it works fine with that so just gonna chill there. Appreciate all you do jc21+contributors

TollhouseC avatar Jan 21 '24 18:01 TollhouseC

I'm getting the same 502 with sqlite. Can be reproduced very easily. Just set up a fresh container, as explained in Quick Start. Afterwards stop and re run the container... and you're getting 502.

technikamateur avatar Jan 21 '24 18:01 technikamateur