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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/etc/nginx/conf.d/include/ip_ranges.conf contains HTML code of Cloudflare instead of IP addresses #1405
Comments
Interesting. This is probably a temporary issue with Cloudflare judging by the content of the html. This ip range fetch happens on every start of the docker container, so the easy fix is to restart NPM assuming that Cloudflare has also resolved their issue. I tested myself just now and it's not happening for me. Still, this highlights a need for better ip range management with the ability to handle this kind of outage. |
Not for this user. I suggested him to open the URLs manually to solve the captcha for his public IP, but he - instead of the container - never faces the captcha: I think filtering the API response for valid IP addresses should be done in any case. Better safe than sorry ;) |
Ah right. I didn't know this was behind throttling. |
Is there a way to manually edit this file to add the IP addresses? I am running the proxy manager on a remote server headless so opening the links in a browser to solve the captcha will not work for me. |
Issue is now considered stale. If you want to keep it open, please comment 👍 |
Error messages:
Reason (NPM does not filter/check the API response):
cat /etc/nginx/conf.d/include/ip_ranges.conf
Temporary solution:
By that the HTML code is removed and the file is locked for further updates.
The text was updated successfully, but these errors were encountered: