- Notifications
You must be signed in to change notification settings - Fork3.2k
Fix the stuck at startup causing 502 bad gateway.#4021
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:develop
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There are some issues about 502 bad gateway, cannot login. Some cloud vendors like Tencentcloud may block aws or be block by aws. Also , it may take a long time downloading this file, which blocked the port 81 backend. |
c3f210e tobdcc904CompareDocker Image for build 2 is available onDockerHub as Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes. |
| @@ -15,7 +15,6 @@ async function appStart () { | |||
| .then(() => { | |||
| return apiValidator.loadSchemas; | |||
| }) | |||
| .then(internalIpRanges.fetch) | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Removing this is not good enough to fix the problem. This call might be in the wrong place but you haven't put a better one in the pr.
yangluoning commentedNov 13, 2024
@jc21 develop branch dont have your commit，Is it flushed by other commit? |
I'm not sure what "commit" you're talking about? This PR is not mine and is not merged either. |
PR is now considered stale. If you want to keep it open, please comment 👍 |
For a quick workaround, you can run the following commands: NPM_CTR_NAME=nginxproxymanagerdockerexec$NPM_CTR_NAME sed -i's/\.then(internalIpRanges\.fetch)//g' /app/index.jsdocker restart$NPM_CTR_NAME This will patch the application to skip fetching the IP ranges on startup. Alternatively, as of#4398, you can use the IP_RANGES_FETCH_ENABLED environment variable to control this behavior. To disable the fetch, set: IP_RANGES_FETCH_ENABLED=false This will also prevent the application from hanging at startup. However,note that the default behavior is still to attempt downloading the IP ranges unless explicitly disabled. |
Some cloud vendors may have been blocked by AWS, this led to stuck at startup.