Community Tip - Fixing "The Speed test could not run"

Try the suggestions in this Community Tip to help you fix the error The Speed test could not run.

The “Speed test could not run” error on the Speed app of the Cloudflare Dashboard indicates the test was somehow blocked. The blocks can occur due to a rule you have set in Cloudflare, a restriction from your hosting provider, or it may just be a temporary issue that resolves without intervention. When the test is somehow blocked, you’ll see the error “The Speed test could not run”. Follow the Quick Fix Ideas to resolve the issue.

Quick Fix Ideas

  1. The site was just added to Cloudflare and is not yet active. Wait until the site becomes active and you are sure the traffic is going through Cloudflare.

  2. It’s a temporary delay, sometimes fetching data for the test takes time and you need to try a couple of times. You may see a 504 error that the origin server (e.g., the web host) is returning to us.

  3. Review any existing Firewall Rules which may be blocking access to ‘Known Bots’.

  4. Review the configuration between your origin server and Cloudflare and ensure that the origin resolves requests successfully. You may see a 522 error if you’ve not whitelisted Cloudflare’s IP’s at your origin server,

  5. Speed tests are performed from Google Cloud Platform IP addresses which will fail if rate limited or blocked at the server or hosting provider. When this happens, we will not be able to execute the test. Review the documentation to verify the IPs are allowed,

  6. Assuming there are no Cloudflare Firewall Rules or Rate Limiting settings or filters in place through your Cloudflare dashboard, the problem may be with your origin server. Check with your server administrator or hosting provider to ensure there are no rules or filters in place on the origin that would cause this issue. You’ll want to ask them to check for IP address, browser, and user-agent blocks. A 403 error in the Speed tab is always returned directly from the origin web server, not Cloudflare, and is generally related to permission rules on the origin server. Either a permission rule or an error in the .htaccess rules, the Mod_security rules, or the IP Deny rules are the most likely reasons for the 403. Use the cURL below to the origin to check for a 403 Forbidden:

    $ curl -I --connect-to ::
    HTTP/1.1 403 Forbidden
    Date: Mon, 11 Nov 2019 09:28:04 GMT
    Server: Apache
    Content-Type: text/html; charset=iso-8859-1

  1. Add a firewall rule that allows Known Bots.

  2. If you’re still unable to run the Speed test and are seeing an error 404, 526, or 530 error please contact Cloudflare Support for more help.

Research The Issue

If You Need More Help
This community of other Cloudflare users may be able to assist you, if not, login to Cloudflare and then contact Cloudflare Support.

Expert Comments Appreciated
This Community Tip will remain open for input from experts and those familiar with this issue. We really appreciate comments that start with words like: “The three things I always try”, or “Do this first” or “In my experience”.

This is a Cloudflare Community Tip, to review other tips click here.

Çevirme…traduzir…翻译…traducir…Traduire…Übersetzen…:greyg: Translate this Tip

FXSTCT 052820

1 Like

This topic was automatically closed after 30 days. New replies are no longer allowed.