search

NginxProxyManager / nginx-proxy-manager

Docker container for managing Nginx proxy hosts with a simple, powerful interface
https://nginxproxymanager.com
MIT License
22.03k stars 2.54k forks source link

WTF :login 502 #3965

Open peterwillcn opened 2 weeks ago

peterwillcn commented 2 weeks ago

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

devMikeUA commented 2 weeks ago

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"
ip520011 commented 2 weeks ago

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

image image image image

成功!!!

riruigit commented 2 weeks ago

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

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

riruigit commented 2 weeks ago

找到解决方案了吗？

ip520011 commented 1 week ago

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

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

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

laopaoer-wallet commented 1 week ago

跟node没关系。。。。

icerao commented 3 days ago

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.