m-cli VS speedtest-cli

The reason developers use terminal/shell is because of its command line interface i.e, each task is a line/command. Each command maybe anything only limited by the tools you have installed on system. These lines can be placed together in a script and run together and developers often use it like this for automation. It is like programming the system. You can install a lot of tools using HomeBrew and lot of tools... Source: about 3 years ago

That's a community cli client https://github.com/sivel/speedtest-cli rather than the official cli client https://www.speedtest.net/apps/cli. Source: 10 months ago

If you read the docs for Speedtest-CLI you will see that the program timeouts after 10 seconds. Try using this for default timeout of 1 minute and also redirect errors to the same file. Speedtest-cli --timeout 60 >> /bin/speedtestoutput.txt 2>&1. Source: over 1 year ago

Already exists https://github.com/sivel/speedtest-cli/, mature, stable, packaged in major distributions. Source: over 1 year ago

I have an open-source software, which can show some stats about your PC/Server. One of those stats is internet speed. I have been using speedtest-cli for now, since it is open-source and runs without having to accept any license agreements. Source: almost 2 years ago

Ah that makes sense then. You could try out https://github.com/sivel/speedtest-cli instead on Ubuntu and see what that comes up with but if it’s still detecting a random, far-away server then you’ll have to use the help options to narrow down your test to your country. Or better yet, try and use the same one that’s fine on your PC 🙏. Source: about 2 years ago