nginx-proxy-manager: 502 bad gateway afer upgrade to 2.11.1

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 After upgrading to latest (2.11.1) I get the error “bad gatway” when trying to login. all hosts work tho.

I found the issue for some people was 2.11.0 when they had no DNS Challenge certs, but in my case I have those, and I use 2.11.1

Nginx Proxy Manager Version 2.11.1

OS / Docker Debian 10

docker version Client: Version: 18.09.1 API version: 1.39 Go version: go1.11.6 Git commit: 4c52b90 Built: Sun, 21 Feb 2021 18:18:35 +0100 OS/Arch: linux/amd64 Experimental: false

Server: Engine: Version: 18.09.1 API version: 1.39 (minimum version 1.12) Go version: go1.11.6 Git commit: 4c52b90 Built: Sun Feb 21 17:18:35 2021 OS/Arch: linux/amd64 Experimental: false

To Reproduce docker-compose up

the startup looks fine at the beginning

Attaching to nginxproxymanager_nginx-proxy-manager_1
nginx-proxy-manager_1  | ❯ Configuring npm user ...
nginx-proxy-manager_1  | useradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range.
nginx-proxy-manager_1  | ❯ Configuring npm group ...
nginx-proxy-manager_1  | ❯ Checking paths ...
nginx-proxy-manager_1  | ❯ Setting ownership ...
nginx-proxy-manager_1  | ❯ Dynamic resolvers ...
nginx-proxy-manager_1  | ❯ IPv6 ...
nginx-proxy-manager_1  | Enabling IPV6 in hosts in: /etc/nginx/conf.d
nginx-proxy-manager_1  | - /etc/nginx/conf.d/default.conf
nginx-proxy-manager_1  | - /etc/nginx/conf.d/include/ssl-ciphers.conf
nginx-proxy-manager_1  | - /etc/nginx/conf.d/include/assets.conf
nginx-proxy-manager_1  | - /etc/nginx/conf.d/include/ip_ranges.conf
nginx-proxy-manager_1  | - /etc/nginx/conf.d/include/force-ssl.conf
nginx-proxy-manager_1  | - /etc/nginx/conf.d/include/proxy.conf
nginx-proxy-manager_1  | - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
nginx-proxy-manager_1  | - /etc/nginx/conf.d/include/block-exploits.conf
nginx-proxy-manager_1  | - /etc/nginx/conf.d/include/resolvers.conf
nginx-proxy-manager_1  | - /etc/nginx/conf.d/production.conf
nginx-proxy-manager_1  | Enabling IPV6 in hosts in: /data/nginx
nginx-proxy-manager_1  | - /data/nginx/proxy_host/2.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/7.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/25.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/23.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/8.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/15.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/22.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/1.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/26.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/24.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/21.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/19.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/9.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/16.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/17.conf
nginx-proxy-manager_1  | - /data/nginx/proxy_host/12.conf
nginx-proxy-manager_1  | - /data/nginx/default_host/site.conf
nginx-proxy-manager_1  | ❯ Docker secrets ...
nginx-proxy-manager_1  | 
nginx-proxy-manager_1  | -------------------------------------
nginx-proxy-manager_1  |  _   _ ____  __  __
nginx-proxy-manager_1  | | \ | |  _ \|  \/  |
nginx-proxy-manager_1  | |  \| | |_) | |\/| |
nginx-proxy-manager_1  | | |\  |  __/| |  | |
nginx-proxy-manager_1  | |_| \_|_|   |_|  |_|
nginx-proxy-manager_1  | -------------------------------------
nginx-proxy-manager_1  | User:  npm PUID:0 ID:0 GROUP:0
nginx-proxy-manager_1  | Group: npm PGID:0 ID:0
nginx-proxy-manager_1  | -------------------------------------
nginx-proxy-manager_1  | 
nginx-proxy-manager_1  | ❯ Starting nginx ...
nginx-proxy-manager_1  | ❯ Starting backend ...

but then it loops with

nginx-proxy-manager_1  | 
nginx-proxy-manager_1  |   #  node[178]: std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start() at ../src/node_platform.cc:68
nginx-proxy-manager_1  |   #  Assertion failed: (0) == (uv_thread_create(t.get(), start_thread, this))
nginx-proxy-manager_1  | 
nginx-proxy-manager_1  | ----- Native stack trace -----
nginx-proxy-manager_1  | 
nginx-proxy-manager_1  |  1: 0xca5430 node::Abort() [node]
nginx-proxy-manager_1  |  2: 0xca54b0 node::errors::SetPrepareStackTraceCallback(v8::FunctionCallbackInfo<v8::Value> const&) [node]
nginx-proxy-manager_1  |  3: 0xd24789 node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) [node]
nginx-proxy-manager_1  |  4: 0xd248ac node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
nginx-proxy-manager_1  |  5: 0xc5e5a3  [node]
nginx-proxy-manager_1  |  6: 0xc5ef34 node::Start(int, char**) [node]
nginx-proxy-manager_1  |  7: 0x7f50877391ca  [/lib/x86_64-linux-gnu/libc.so.6]
nginx-proxy-manager_1  |  8: 0x7f5087739285 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
nginx-proxy-manager_1  |  9: 0xbb8d7e _start [node]
nginx-proxy-manager_1  | ./run: line 21:   178 Aborted                 (core dumped) s6-setuidgid "$PUID:$PGID" bash -c "export HOME=$NPMHOME;node --abort_on_uncaught_exception --max_old_space_size=250 index.js"
nginx-proxy-manager_1  | ❯ Starting backend ...

rolling back to 2.10.4 everything works fine

my docker compose file:

version: "3"
services:
  nginx-proxy-manager:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '443:443'
      - '81:81'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt