FastDomain - Using CloudFlare
 

FastDomain Web Hosting Help

Using CloudFlare

Summary

CloudFlare is a FREE system that acts as a proxy between your visitors and our server. By acting as a proxy, CloudFlare caches static content for your site, subsequently lowering the number of requests to our servers while allowing visitors to access your site.



Pros and Cons of CloudFlare

Advantages of the CloudFlare System

  • Site Performance Improvement- CloudFlare has proxy servers located throughout the world. Proxy servers are located closer to your visitors, which means they will likely see page load speed improvements as the cached content is delivered from the closest caching box instead of directly off our server. There is a lot of research showing a correlation between the speed of a site and the length of time that a visitor stays.
  • Bot and Threat Protection- CloudFlare uses data from Project Honey Pot and other third party sources, as well as the data from its community to identify malicious threats online and stop the attacks before they even get to your site. You can see which threats are being stopped through your CloudFlare dashboard.
  • Spam Comments Protection- CloudFlare leverages data from third party resources to reduce the number of spam comments on your site
  • Alerting Visitors of Infected Computers- CloudFlare alerts human visitors that have an infected computer that they need to take action to clean up the malware or virus on their machine. The visitor can enter a CAPTCHA to gain access to your site.
  • Offline Browsing Mode: In the event that our server is unavailable, visitors should still be able to access your site since CloudFlare serves the visitor a page from its cache.
  • Lower CPU Usage- As fewer requests hit our server, this lowers the overall CPU usage of your account.
  • New Site Stats- You have good tools to evaluate human traffic coming to your site, but no insight into search engine crawlers and threats. With CloudFlare, now you do.

Limitations of the CloudFlare Stystem

  • Currently, requests must be directed to www.$domain instead of $domain (which means you may need to make some configuration changes).
  • CloudFlare may affect internal statistic programs that read directly from Apache logs (CloudFlare will not affect web-based analytic programs that use JavaScript like Google Analytics.) While your logs will reflect fewer requests to your server and therefore lower load, the experience to your visitors should be unaffected.
  • CloudFlare caches static content from your site. While this reduces the load on your server, it means that if you make a change to an existing static file, like an image, there may be a delay before the change appears. While you are updating your site, you can put CloudFlare in Development Mode so changes appear immediately.
  • CloudFlare's basic mode cannot handle SSL certificates. If you need to use an SSL certificate, that part of your site needs to be on a subdomain that is not protected.

Enabling CloudFlare

Shared plans may enable CloudFlare services via the control panel by using the icon located in the Domains section.

  1. Click the CloudFlare icon, located in the Domains section.


    CloudFlare


  2. Under the Enable CloudFlare section, click the Next button to create your "Free CloudFlare Account."
    Note: You will need to agree to Terms of Service.


  3. CloudFlare


  4. Under the CloudFlare Account View section, click Activate to enable CloudFlare.

CloudFlare's searchable knowledge base is available at CloudFlare Support.

For information on how to disable CloudFlare, read:



Was this resource helpful?

Did this resolve your issue?


Please add any other comments or suggestions about this content:





Recommended Help Content

This article explains the name server requirement for using CloudFlare.
Knowledgebase Article 230,538 views tags: cloudflare nameserver

How do I disable CloudFlare for my domain?
Knowledgebase Article 353,697 views tags: cloudflare disable

How to Modify Your DNS Records
Knowledgebase Article 1,550,067 views tags: a aaaa access cname dns editor management mx nameserver ns ptr server spf txt update zone

Related Help Content

What are the commonly used DNS entries?
Knowledgebase Article 844,118 views tags: a aaaa cname dns record srv txt zone

Any time DNS is updated, it can take up to 48 hours for those changes to take effect. This period of time is called propagation, and it applies to any and all DNS updates. This article will explain what propagation is and why it's important.
Knowledgebase Article 165,080 views tags: a cache cname dns domains mx propagation txt

How do I flush my DNS cache?
Knowledgebase Article 298,145 views tags: dns dnsflush flush ipconfig network

Do you support wildcard subdomains or wildcard DNS entries?
Knowledgebase Article 316,823 views tags: dns domain subdomain wildcard zone

How do I Change My DNS?
Knowledgebase Article 501,037 views tags: change delegate dns modify

I would like to change my MX Record so I can use a mail server with another provider.
Knowledgebase Article 660,583 views tags: dns email exchanger local mail mx remote routing

The hosts file is a plain text file that allows you to set IP Addresses for a domain on your computer. This may override authoritative DNS.
Knowledgebase Article 114,841 views tags: admin development dns file hosts ip test

When you call in for help with your account, the account must be validated before our support staff can assist.
Knowledgebase Article 134,611 views tags: account security support validate validation