Troubleshooting

Troubleshooting

Below are error messages one might see if an installation is not configured properly. Potential reasons and solutions are also provided for each possible error message.

Expired License

The license for this Speedtest® has expired.

Please contact the webmaster of this site to let them know.

The license key that has been loaded by the Speedtest® (found in the settings file on the server) is not valid due to the expiration date being passed. You will need to contact Ookla to make sure that your account is current and you have your most recent license key.

Wrong License

This Speedtest® is not setup to work at this URL.

Please contact the webmaster of this site to let them know.

The license key that has been loaded by the Speedtest® (found in the settings file on the server) is not valid due to the URLspeedtest.swf was loaded from not being in the access list. Make sure that the full path to speedtest.swf matches what Ookla has setup for your account.

Invalid License

The license for this Speedtest® is invalid or the configuration is missing.

Please contact the webmaster of this site to let them know.

The license key that has been loaded by the Speedtest® is not valid for this Speedtest®. This is usually caused by a typo or hidden character in the license key.

Configuration Load Failed

The configuration for the Speedtest® couldn't be loaded.

Please contact the webmaster of this site to let them know.

This means the test was unable to load the settings file itself. Make sure that you can load it directly in your browser without an error.

Missing License Key

Download Error

Download test returned an error while trying to read the download file.

This error message means that the test was unable to load one of the download sample files on the server. The most common cause of this is an error in the server URL in your settings file. Test to see if you can load one of the smaller sample files (such as random350x350.jpg) in the same directory as the upload script using a web browser.

Upload Error

Upload test returned an error while trying to read the upload file.

This is one of the most commonly seen errors with a newly setup server. It means that there was an issue trying to send data to the chosen upload script on the server. If you receive the error right at the start of the upload test the issue is likely one of the following:

The scripting language (PHP, ASP.NET, ASP or JSP) is not properly setup or the wrong one was chosen (learn more here).

The upload testing script is on a different host than the Speedtest® - try copying crossdomain.xml to the web root of the testing server to resolve this

If the upload test starts but then fails with this error then the problem is usually related to a maximum HTTP POST size getting hit. Here are tips to resolving it on some platforms:

Apache with PHP (DO NOT use mod_security)

Open apache2.conf or httpd.conf

Search for LimitRequestBody and remove that line if it exists

Open php.conf or php.ini

Search for post_max_size and increase it to 10M

Restart Apache (usually /etc/init.d/httpd restart)

IIS6 using ASP

Open IIS Manager

Right-click on the server name at the top of the tree and choose Properties

Check the first box for Enable Direct Metabase Edit and click the OK button

Open C:\Windows\System32\Inetsrv\metabase.xml with Notepad (NOT Wordpad)

Find AspMaxRequestEntityAllowed and change it to 1073741824

Find AspEnableChunkedEncoding and set it to False

Latency Error

Latency test returned an error while trying to read the latency file.

This error message means that the test was unable to load the latency test file on the server. The most common cause of this is an error in the server URL in your settings file. Test to see if you can load latency.txt in the same directory as the upload script using a web browser.

Daily Limit Exceeded

You have exceeded the limit of tests per day.

This Speedtest® has been setup to use the Ookla throttling API to limit the number of tests a client can take in a 24 hour period. You will need to wait until tomorrow to take another test.

Java Failure

Test cannot be completed. The Java portion of the test could not be started. Please ensure that Java 1.4 or newer is installed and setup correctly then try again.

Server Unreachable

The test server is inaccessible. It is possible that a firewall is blocking the test from happening. Please verify your configuration and try again.

The client Java component loaded but was unable to reach the Java server daemon. This could be firewall related, or it could mean that the server is not properly configured. The default TCP port is 5060 which needs to be open between the client and the server.