-
Notifications
You must be signed in to change notification settings - Fork 10
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
Server no more available #10
Comments
I've had the same problem. Could solve it by updating speedtest-cli https://github.com/sivel/speedtest-cli to the latest version. |
Update: unfortunately it did not solve it completely, but it happens less often now (might be coincidental). We don't seem to be the only ones experiencing this: |
By analyzing the official test webpage requests it seems JSON server list at https://www.speedtest.net/api/js/servers?engine=js&limit=10&https_functional=true is used instead of XML at www.speedtest.net/speedtest-servers(-static)?.php and c.speedtest.net/speedtest-servers(-static)?.php. |
I found that the speedtest-cli from sivel was getting less and less reliable too. I have begun work on an updated plugin which uses the official binaries from Speedtest: https://www.speedtest.net/apps/cli I have a version of this working at work; but I am not completely happy with how it runs. The speedtest-native branch of this repo has my code so far... |
Yes I had better to write on a sivel's pull request... the issue I'm experiencing is exactly the one you mentioned. Thanks, going to do that. |
Just download version 1.3 of the script from https://github.com/iLem0n/nagios-speedtest/tree/0f0fd188a9ef0f37db71372ec3d6cd0784841c79 and use option for automatic server selection. |
Hi!
During the last period, I observed that the Servers available for the test is changing continuously.
So, if you writhe the server ID into a NAGIOS\ICINGA command, in case this server will change - the command does not work anymore.
Is possible to select the best server automatically?
As you do, when you run the script manually?
THX
The text was updated successfully, but these errors were encountered: