NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Initial login leads to "Bad Gateway"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Describe the bug
Initial login shows "Bad gateway" error
Nginx Proxy Manager Version
2.11.1
To Reproduce
Steps to reproduce the behavior:
- launch latest Docker container -> works
- goto myIP:81/login
- use the initial creds
- Error on page: Bad gateway
Expected behavior
Log into manager
Operating System
Debian 9.13 on Host
Here is the error log:
14/03/2024
13:57:27
❯ Configuring npm user ...
14/03/2024
13:57:27
useradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range.
14/03/2024
13:57:27
❯ Configuring npm group ...
14/03/2024
13:57:27
❯ Checking paths ...
14/03/2024
13:57:27
❯ Setting ownership ...
14/03/2024
13:57:36
❯ Dynamic resolvers ...
14/03/2024
13:57:36
❯ IPv6 ...
14/03/2024
13:57:36
Enabling IPV6 in hosts in: /etc/nginx/conf.d
14/03/2024
13:57:36
- /etc/nginx/conf.d/default.conf
14/03/2024
13:57:36
- /etc/nginx/conf.d/include/block-exploits.conf
14/03/2024
13:57:36
- /etc/nginx/conf.d/include/ssl-ciphers.conf
14/03/2024
13:57:36
- /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
14/03/2024
13:57:36
- /etc/nginx/conf.d/include/proxy.conf
14/03/2024
13:57:36
- /etc/nginx/conf.d/include/ip_ranges.conf
14/03/2024
13:57:36
- /etc/nginx/conf.d/include/force-ssl.conf
14/03/2024
13:57:36
- /etc/nginx/conf.d/include/assets.conf
14/03/2024
13:57:36
- /etc/nginx/conf.d/include/resolvers.conf
14/03/2024
13:57:36
- /etc/nginx/conf.d/production.conf
14/03/2024
13:57:36
Enabling IPV6 in hosts in: /data/nginx
14/03/2024
13:57:36
❯ Docker secrets ...
14/03/2024
13:57:36
14/03/2024
13:57:36
-------------------------------------
14/03/2024
13:57:36
_ _ ____ __ __
14/03/2024
13:57:36
| \ | | _ \| \/ |
14/03/2024
13:57:36
| \| | |_) | |\/| |
14/03/2024
13:57:36
| |\ | __/| | | |
14/03/2024
13:57:36
|_| \_|_| |_| |_|
14/03/2024
13:57:36
-------------------------------------
14/03/2024
13:57:36
User: npm PUID:0 ID:0 GROUP:0
14/03/2024
13:57:36
Group: npm PGID:0 ID:0
14/03/2024
13:57:36
-------------------------------------
14/03/2024
13:57:36
14/03/2024
13:57:36
❯ Starting nginx ...
14/03/2024
13:57:36
❯ Starting backend ...
14/03/2024
13:57:36
14/03/2024
13:57:36
# node[161]: std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start() at ../src/node_platform.cc:68
14/03/2024
13:57:36
# Assertion failed: (0) == (uv_thread_create(t.get(), start_thread, this))
14/03/2024
13:57:36
14/03/2024
13:57:36
----- Native stack trace -----
14/03/2024
13:57:36
14/03/2024
13:57:36
1: 0xca5580 node::Abort() [node]
14/03/2024
13:57:36
2: 0xca5600 node::errors::SetPrepareStackTraceCallback(v8::FunctionCallbackInfo<v8::Value> const&) [node]
14/03/2024
13:57:36
3: 0xd24949 node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) [node]
14/03/2024
13:57:36
4: 0xd24a6c node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
14/03/2024
13:57:36
5: 0xc5e5d3 [node]
14/03/2024
13:57:36
6: 0xc5ef64 node::Start(int, char**) [node]
14/03/2024
13:57:36
7: 0x7fee5d05224a [/lib/x86_64-linux-gnu/libc.so.6]
14/03/2024
13:57:36
8: 0x7fee5d052305 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
14/03/2024
13:57:36
9: 0xbb8eee _start [node]
14/03/2024
13:57:36
./run: line 21: 161 Aborted (core dumped) s6-setuidgid "$PUID:$PGID" bash -c "export HOME=$NPMHOME;node --abort_on_uncaught_exception --max_old_space_size=250 index.js"
14/03/2024
13:57:37
❯ Starting backend ...
14/03/2024
13:57:37
14/03/2024
13:57:37
# node[182]: std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start() at ../src/node_platform.cc:68
14/03/2024
13:57:37
# Assertion failed: (0) == (uv_thread_create(t.get(), start_thread, this))
14/03/2024
13:57:37
14/03/2024
13:57:37
----- Native stack trace -----
14/03/2024
13:57:37
14/03/2024
13:57:37
1: 0xca5580 node::Abort() [node]
14/03/2024
13:57:37
2: 0xca5600 node::errors::SetPrepareStackTraceCallback(v8::FunctionCallbackInfo<v8::Value> const&) [node]
14/03/2024
13:57:37
3: 0xd24949 node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) [node]
14/03/2024
13:57:37
4: 0xd24a6c node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
14/03/2024
13:57:37
5: 0xc5e5d3 [node]
14/03/2024
13:57:37
7: 0x7f8eab65a24a [/lib/x86_64-linux-gnu/libc.so.6]
14/03/2024
13:57:37
8: 0x7f8eab65a305 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
14/03/2024
13:57:37
9: 0xbb8eee _start [node]
14/03/2024
13:57:37
./run: line 21: 182 Aborted (core dumped) s6-setuidgid "$PUID:$PGID" bash -c "export HOME=$NPMHOME;node --abort_on_uncaught_exception --max_old_space_size=250 index.js"
14/03/2024
13:57:38
❯ Starting backend ...
14/03/2024
13:57:38
14/03/2024
13:57:38
# node[186]: std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start() at ../src/node_platform.cc:68
14/03/2024
13:57:38
# Assertion failed: (0) == (uv_thread_create(t.get(), start_thread, this))
14/03/2024
13:57:38
14/03/2024
13:57:38
----- Native stack trace -----
14/03/2024
13:57:38
14/03/2024
13:57:38
1: 0xca5580 node::Abort() [node]
14/03/2024
13:57:38
2: 0xca5600 node::errors::SetPrepareStackTraceCallback(v8::FunctionCallbackInfo<v8::Value> const&) [node]
14/03/2024
13:57:38
3: 0xd24949 node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) [node]
14/03/2024
13:57:38
4: 0xd24a6c node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
14/03/2024
13:57:38
5: 0xc5e5d3 [node]
14/03/2024
13:57:38
6: 0xc5ef64 node::Start(int, char**) [node]
14/03/2024
13:57:38
7: 0x7fbf8030724a [/lib/x86_64-linux-gnu/libc.so.6]
14/03/2024
13:57:38
8: 0x7fbf80307305 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
14/03/2024
13:57:38
9: 0xbb8eee _start [node]
14/03/2024
13:57:39
./run: line 21: 186 Aborted (core dumped) s6-setuidgid "$PUID:$PGID" bash -c "export HOME=$NPMHOME;node --abort_on_uncaught_exception --max_old_space_size=250 index.js"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Docker container startup sequence and the backend entry point shown in the log, index.js. Reproduce the initial login on Debian 9 and inspect the repeated Node uv_thread_create assertion and nginx gateway response. Done means the backend remains running and the initial credentials successfully log into the manager.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, docker, nginx, nodejs
- Domain
- backend, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100