[GH-ISSUE #3965] WTF :login 502 #2593

Closed
opened 2026-02-26 07:36:07 +03:00 by kerem · 13 comments
Owner

Originally created by @peterwillcn on GitHub (Aug 29, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3965

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

Originally created by @peterwillcn on GitHub (Aug 29, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3965 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](https://github.com/user-attachments/assets/1865f6e2-0265-4e3d-a9e8-4aa1a1043c8e)
kerem 2026-02-26 07:36:07 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@devMikeUA commented on GitHub (Aug 30, 2024):

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"

<!-- gh-comment-id:2320360689 --> @devMikeUA commented on GitHub (Aug 30, 2024): Same crap: ```shell 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" ```
Author
Owner

@ip520011 commented on GitHub (Aug 31, 2024):

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

成功!!!

<!-- gh-comment-id:2322832511 --> @ip520011 commented on GitHub (Aug 31, 2024): 找到解决办法了,我发现是因为我的宿主机上装了node 导致的,把 node 卸载掉,就可以了。 重要的事情说三遍! 宿主机必须删除 node 环境!宿主机必须删除 node 环境!宿主机必须删除 node 环境!注意需要重启宿主机! <img width="807" alt="image" src="https://github.com/user-attachments/assets/42f5cbae-94db-42e4-bdff-1df6f2cc4a92"> <img width="699" alt="image" src="https://github.com/user-attachments/assets/cbce6717-f3f7-4e7e-a59c-8ffb0f74df63"> <img width="490" alt="image" src="https://github.com/user-attachments/assets/77c38b9d-2566-4bb8-917c-f6d80e5e1303"> <img width="944" alt="image" src="https://github.com/user-attachments/assets/1a29c552-60b9-48a9-843f-3ff6fa8c7596"> 成功!!!
Author
Owner

@riruigit commented on GitHub (Sep 1, 2024):

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

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

<!-- gh-comment-id:2323233437 --> @riruigit commented on GitHub (Sep 1, 2024): > 找到解决办法了,我发现是因为我的宿主机上装了node 导致的,把 node 卸载掉,就可以了。 重要的事情说三遍! 宿主机必须删除 node 环境!宿主机必须删除 node 环境!宿主机必须删除 node 环境! 他这个是基于docker运行的,应该跟你这个没多大关系,我也是docker 复现了。
Author
Owner

@riruigit commented on GitHub (Sep 1, 2024):

找到解决方案了吗?

<!-- gh-comment-id:2323233569 --> @riruigit commented on GitHub (Sep 1, 2024): 找到解决方案了吗?
Author
Owner

@ip520011 commented on GitHub (Sep 2, 2024):

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

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

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

<!-- gh-comment-id:2323639210 --> @ip520011 commented on GitHub (Sep 2, 2024): > > 找到解决办法了,我发现是因为我的宿主机上装了node 导致的,把 node 卸载掉,就可以了。 重要的事情说三遍! 宿主机必须删除 node 环境!宿主机必须删除 node 环境!宿主机必须删除 node 环境! > > 他这个是基于docker运行的,应该跟你这个没多大关系,我也是docker 复现了。 那就不清楚了,我复现了好几次,删除了 node 环境,并且重启服务器,就可以了
Author
Owner

@laopaoer-wallet commented on GitHub (Sep 4, 2024):

跟node没关系。。。。

<!-- gh-comment-id:2329206197 --> @laopaoer-wallet commented on GitHub (Sep 4, 2024): 跟node没关系。。。。
Author
Owner

@icerao commented on GitHub (Sep 12, 2024):

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.

<!-- gh-comment-id:2345297405 --> @icerao commented on GitHub (Sep 12, 2024): I have same issue.start log I found: ```[9/12/2024] [4:58:36 AM] [Setup ] › ℹ info Creating a new user: admin@example.com with password: changeme [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.
Author
Owner

@zanderzhng commented on GitHub (Sep 19, 2024):

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.

<!-- gh-comment-id:2362392559 --> @zanderzhng commented on GitHub (Sep 19, 2024): 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.
Author
Owner

@jqknono commented on GitHub (Sep 26, 2024):

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.

<!-- gh-comment-id:2376700329 --> @jqknono commented on GitHub (Sep 26, 2024): > 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: ```bash 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.
Author
Owner

@JokerAlger commented on GitHub (Oct 15, 2024):

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

成功!!!

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

image

<!-- gh-comment-id:2414167258 --> @JokerAlger commented on GitHub (Oct 15, 2024): > 找到解决办法了,我发现是因为我的宿主机上装了node 导致的,把 node 卸载掉,就可以了。 重要的事情说三遍! 宿主机必须删除 node 环境!宿主机必须删除 node 环境!注意需要重启宿主机! <img alt="图像" width="807" src="https://private-user-images.githubusercontent.com/40999593/363545010-42f5cbae-94db-42e4-bdff-1df6f2cc4a92.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjkwMDM5NDgsIm5iZiI6MTcyOTAwMzY0OCwicGF0aCI6Ii80MDk5OTU5My8zNjM1NDUwMTAtNDJmNWNiYWUtOTRkYi00MmU0LWJkZmYtMWRmNmYyY2M0YTkyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDE1VDE0NDcyOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTczMmZiNDNhZWQzOGI0OTkzMDg2ZjYwZWY3YzU3ZjA2MmJjZjU4MTFmZGY5Y2FiYWRkMDEyODQ5MjVhOTVjNmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.FfSir1INcfQBfwKvcbQrFFyW0x0iP1-PQNeUI5pyDew"> <img alt="图像" width="699" src="https://private-user-images.githubusercontent.com/40999593/363545905-cbce6717-f3f7-4e7e-a59c-8ffb0f74df63.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjkwMDM5NDgsIm5iZiI6MTcyOTAwMzY0OCwicGF0aCI6Ii80MDk5OTU5My8zNjM1NDU5MDUtY2JjZTY3MTctZjNmNy00ZTdlLWE1OWMtOGZmYjBmNzRkZjYzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDE1VDE0NDcyOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRiNGZkZmU5Yjc0N2NmMjMxYmJjZjEyYzRhZDJkN2I4NmViZGMyMjdhOWMzZGFhMGZjNzIzNDY1Mzg0MmE5ODkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.1kr87525TbpXBX1INQwpuU3QVVbOcb8qdaljRrAoNOc"> <img alt="图像" width="490" src="https://private-user-images.githubusercontent.com/40999593/363546129-77c38b9d-2566-4bb8-917c-f6d80e5e1303.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjkwMDM5NDgsIm5iZiI6MTcyOTAwMzY0OCwicGF0aCI6Ii80MDk5OTU5My8zNjM1NDYxMjktNzdjMzhiOWQtMjU2Ni00YmI4LTkxN2MtZjZkODBlNWUxMzAzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDE1VDE0NDcyOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTlmMGFiMWNiYTQ0ZTE0NTY4ZDEzNTUxODJlM2U3NDI4MmRkM2ZhODg5NjhlMjc4ODNjMjNlNDkzNzlhNTQ4NjAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.HudwLjwjHUgBvoBY9nhEByziTcaUJumtuw-Ma98GtK8"> <img alt="图像" width="944" src="https://private-user-images.githubusercontent.com/40999593/363547255-1a29c552-60b9-48a9-843f-3ff6fa8c7596.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjkwMDM5NDgsIm5iZiI6MTcyOTAwMzY0OCwicGF0aCI6Ii80MDk5OTU5My8zNjM1NDcyNTUtMWEyOWM1NTItNjBiOS00OGE5LTg0M2YtM2ZmNmZhOGM3NTk2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDE1VDE0NDcyOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWVlNTJiMWE1ZWQwZTJhYzE2MWEzMWI1NWQ2ZmNhYzY1YTYwMjkzZTM5OGJkNWI0NmJlODU4NDhjODk0ZjYwN2MmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.KYbFLhY3zXszS0y9GIPv0KghNKxZe4vrBBF7Jqbt78w"> > > 成功!!! 感谢我也是卸载node后重启就好了 ![微信截图_20241015224924](https://github.com/user-attachments/assets/1dd66316-936b-4c0f-ba7b-112ea0ddfd21) ![image](https://github.com/user-attachments/assets/0acd443d-b08b-4a31-abc4-b369efd56345)
Author
Owner

@riruigit commented on GitHub (Oct 15, 2024):

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

<!-- gh-comment-id:2414183175 --> @riruigit commented on GitHub (Oct 15, 2024): 这么神奇,我是直接docker部署的。宿主机没有node啊
Author
Owner

@Tenodec commented on GitHub (Nov 16, 2024):

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

成功!!!

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

<!-- gh-comment-id:2480466032 --> @Tenodec commented on GitHub (Nov 16, 2024): > 找到解决办法了,我发现是因为我的宿主机上装了node 导致的,把 node 卸载掉,就可以了。 重要的事情说三遍! 宿主机必须删除 node 环境!宿主机必须删除 node 环境!宿主机必须删除 node 环境!注意需要重启宿主机! <img alt="image" width="807" src="https://private-user-images.githubusercontent.com/40999593/363545010-42f5cbae-94db-42e4-bdff-1df6f2cc4a92.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzE3NDI5OTQsIm5iZiI6MTczMTc0MjY5NCwicGF0aCI6Ii80MDk5OTU5My8zNjM1NDUwMTAtNDJmNWNiYWUtOTRkYi00MmU0LWJkZmYtMWRmNmYyY2M0YTkyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDExMTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMTE2VDA3MzgxNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc2MzQ1NWE5NDlkYjZmNTk5MGQyODQ0Y2MzZGFmYTcyOWIxNThhNDZhMTcyNGNmZjA2NmNiMGM2OWQ1NjMwODEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.5NboJpCm8APgiJA__tAuCM9Kk7QcllzrV_31yNn6rvI"> <img alt="image" width="699" src="https://private-user-images.githubusercontent.com/40999593/363545905-cbce6717-f3f7-4e7e-a59c-8ffb0f74df63.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzE3NDI5OTQsIm5iZiI6MTczMTc0MjY5NCwicGF0aCI6Ii80MDk5OTU5My8zNjM1NDU5MDUtY2JjZTY3MTctZjNmNy00ZTdlLWE1OWMtOGZmYjBmNzRkZjYzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDExMTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMTE2VDA3MzgxNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTcxMmNlNTVlODhjYzZlY2E3MzFkMGMwN2E2YWUxNjg4NDcyN2MwNjJiYWUzZTQ1NWY1NjNjMTU4NWNjYTY0YjYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.0aGm-1AudbksKCXX83_O05IR2jspIYgzLRl2VZPF1L4"> <img alt="image" width="490" src="https://private-user-images.githubusercontent.com/40999593/363546129-77c38b9d-2566-4bb8-917c-f6d80e5e1303.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzE3NDI5OTQsIm5iZiI6MTczMTc0MjY5NCwicGF0aCI6Ii80MDk5OTU5My8zNjM1NDYxMjktNzdjMzhiOWQtMjU2Ni00YmI4LTkxN2MtZjZkODBlNWUxMzAzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDExMTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMTE2VDA3MzgxNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNhMjU0N2IxMzIxM2Q2NmNhNDRhZjQ2Mzg4NjEyMTVlMDkxZTJjMGI4ZWM5ZGMyNjc2M2E2NTBlNmRlMTJjZWQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.sXiKCk-HkM6H_6YSCMM3bLB7K6dF5VOvQxZ1BCoOIpU"> <img alt="image" width="944" src="https://private-user-images.githubusercontent.com/40999593/363547255-1a29c552-60b9-48a9-843f-3ff6fa8c7596.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzE3NDI5OTQsIm5iZiI6MTczMTc0MjY5NCwicGF0aCI6Ii80MDk5OTU5My8zNjM1NDcyNTUtMWEyOWM1NTItNjBiOS00OGE5LTg0M2YtM2ZmNmZhOGM3NTk2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDExMTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMTE2VDA3MzgxNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQxOWFkOWQ5MmIxNTY0MDYwY2M5NmY4Mjg5MTk2ZmFkMTA3MjFhNDQ5ZTg0N2Q4ZTY1ODdiZTE3ZWUyMjE1ZWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.6oUFGWu9FzQUQOIf271PiTqxTE60SU9vYbireP6MT2g"> > > 成功!!! 这不是最终解决办法啊,那项目非得用node呢。我怀疑是某个指令是npm 与node的npm冲突了。
Author
Owner

@github-actions[bot] commented on GitHub (May 18, 2025):

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

<!-- gh-comment-id:2888715037 --> @github-actions[bot] commented on GitHub (May 18, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#2593
No description provided.