nginx-proxy-manager: Bad Gateway on Frontend after Upgrade to 2.9.21

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 Since Watchtower took an upgrade to the latest version, the restart of the container works, however I am unable to login to the front end and the logs show issues.

Nginx Proxy Manager Version 2.9.21

Logs 2023-03-18T07:30:44.462695207Z s6-rc: info: service s6rc-oneshot-runner: starting 2023-03-18T07:30:44.465995072Z s6-rc: info: service s6rc-oneshot-runner successfully started 2023-03-18T07:30:44.466098352Z s6-rc: info: service fix-attrs: starting 2023-03-18T07:30:44.470635343Z s6-rc: info: service fix-attrs successfully started 2023-03-18T07:30:44.470747743Z s6-rc: info: service legacy-cont-init: starting 2023-03-18T07:30:44.475032623Z cont-init: info: running /etc/cont-init.d/01_perms.sh 2023-03-18T07:30:44.475160074Z /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: 20: /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: /etc/cont-init.d/01_perms.sh: not found 2023-03-18T07:30:44.475223404Z cont-init: info: /etc/cont-init.d/01_perms.sh exited 127 2023-03-18T07:30:44.475261704Z cont-init: info: running /etc/cont-init.d/01_s6-secret-init.sh 2023-03-18T07:30:44.475348905Z /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: 20: /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: /etc/cont-init.d/01_s6-secret-init.sh: Permission denied 2023-03-18T07:30:44.475406135Z cont-init: info: /etc/cont-init.d/01_s6-secret-init.sh exited 126 2023-03-18T07:30:44.476746421Z cont-init: warning: some scripts exited nonzero 2023-03-18T07:30:44.477097442Z s6-rc: info: service legacy-cont-init successfully started 2023-03-18T07:30:44.477199123Z s6-rc: info: service prepare: starting 2023-03-18T07:30:44.482177186Z ❯ Checking folder structure … 2023-03-18T07:30:44.492934735Z ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d 2023-03-18T07:30:44.493071006Z ❯ /etc/nginx/conf.d/include/assets.conf 2023-03-18T07:30:44.494690023Z ❯ /etc/nginx/conf.d/include/block-exploits.conf 2023-03-18T07:30:44.496363781Z ❯ /etc/nginx/conf.d/include/force-ssl.conf 2023-03-18T07:30:44.498005978Z ❯ /etc/nginx/conf.d/include/ip_ranges.conf 2023-03-18T07:30:44.499598465Z ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf 2023-03-18T07:30:44.501253803Z ❯ /etc/nginx/conf.d/include/proxy.conf 2023-03-18T07:30:44.502925121Z ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf 2023-03-18T07:30:44.504510958Z ❯ /etc/nginx/conf.d/include/resolvers.conf 2023-03-18T07:30:44.506164905Z ❯ /etc/nginx/conf.d/default.conf 2023-03-18T07:30:44.507717663Z ❯ /etc/nginx/conf.d/production.conf 2023-03-18T07:30:44.514301083Z ❯ Enabling IPV6 in hosts: /data/nginx 2023-03-18T07:30:44.514413493Z ❯ /data/nginx/default_host/site.conf 2023-03-18T07:30:44.516041551Z ❯ /data/nginx/proxy_host/1.conf 2023-03-18T07:30:44.517753429Z ❯ /data/nginx/proxy_host/2.conf 2023-03-18T07:30:44.519437616Z ❯ /data/nginx/proxy_host/3.conf 2023-03-18T07:30:44.521189684Z ❯ /data/nginx/proxy_host/4.conf 2023-03-18T07:30:44.522984612Z ❯ /data/nginx/proxy_host/5.conf 2023-03-18T07:30:44.524717690Z ❯ /data/nginx/proxy_host/6.conf 2023-03-18T07:30:44.526496498Z ❯ /data/nginx/proxy_host/7.conf 2023-03-18T07:30:44.528184116Z ❯ /data/nginx/proxy_host/8.conf 2023-03-18T07:30:44.529967204Z ❯ /data/nginx/proxy_host/9.conf 2023-03-18T07:30:44.531864333Z 2023-03-18T07:30:44.531936283Z ------------------------------------- 2023-03-18T07:30:44.531962583Z _ _ ____ __ __ 2023-03-18T07:30:44.531994284Z | \ | | _ | / | 2023-03-18T07:30:44.532017744Z | | | |) | |/| | 2023-03-18T07:30:44.532039104Z | |\ | __/| | | | 2023-03-18T07:30:44.532059204Z || _|| || |_| 2023-03-18T07:30:44.532080334Z ------------------------------------- 2023-03-18T07:30:44.532113064Z 2023-03-18T07:30:44.532281925Z s6-rc: info: service prepare successfully started 2023-03-18T07:30:44.532390335Z s6-rc: info: service nginx: starting 2023-03-18T07:30:44.532472086Z s6-rc: info: service frontend: starting 2023-03-18T07:30:44.532672087Z s6-rc: info: service backend: starting 2023-03-18T07:30:44.536224543Z s6-rc: info: service frontend successfully started 2023-03-18T07:30:44.536397654Z s6-rc: info: service nginx successfully started 2023-03-18T07:30:44.536433794Z s6-rc: info: service backend successfully started 2023-03-18T07:30:44.536643575Z s6-rc: info: service legacy-services: starting 2023-03-18T07:30:44.539354547Z ❯ Starting nginx … 2023-03-18T07:30:44.539493008Z ❯ Starting backend … 2023-03-18T07:30:44.543829498Z s6-rc: info: service legacy-services successfully started 2023-03-18T07:30:45.554489212Z [3/18/2023] [7:30:45 AM] [Global ] › ✖ error getaddrinfo ENOTFOUND db 2023-03-18T07:30:46.560462785Z [3/18/2023] [7:30:46 AM] [Global ] › ✖ error getaddrinfo ENOTFOUND db 2023-03-18T07:30:47.565025631Z [3/18/2023] [7:30:47 AM] [Global ] › ✖ error getaddrinfo ENOTFOUND db 2023-03-18T07:30:48.570174530Z [3/18/2023] [7:30:48 AM] [Global ] › ✖ error getaddrinfo ENOTFOUND db 2023-03-18T07:30:49.575289338Z [3/18/2023] [7:30:49 AM] [Global ] › ✖ error getaddrinfo ENOTFOUND db 2023-03-18T07:30:50.579833474Z [3/18/2023] [7:30:50 AM] [Global ] › ✖ error getaddrinfo ENOTFOUND db 2023-03-18T07:30:51.583636767Z [3/18/2023] [7:30:51 AM] [Global ] › ✖ error getaddrinfo ENOTFOUND db 2023-03-18T07:30:52.588066903Z [3/18/2023] [7:30:52 AM] [Global ] › ✖ error getaddrinfo ENOTFOUND db 2023-03-18T07:30:53.593748814Z [3/18/2023] [7:30:53 AM] [Global ] › ✖ error getaddrinfo ENOTFOUND db

