-
Notifications
You must be signed in to change notification settings - Fork 32
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
EOF on Speedtest when starting node #105
Comments
any news? |
Same for me since a few months. |
I think this is an issue with speedtest-cli software since the dVPN node software uses it. I tried to use the speedtest-cli ( The github https://github.com/sivel/speedtest-cli says that they will not fix any issues any more. Maybe adopt the speedtest.net CLI in future dVPN node releases?? |
Yes, that is what they told me this summer but no fix since then :-( |
Maybe we should ping them on twitter: https://twitter.com/speedtest |
The CLI works for me. I installed it using
|
Yeah Sentinel should use this one going forward. I think (not sure though), they are are using that github speedtest-cli version |
Figured it out. It's a IP ban from speedtest.net - IN speedtest-cli at line 1447 it calls a routine to get the servers from speedtest.net which can be traced back to line 1261 where it requests the server information to preform a speedtest from the url running $ curl http://c.speedtest.net/speedtest-servers.php
<html><head><title>Too Many Requests</title></head><body><h1>429 Error - Too Many Requests</h1><p>Your IP address is making too many requests. We ask that you limit requests to no more than 1 per second.</p><p>We make an attempt to be flexible, allowing small bursts in traffic. You have exceeded this threshold however and have been blocked.</p><p>Please reduce the speed at which your requests are made and try again after a while. If you feel you have reached this message in error, please contact us at noc @ speedtest.net and reference this error code.</p><p>Thank you</p></body></html> I'm going to e-mail speedtest as they provided me their e-mail on twitter. |
Same error from my node. I get a correct list from another country. So they blocked all French IPs it seems. |
Solved with last release! |
Yes. This was fixed in 0.4.0. I will close it now. Good work!!! |
Describe the bug
A few users are experiencing issues with exactly one of their nodes after stopping it and restarting it. The error is an EOF immediately after beginning the Speedtest with speedtest.net
To Reproduce
Run the node
Expected behavior
For the Node to run as prior to restarting it. It seems there is a problem Fetching the servers in
utils/speedtest.go
This might be a speedtest thing, but I dunno, since it works on all other nodes. It could be a host problem on our end.Desktop (please complete the following information):
Additional context
I successfully spun up a new node and everything worked. It is just on exactly one node for many users. I downloaded the speedtest CLI by Okala and that did work.
The text was updated successfully, but these errors were encountered: