Cloudflare Tips: Troubleshooting Common Problems
Debugging technical issues online can be tricky. There are many moving pieces; it can be an isolated network connection with the ISP, an issue with your server or one of Cloudflare's data centers could be temporarily having a problem. We wanted to share some tips on how to troubleshoot website issues and provide some good techniques to prevent site issues in the future.

Website is Unavailable

If you can't get to your website and you see a cached copy of your website or a "Your Website is Unavailable" error page, the first thing to do is to check if your server is having issues.

How to quickly test if your server is having issues

For Mac Users:
Open the application called terminal on your Mac, and run the following curl command to see if your server is responding:

curl -v -A firefox/4.0 -H 'Host: yourdomain.com' YourServerIP

--> YourServerIP: You can get the IP for your server origin by checking your DNS Settings page on your Cloudflare account. It will look something like 192.73.146.94

When you press enter, you'll get an output message.

If you get an error message like "can't connect to host" or "500 internal server error", then this means that your server is not responding. You should contact your hosting provider and work with them to resolve the server issue.

If you get HTML returned, but you still get a site offline or unavailable message from Cloudflare, then this means that connections fromCloudflare's IPs are being restricted or blocked at either the hosting provider or server level. Please make sure that the CloudFlare IP addresses are whitelisted on your server and with your host.

If you can't access cPanel or useFTP

Cloudflare acts as a reverse proxy. As a result, you can still access cPanel or use FTP, but you will have to do so a little differently. To access cPanel or FTP:

Certain scripts on my website (like ads or social plugins) are breaking or not working

Cloudflare has two beta features that speed up the loading of your web pages, but they can sometimes cause issues.

Rocket Loader
Rocket Loader can potentially impact JavaScript calls on your site, including things that potentially use jQuery. For example, if you see an ad widget breaking, it is possible that Rocket Loader is breaking the JavaScript and you should turn this feature off by going to your Cloudflare Settings page.

If you want to keep Rocket Loader turned on for the performance boosts, you can make some edits for the service to ignore certain scripts on your site.

Note: Rocket Loader is defaulted to off upon signup. Once you turn it on or off, the change takes less than 3 minutes to take effect.

Auto Minify
Auto Minify rarely impacts CSS and JavaScript. However, Auto Minify can sometimes cause issues if you already have another minification service turned on. We recommend that you only have one minify option turned on for your website.

The changes I made to my website aren't appearing:

If you're making changes to the static content Cloudflare caches on your site, including changes to JavaScript, CSS or images, it can be very easy to forget that you need to turn Cloudflare Development Mode on to bypass our cache so these changes appear immediately.If you forgot to turn on Development Mode when making the changes, you can always purge your Cloudflare cache to have these changes appear immediately. Just a reminder that by purging the cache for your website, there will be a performance impact for a couple of hours.

Preventing site issues while on Cloudflare

The most important step you can take is to make sure that your server or hosting provider has the Cloudflare IP ranges whitelisted. If any attempts to connect to your site are blocked or limited in any way, this could create connectivity issues to your site for some of your visitors.Another very important step you can take is to install mod_cloudflare (which is an Apache module) on your server. mod_cloudflare will restore the original visitor IP back to your server logs, and is also a good way to reduce the probability that your hosting provider will limit connections from CloudFlare's IPs. If you are not using Apache, we have a list of solutions for nginx, Windows and others in the CloudFlare Support Forums.

Cloudflare is Having an Issue

Cloudflare runs 14 data centers around the world. Sometimes issues arise at one of our data centers, and we deal with these quickly (on average, in less than 10 minutes). Only visitors in that geographic region are affected.

If you get a report from one of your visitors that they can not connect to your website:

  1. Check to make sure your server is online (see instructions on to do this above)

  2. If your server is online, make sure Cloudflare's IPs are not being blocked

  3. If your server is online and Cloudflare's IP are not being blocked, send us the report here. In your email, include:
    i) Your website
    ii) Where the visitor is geographically located (Issues are almost always isolated to one of our data centers. By knowing where they are located, we can investigate much quicker)
    iii) A description of the error page they are seeing
    iv) The output of a traceroute (if possible)

  4. Temporarily deactivate Cloudflare for your website by choosing
    ‘Deactivate' from your Cloudlare control panel. Choosing deactivate means that CloudFlare will continue to resolve DNS for your website, but none of your traffic will pass through our performance and security network. If it is a CloudFlare issue, this will immediately resolve the problem and our team can investigate the report. Once we've identified what is wrong, you will easily be able to reactivate CloudFlare. Note: You do not need to change your name servers.

I hope these tips help you troubleshoot some of the common issues users have on Cloudlare. Please let us know if there are any other areas of confusion that we can address in either our help section or in another Cloudflare blog post.