Operating System Synology DS1821+ with Docker Containers.

Docker Compose via Portainer version: ‘3’ services: app: image: ‘jc21/nginx-proxy-manager:latest’ ports: - ‘8765:80’ - ‘81:81’ - ‘8907:443’ environment: DB_MYSQL_HOST: “db” DB_MYSQL_PORT: 3306 DB_MYSQL_USER: “npm” DB_MYSQL_PASSWORD: “npm” DB_MYSQL_NAME: “npm” network_mode: synobridge volumes: - /volume1/docker/nginx_proxy_manager/data/:/data - /volume1/docker/nginx_proxy_manager/letsencrypt:/etc/letsencrypt restart: unless-stopped db: image: ‘jc21/mariadb-aria:latest’ environment: MYSQL_ROOT_PASSWORD: ‘npm’ MYSQL_DATABASE: ‘npm’ MYSQL_USER: ‘npm’ MYSQL_PASSWORD: ‘npm’ network_mode: synobridge volumes: - /volume1/docker/nginx_proxy_manager/mysql:/var/lib/mysql restart: unless-stopped

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 2
  • Comments: 22 (5 by maintainers)

Most upvoted comments

But this is not a solution to reconfigure everything. Unfortunately, this is not an alternative for active 50-100 subdomains. I remain before only with 2.9.19.

+4
topa-LE on Mar 18, 2023

I have the same error:

s6-svscan: warning: unable to iopause: Operation not permitted
s6-svscan: warning: executing into .s6-svscan/crash
s6-svscan crashed. Killing everything and exiting.
s6-linux-init-hpr: fatal: unable to reboot(): Operation not permitted

Both on 2.9.21 and 2.9.22, running on pi3b+ arm

Stay with 2.9.19 for now until the developer fixes the bug

+1
topa-LE on Mar 29, 2023

@labodj the JsonWebTokenError isn’t an issue and can be safely ignored but specifically here’s why it happens:

  • You bring up NPM, it creates new keys and saves them to the config file
  • You login, and are given a JWT that is encrypted with those keys
  • When you restart NPM, since the config file is not mounted and not persistent, it generates new keys again
  • The UI tries to use the JWT from localstorage against the API and it fails with this error
  • Then you’re redirected to login again and you’ll received a new JWT that works
+1
jc21 on Mar 20, 2023

sometimes a docker-compose down and docker-compose up -d can fix a few things in the background.

+1
jc21 on Mar 18, 2023
Read more comments on GitHub
← nginx-proxy-manager: Bad Gateway at Admin Page: production.json cannot be read
nginx-proxy-manager: basically the application is broken. →