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
Digital Ocean API Change Breaking Pinger & Traffic #196
Comments
I was going nuts trying to figure out why it wasn't working on DigitalOcean also. Proxies would start up then not register as alive even though they were running themselves. I'm surprised this fix hasn't been pushed into production for scrapoxy. |
Maybe I could use private to connect over DigitalOcean VPC so,
|
Hello, |
@Tugrulvural89 matching using in check-alive is strict, so double check that you are using the right case in values e.g. region to be lon1 instead of LON1 |
This fix really helps us, thanks |
@Tugrulvural89 If you used "sudo npm install -g scrapoxy" and installed scrapoxy again in your local module, make sure you change the settings in the global node module. |
it will be corrected in the 4.0.0 version |
Hey there! 🌟 Exciting news! Scrapoxy 4 is ready to rock 🚀. Check it out at Scrapoxy.io (explore the "get started" guide, deployment documentation, and more 📚). |
Hello,
We noticed around 1PM today our Proxies for DigitalOcean started to fail to come online. Upon checking Scrapoxy, I noticed the control panel was reporting the local (private) IP address for all DO proxies. The pinger would then attempt to ping a private IP, which it obviously cannot reach, causing Scrapoxy to never properly see the online status of any DO instances.
Expected Behavior
Request is sent to digitalocean API to fetch a summary of all instance details. The Digital Ocean provider should then parse the API response and report the public IP to the Scrapoxy manager.
Actual Behavior
The API request is properly sent, but incorrectly parsed. The provider script is improperly hard-coded to recognize networks.v4[0].ip_address as the public ip address without checking the type. The causes the online status of DO instances to always be false. Digital Ocean began reporting private and public IPs, and the public IP was bumped to networks.v4[1].ip_address.
Fix
ip: _.get(_.find(_.get(droplet,'networks.v4'), _.matchesProperty('type', 'public')),'ip_address'),
Thanks
The text was updated successfully, but these errors were encountered: