-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
403 error fix #790
base: master
Are you sure you want to change the base?
403 error fix #790
Conversation
Fixing the 403 error by making all requests use HTTPS instead of HTTP. Also removing the --secure flag as it's now enabled by default.
Please merge as the tool is unusable at the moment |
This version doesn't work for me |
Do you have any specific error? |
Can you try this on Windows? |
no on Linux Debian |
Yes but can you try it on Windows? |
Where do you provide the '--secure' flag? I'm running speedtest.py through curl. And every time I I try to pass the '--secure' flag to the script in the url, curl gripes at me about it being an unknown option. ([...]/master/speedtest.py --secure | python3 -) Or can you not pass options to the script when running as a url? |
You're just simply using curl to download the file from GitHub and then telling python to read the contents of the file through stdin using the - after python. You can provide any arguments you want, specifically to the python script, after the - argument like this. Again think of the dash as you telling python that instead of reading from a file on the disk just read from stdin, which in this case you're piping stdout of curl into stdin of python. You might already know this, but just wanted to clarify. |
Thank you; I'm kinda new to working with curl like this, (or really in much of any capacity) so, I wasn't sure. |
I have speedtest-cli 2.1.3, which I run on Linux (Mint) and occasionally I see the following.
I am unsure what workaround, if any, this page (the current webpage) is suggesting. |
@LinuxOnTheDesktop - just run it with the "secure" flag and everything will be good. Provider finally starts blocking HTTP requests and looks like most of their servers allowing only HTTPS protocol: |
Right. Thank you. Will do.
Yet me clarify that, in case someone else comes across it and has trouble understanding it. So: the servers that provide the speed tests are blocking speedtest-cli (or rather, in my experience: blocking it sometimes) because (by default, i.e. without |
i prefer #800 for the |
Fixing the 403 error by making all requests use HTTPS instead of HTTP. Also removing the --secure flag as it's now enabled by default.