Knowledge Base

Troubleshooting CloudFlare connections

If you experience connection-related issues with your web site when CloudFlare is enabled, this article provides information you can use to troubleshoot and help determine the cause.

For information about what CloudFlare is and what it can do for your site, please see this article.

CloudFlare error pages

One of the most common (and visible) indications of a problem is when your site displays a CloudFlare error page instead of your own content. These error pages can provide valuable information about why your site is not loading correctly.

There are several scenarios where CloudFlare displays an error page:

Site DNS settings

For CloudFlare to work, your site's DNS settings must be configured to route traffic through their network. When you enable CloudFlare using cPanel, this process happens automatically.

  • If your site experiences connection issues and it has been less than 24 hours since you enabled CloudFlare, please be patient. It can take up to 24 hours for DNS propagation to complete.
  • If you receive a blank page in your browser (sometimes referred to as the “white screen of death”), this indicates a problem with your site's web application or the web server itself—CloudFlare is not the cause.

To verify that your site is configured at the DNS level to use CloudFlare's network, follow these steps:

  1. Log in to your account using SSH.
  2. At the command prompt, type the following command. Replace example.com with your own domain name:
    dig www.example.com @127.0.0.1
    • If dig receives a response of www.example.com.cdn.cloudflare.net, where example.com represents your domain name, go to step 3.
    • If dig does not receive this response, your domain's DNS is not configured to use CloudFlare. If cPanel indicates that CloudFlare is enabled, please open a support ticket on the A2 Hosting Customer Portal at https://my.a2hosting.com so we can investigate further.
  3. At the command prompt, type the following command. Replace example.com with your own domain name:

    dig www.example.com
    • If dig receives a response of www.example.com.cdn.cloudflare.net, where example.com represents your domain name, go to step 4.
    • If dig does not receive this response, your domain's DNS is not configured to use CloudFlare. If cPanel indicates that CloudFlare is enabled, please open a support ticket on the A2 Hosting Customer Portal at https://my.a2hosting.com so we can investigate further.
  4. On your local computer, use dig or nslookup to query www.example.com, where example.com represents your domain name.

    For information about how to use dig or nslookup on your own computer, please see this article.
    • If you receive a response of www.example.com.cdn.cloudflare.net, where example.com represents your domain name, then your domain's DNS settings are working along the entire connection path from your local computer to CloudFlare to the server.
    • If you do not receive this response, the problem is not with CloudFlare. Your local computer or network may have a configuration issue preventing access to the CloudFlare network or your site.