starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #3328] first login with 502 bad gateway,what should I do #2240

New issue
Open
opened 2026-02-26 07:34:40 +03:00 by kerem · 16 comments
kerem commented 2026-02-26 07:34:40 +03:00
Owner
Copy link

Originally created by @HaSaKiYasuooo on GitHub (Nov 16, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3328

this is my docker-compose.yml file
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

when I login with admin@example.com and changeme,I revieve the 502 bad gateway,how can i resolve it?

Originally created by @HaSaKiYasuooo on GitHub (Nov 16, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3328 this is my docker-compose.yml file 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 ------------------------------ when I login with admin@example.com and changeme,I revieve the 502 bad gateway,how can i resolve it?
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@pvnkrockjesvs commented on GitHub (Nov 19, 2023):

Same with my install I use for months. Tried a fresh install, same problem as op

<!-- gh-comment-id:1817802826 --> @pvnkrockjesvs commented on GitHub (Nov 19, 2023): Same with my install I use for months. Tried a fresh install, same problem as op
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@HaSaKiYasuooo commented on GitHub (Nov 20, 2023):

ar/run/docker.sock：发布“http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create?name=npm”：拨打unix /var/run/docker.sock：连接：权限否认。
请参阅“docker run --help”。
arch@archlinux ~/nginx2 [126]> sudo docker run -d \ (base)
--name=npm
-p 6080:80
-p 81:81
-p 6443:443
-v /home/npm/data:/data
-v /home/npm/letsencrypt:/etc/letsencrypt
--restart=always
jc21/nginx-proxy-manager:latest
81端口的入口需要用本地127.0.0.1:81才能进入，这个配置在服务器以后还需要做个ssh端口转发才能进入设置...

<!-- gh-comment-id:1818188104 --> @HaSaKiYasuooo commented on GitHub (Nov 20, 2023): ar/run/docker.sock：发布“http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create?name=npm”：拨打unix /var/run/docker.sock：连接：权限否认。 请参阅“docker run --help”。 arch@archlinux ~/nginx2 [126]> sudo docker run -d \ (base) --name=npm -p 6080:80 -p 81:81 -p 6443:443 -v /home/npm/data:/data -v /home/npm/letsencrypt:/etc/letsencrypt --restart=always jc21/nginx-proxy-manager:latest 81端口的入口需要用本地127.0.0.1:81才能进入，这个配置在服务器以后还需要做个ssh端口转发才能进入设置...
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@lastsamurai26 commented on GitHub (Nov 21, 2023):

how you are opening the Side ?
http://ip:81 or https://ip:81 ?

i cant reproduce the issue

<!-- gh-comment-id:1820719668 --> @lastsamurai26 commented on GitHub (Nov 21, 2023): how you are opening the Side ? http://ip:81 or https://ip:81 ? i cant reproduce the issue
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@HaSaKiYasuooo commented on GitHub (Nov 21, 2023):

how you are opening the Side ? http://ip:81 or https://ip:81 ?

i cant reproduce the issue

Use the local address 127.0.0.1:81. If you are booting on a remote vps, then you need to map the remote port 81 to the local machine. Use ssh port forwarding commands

<!-- gh-comment-id:1821063158 --> @HaSaKiYasuooo commented on GitHub (Nov 21, 2023): > how you are opening the Side ? http://ip:81 or https://ip:81 ? > > i cant reproduce the issue Use the local address 127.0.0.1:81. If you are booting on a remote vps, then you need to map the remote port 81 to the local machine. Use ssh port forwarding commands
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@lastsamurai26 commented on GitHub (Nov 22, 2023):

I am using this on a Cloud VPS, my compose looks like this:

version: '3.8'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    hostname: proxymanager
    healthcheck:
      test: ["CMD", "/bin/check-health"]
      interval: 10s
      timeout: 3s
    ports:
      # These ports are in format <host-port>:<container-port>
      - '80:80' # Public HTTP Port
      - '443:443' # Public HTTPS Port
#      - '81:81' # Admin Web Port
      - '8000:8000'
      - '8001:8001'

    # Uncomment the next line if you uncomment anything in the section
    environment:
      # Uncomment this if you want to change the location of
      # the SQLite DB file within the container
      # DB_SQLITE_FILE: "/data/database.sqlite"

      # Uncomment this if IPv6 is not enabled on your host
      DISABLE_IPV6: 'false'
    networks:
        proxy:
          ipv4_address: 172.18.1.253
    volumes:
      - /opt/containers/nginxproxy/data:/data
      - /opt/containers/nginxproxy/letsencrypt:/etc/letsencrypt
      - /opt/containers/nginxproxy/templates/_hsts.conf:/app/templates/_hsts.conf:ro
      - /etc/timezone:/etc/timezone:ro
      - /usr/share/zoneinfo:/usr/share/zoneinfo:ro
networks:
  proxy:
    external: true

after creating a domain for port 81, I deactivate port 81 again so that the NPM dashboard can only be reached via the domain.

maybe the error is somewhere there
http://IPVPS:81

<!-- gh-comment-id:1822673010 --> @lastsamurai26 commented on GitHub (Nov 22, 2023): I am using this on a Cloud VPS, my compose looks like this: ``` version: '3.8' services: app: image: 'jc21/nginx-proxy-manager:latest' restart: unless-stopped hostname: proxymanager healthcheck: test: ["CMD", "/bin/check-health"] interval: 10s timeout: 3s ports: # These ports are in format <host-port>:<container-port> - '80:80' # Public HTTP Port - '443:443' # Public HTTPS Port # - '81:81' # Admin Web Port - '8000:8000' - '8001:8001' # Uncomment the next line if you uncomment anything in the section environment: # Uncomment this if you want to change the location of # the SQLite DB file within the container # DB_SQLITE_FILE: "/data/database.sqlite" # Uncomment this if IPv6 is not enabled on your host DISABLE_IPV6: 'false' networks: proxy: ipv4_address: 172.18.1.253 volumes: - /opt/containers/nginxproxy/data:/data - /opt/containers/nginxproxy/letsencrypt:/etc/letsencrypt - /opt/containers/nginxproxy/templates/_hsts.conf:/app/templates/_hsts.conf:ro - /etc/timezone:/etc/timezone:ro - /usr/share/zoneinfo:/usr/share/zoneinfo:ro networks: proxy: external: true ``` after creating a domain for port 81, I deactivate port 81 again so that the NPM dashboard can only be reached via the domain. maybe the error is somewhere there http://IPVPS:81
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@rsebi commented on GitHub (Nov 27, 2023):

Just performed an upgrade from 2.9.1 to latest image and cant login to admin panel anymore.
Screenshot 2023-11-27 130140

<!-- gh-comment-id:1828605397 --> @rsebi commented on GitHub (Nov 27, 2023): Just performed an upgrade from 2.9.1 to latest image and cant login to admin panel anymore. <img width="549" alt="Screenshot 2023-11-27 130140" src="https://github.com/NginxProxyManager/nginx-proxy-manager/assets/102179977/41c5f42d-31ff-4382-940f-7f77e122495c">
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@rsebi commented on GitHub (Nov 28, 2023):

After bit of research , i found another post with possible fix:
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3237

Managed to apply the fix as outlined and it worked.

<!-- gh-comment-id:1828891752 --> @rsebi commented on GitHub (Nov 28, 2023): After bit of research , i found another post with possible fix: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3237 Managed to apply the fix as outlined and it worked.
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (May 28, 2024):

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

<!-- gh-comment-id:2134222680 --> @github-actions[bot] commented on GitHub (May 28, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@Akmalwy commented on GitHub (Aug 29, 2024):

i have the same problem

and this is the log from my nginx-proxy-manager :

❯ Starting backend ...
node: symbol lookup error: node: undefined symbol: , version GLIBC_2.2.5
❯ Starting backend ...
node: symbol lookup error: node: undefined symbol: , version GLIBC_2.2.5
❯ Starting backend ...
node: symbol lookup error: node: undefined symbol: , version GLIBC_2.2.5
❯ Starting backend ...
node: symbol lookup error: node: undefined symbol: , version GLIBC_2.2.5

<!-- gh-comment-id:2316733056 --> @Akmalwy commented on GitHub (Aug 29, 2024): i have the same problem and this is the log from my nginx-proxy-manager : ❯ Starting backend ... node: symbol lookup error: node: undefined symbol: , version GLIBC_2.2.5 ❯ Starting backend ... node: symbol lookup error: node: undefined symbol: , version GLIBC_2.2.5 ❯ Starting backend ... node: symbol lookup error: node: undefined symbol: , version GLIBC_2.2.5 ❯ Starting backend ... node: symbol lookup error: node: undefined symbol: , version GLIBC_2.2.5
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@zsio commented on GitHub (Sep 2, 2024):

i have the same problem

<!-- gh-comment-id:2324118637 --> @zsio commented on GitHub (Sep 2, 2024): i have the same problem
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@MarkRotNF commented on GitHub (Sep 8, 2024):

I also had the gateway error.

docker ps showed that " nginxproxymanager-db-1" (jc21/mariadb-aria:latest) ist "restarting" (in loop).

docker-compose up (without -d) returned:

app-1  | ❯ Starting backend ...
app-1  | ❯ Starting nginx ...
db-1   | 2024-09-08 10:59:54 0 [Note] Starting MariaDB 10.11.5-MariaDB source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 1
db-1   | Cannot find checkpoint record at LSN (1,0x361f80)
db-1   | 2024-09-08 10:59:54 0 [ERROR] mysqld: Aria recovery failed. Please run aria_chk -r on all Aria tables (*.MAI) and delete all aria_log.######## files
db-1   | 2024-09-08 10:59:54 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
db-1   | 2024-09-08 10:59:54 0 [Note] Plugin 'InnoDB' is disabled.
db-1   | 2024-09-08 10:59:54 0 [Note] Plugin 'FEEDBACK' is disabled.
db-1   | 2024-09-08 10:59:54 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded
db-1   | 2024-09-08 10:59:54 0 [ERROR] Failed to initialize plugins.

I was able to fix it with the following:
cd to the mysql folder (should be the path thats in the docker-compose.yaml "db:" -> "volumes:". E.g. "./mysql" as in my case.
image

docker-compose down
sudo mv aria_log. XXXXXXXXX bak.aria_log.XXXXXXXXX
docker-compose up -d
(similar to described here: https://serverfault.com/questions/893626/mysql-wont-start-mysqld-got-signal-11)

(I'm not sure if this was due to insufficient free storage space. Mine was almost full.)

<!-- gh-comment-id:2336676010 --> @MarkRotNF commented on GitHub (Sep 8, 2024): I also had the gateway error. ``` docker ps``` showed that " nginxproxymanager-db-1" (jc21/mariadb-aria:latest) ist "restarting" (in loop). ``` docker-compose up``` (without -d) returned: ``` app-1 | ❯ Starting backend ... app-1 | ❯ Starting nginx ... db-1 | 2024-09-08 10:59:54 0 [Note] Starting MariaDB 10.11.5-MariaDB source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 1 db-1 | Cannot find checkpoint record at LSN (1,0x361f80) db-1 | 2024-09-08 10:59:54 0 [ERROR] mysqld: Aria recovery failed. Please run aria_chk -r on all Aria tables (*.MAI) and delete all aria_log.######## files db-1 | 2024-09-08 10:59:54 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. db-1 | 2024-09-08 10:59:54 0 [Note] Plugin 'InnoDB' is disabled. db-1 | 2024-09-08 10:59:54 0 [Note] Plugin 'FEEDBACK' is disabled. db-1 | 2024-09-08 10:59:54 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded db-1 | 2024-09-08 10:59:54 0 [ERROR] Failed to initialize plugins. ``` I was able to fix it with the following: cd to the mysql folder (should be the path thats in the docker-compose.yaml "db:" -> "volumes:". E.g. "./mysql" as in my case. ![image](https://github.com/user-attachments/assets/38c24d7f-91fd-4baa-87db-65bd6002340d) ``` docker-compose down``` ``` sudo mv aria_log. XXXXXXXXX bak.aria_log.XXXXXXXXX``` ``` docker-compose up -d``` (similar to described here: [https://serverfault.com/questions/893626/mysql-wont-start-mysqld-got-signal-11](https://serverfault.com/questions/893626/mysql-wont-start-mysqld-got-signal-1)) (I'm not sure if this was due to insufficient free storage space. Mine was almost full.)
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@pureexe commented on GitHub (Dec 23, 2024):

I have the same problem. Turn out it conflicts with the UFW firewall on my machine. So, disable UFW make it working correctly.

<!-- gh-comment-id:2559140196 --> @pureexe commented on GitHub (Dec 23, 2024): I have the same problem. Turn out it conflicts with the UFW firewall on my machine. So, disable UFW make it working correctly.
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@merrime-n commented on GitHub (Apr 28, 2025):

After a couple of minutes, the issue was automatically resolved for me.

<!-- gh-comment-id:2834004445 --> @merrime-n commented on GitHub (Apr 28, 2025): After a couple of minutes, the issue was automatically resolved for me.
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@alectric-tr commented on GitHub (Jun 27, 2025):

Same issue here as well. Same outcome as @okaeiz, the issue resolved itself after a few minutes.

<!-- gh-comment-id:3010888779 --> @alectric-tr commented on GitHub (Jun 27, 2025): Same issue here as well. Same outcome as @okaeiz, the issue resolved itself after a few minutes.
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

@Prathyush-KKK commented on GitHub (Jul 16, 2025):

yup leave the container running, it gets resolved on its own

<!-- gh-comment-id:3080339971 --> @Prathyush-KKK commented on GitHub (Jul 16, 2025): yup leave the container running, it gets resolved on its own
kerem commented 2026-02-26 07:34:41 +03:00
Author
Owner
Copy link

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

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

<!-- gh-comment-id:3782127529 --> @github-actions[bot] commented on GitHub (Jan 22, 2026): Issue is now considered stale. If you want to keep it open, please comment :+1:
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear labels   
awaiting feedback

   
bug

   
cannot reproduce

   
dns provider request

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
need more info

   
no certbot plugin available

   
product-support

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#2240
No description provided.