Login failure 502 bad gateway

[burningimlam]

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

When I installed npm and logged in, 502 bad gateway appeared

I have tried to replace the image version and change the installation location. A problem was found when the npm mirror was started he got stuck at Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
Since the system is now booted normally, please forgive me for not providing a complete error log
Nginx Proxy Manager Version
2.10.4，latest

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

Screenshots

Operating System

Additional context

[burningimlam]

#3965

I executed the command in the link to get the system to start properly

commands：

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

[lybtt]

#3965

I executed the command in the link to get the system to start properly

commands：

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

Indeed, it seems that the request is being blocked.

[makeup1122]

没有完全启动导致的502，我是因为国内访问https://ip-ranges.amazonaws.com/ip-ranges.json困难， 添加DNS 8.8.8.8 解决了

[ghostlitao]

没有完全启动导致的502，我是因为国内访问https://ip-ranges.amazonaws.com/ip-ranges.json困难， 添加DNS 8.8.8.8 解决了

Yes , Just because it is not fully started, it will cause 502. I am using the intranet and cannot access the internat.
After the

app-1  | [12/11/2024] [4:57:23 AM] [IP Ranges] › ✖  error
``` shows Error , every thing works fine .