Ookla Server – How to Set Up for Speed Test

httpsUbuntu

I'm trying to setup an Ookla server for speed test. My OS is Ubuntu (20.04 LTS) and I installed the script, also set it up to start after reboot, but I don't know how to set it up to work with HTTPS. The test page says my server passed on netgauge, websocket and crossdomain but failed on https. I would also like to know how I use my server for speed testing before I upload it to Ookla? I would like to know what is the speed and how it performs. I didn't find much documentation on Ookla's website, for example I didn't find how to setup HTTPS. If I get a certificate from Let's encrypt, how do I install and use my certificate?

For installing the server, I followed the links on https://www.speedtest.net/speedtest-servers.

Best Answer

https://support.ookla.com/hc/en-us/articles/234578568 says

Please note that the automatic Let's Encrypt certificate provisioning will not begin until after your server has been submitted and either approved or accepted for use. The HTTPS test on the Server Tester can be ignored during the initial submission period.

I believe your other questions would also best be answered by Ookla support.

Related Solutions

Nginx – Public Key Pinning headers correct setup and failure test

To be accepted, your pin must :

Contains at least one key of the current certificate chain
Contains at least one key NOT in the current certificate chain (a "Back up key"). I think this one was missing in your case.

To test it :

use firefox developper edition, go in the network tab, select a request, select the security tab of the right. It must indicate "Public Key Pinning" with the status
if you really want to produce the error, use the option "include subdomains", and sign any subdomain with a new key. Firefox should refuse the connection.

Some docs : https://developer.mozilla.org/en-US/docs/Web/Security/Public_Key_Pinning

To be more specific : "If I don't include the certificate's pin-sha256 (nor any intermediate or root certificate's)", then the browser don't save the pin. The browser display at connection error only when an already saved pin list doesn't match the current certificate chain.

https://scotthelme.co.uk/hpkp-toolset and https://report-uri.io/home/pkp_analyse can help

Web-server – Disable https for a single file in apache

On your default vhost, try the following:

 RewriteEngine on
 RewriteCond %{HTTPS} !=on
 RewriteCond %{REQUEST_URI} !^/path/to/your_single_file.html$
 RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [L,QSA,R=permanent]

Best Answer

Related Solutions

Nginx – Public Key Pinning headers correct setup and failure test

Web-server – Disable https for a single file in apache

Related Topic