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

WTF :login 502

Open peterwillcn opened this issue 1 year ago • 11 comments

WTF : login 502

  ngx:
    image: 'docker.io/jc21/nginx-proxy-manager:latest'
    container_name: nginx
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - /data/nginx:/data
      - /data/nginx/letsencrypt:/etc/letsencrypt

image

peterwillcn avatar Aug 29 '24 13:08 peterwillcn

Same crap:


 Starting backend ...
    node[1006]: std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start() at ../src/node_platform.cc:68
    Assertion failed: (0) == (uv_thread_create(t.get(), start_thread, this))
----- Native stack trace -----
 1: 0xcbc127 node::Assert(node::AssertionInfo const&) [node]
 2: 0xd3b96e node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) [node]
 3: 0xd3ba4c node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
 4: 0xc702d6  [node]
 5: 0xc717d4 node::Start(int, char**) [node]
 6: 0x7f54bfe8324a  [/lib/x86_64-linux-gnu/libc.so.6]
 7: 0x7f54bfe83305 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
 8: 0xbc630e _start [node]
./run: line 21:  1006 Aborted                 (core dumped) s6-setuidgid "$PUID:$PGID" bash -c "export HOME=$NPMHOME;node --abort_on_uncaught_exception --max_old_space_size=250 index.js"

devMikeUA avatar Aug 30 '24 07:08 devMikeUA

找到解决办法了，我发现是因为我的宿主机上装了node 导致的，把 node 卸载掉，就可以了。 重要的事情说三遍！ 宿主机必须删除 node 环境！宿主机必须删除 node 环境！宿主机必须删除 node 环境！注意需要重启宿主机！ image image image image

成功!!!

ip520011 avatar Aug 31 '24 08:08 ip520011

找到解决办法了，我发现是因为我的宿主机上装了node 导致的，把 node 卸载掉，就可以了。 重要的事情说三遍！ 宿主机必须删除 node 环境！宿主机必须删除 node 环境！宿主机必须删除 node 环境！

他这个是基于docker运行的，应该跟你这个没多大关系，我也是docker 复现了。

riruigit avatar Sep 01 '24 08:09 riruigit

找到解决方案了吗？

riruigit avatar Sep 01 '24 08:09 riruigit

找到解决办法了，我发现是因为我的宿主机上装了node 导致的，把 node 卸载掉，就可以了。 重要的事情说三遍！ 宿主机必须删除 node 环境！宿主机必须删除 node 环境！宿主机必须删除 node 环境！

他这个是基于docker运行的，应该跟你这个没多大关系，我也是docker 复现了。

那就不清楚了，我复现了好几次，删除了 node 环境，并且重启服务器，就可以了

ip520011 avatar Sep 02 '24 02:09 ip520011

跟node没关系。。。。

laopaoer-wallet avatar Sep 04 '24 14:09 laopaoer-wallet

I have same issue.start log I found:

[9/12/2024] [4:58:37 AM] [Setup    ] › ℹ  info      Initial admin setup completed
[9/12/2024] [4:58:37 AM] [Setup    ] › ℹ  info      Default settings added
[9/12/2024] [4:58:37 AM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[9/12/2024] [4:58:37 AM] [Global   ] › ⬤  debug     CMD: logrotate /etc/logrotate.d/nginx-proxy-manager
[9/12/2024] [4:58:37 AM] [Setup    ] › ℹ  info      Logrotate completed.
[9/12/2024] [4:58:37 AM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[9/12/2024] [4:58:37 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json

[9/12/2024] [5:04:41 AM] [IP Ranges] › ✖  error     read ECONNRESET
[9/12/2024] [5:04:41 AM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[9/12/2024] [5:04:41 AM] [SSL      ] › ℹ  info      Renewing SSL certs expiring within 30 days ...
[9/12/2024] [5:04:41 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[9/12/2024] [5:04:41 AM] [Global   ] › ℹ  info      Backend PID 159 listening on port 3000 ...
[9/12/2024] [5:04:41 AM] [SSL      ] › ℹ  info      Completed SSL cert renew process

The Fetching https://ip-ranges.amazonaws.com/ip-ranges.json blocked at startup. Some times this will cost many many time.

icerao avatar Sep 12 '24 05:09 icerao

Last night my container stuck at fetching ip-ranges as well, and failed to fetch it for all night. But I restarted it again this morning and it was all fixed. It would be better to add a timeout and retry here.

zanderzhng avatar Sep 19 '24 23:09 zanderzhng

I have same issue.start log I found:

[9/12/2024] [4:58:37 AM] [Setup    ] › ℹ  info      Initial admin setup completed
[9/12/2024] [4:58:37 AM] [Setup    ] › ℹ  info      Default settings added
[9/12/2024] [4:58:37 AM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[9/12/2024] [4:58:37 AM] [Global   ] › ⬤  debug     CMD: logrotate /etc/logrotate.d/nginx-proxy-manager
[9/12/2024] [4:58:37 AM] [Setup    ] › ℹ  info      Logrotate completed.
[9/12/2024] [4:58:37 AM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[9/12/2024] [4:58:37 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json

[9/12/2024] [5:04:41 AM] [IP Ranges] › ✖  error     read ECONNRESET
[9/12/2024] [5:04:41 AM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[9/12/2024] [5:04:41 AM] [SSL      ] › ℹ  info      Renewing SSL certs expiring within 30 days ...
[9/12/2024] [5:04:41 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[9/12/2024] [5:04:41 AM] [Global   ] › ℹ  info      Backend PID 159 listening on port 3000 ...
[9/12/2024] [5:04:41 AM] [SSL      ] › ℹ  info      Completed SSL cert renew process

The Fetching https://ip-ranges.amazonaws.com/ip-ranges.json blocked at startup. Some times this will cost many many time.

I'm blocked by this fetching too, just run:

NPM_CTR_NAME=nginxproxymanager
docker exec $NPM_CTR_NAME sed -i 's/\.then(internalIpRanges\.fetch)//g' /app/index.js
docker restart $NPM_CTR_NAME

This should skip the fetching of the startup.

jqknono avatar Sep 26 '24 11:09 jqknono

找到解决办法了，我发现是因为我的宿主机上装了node 导致的，把 node 卸载掉，就可以了。 重要的事情说三遍！ 宿主机必须删除 node 环境！宿主机必须删除 node 环境！注意需要重启宿主机！ 图像 图像 图像 图像

成功!!!

感谢我也是卸载node后重启就好了 微信截图_20241015224924

image

JokerAlger avatar Oct 15 '24 14:10 JokerAlger

这么神奇，我是直接docker部署的。宿主机没有node啊

riruigit avatar Oct 15 '24 14:10 riruigit

找到解决办法了，我发现是因为我的宿主机上装了node 导致的，把 node 卸载掉，就可以了。 重要的事情说三遍！ 宿主机必须删除 node 环境！宿主机必须删除 node 环境！宿主机必须删除 node 环境！注意需要重启宿主机！ image image image image

成功!!!

这不是最终解决办法啊，那项目非得用node呢。我怀疑是某个指令是npm 与node的npm冲突了。

Tenodec avatar Nov 16 '24 07:11 Tenodec

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

github-actions[bot] avatar May 18 '25 02:05 github-actions[bot]