CloudFlare and Joomla: Recommended First Steps

These basic steps will help reduce common areas of confusion for Joomla users that are new to the CloudFlare services. In addition, these steps are very quick and will generally take you only a few minutes of your time to help you make your experience using CloudFlare better.

Step #1

Install the CloudFlare Joomla plugin to restore visitor IP. Since CloudFlare acts as a proxy for sites using our network, CloudFlare’s IPs are going to show in your logs, including comments, unless you install something to restore the original visitor IP.

Why should you install the plugin?

If you receive a lot of comments or spam on your blog, you may mistakenly believe that CloudFlare is spamming you. Some other Joomla plugins or extensions  may also rely on the original visitor IP for the  services to work properly and reduce false alerts.

Note: You don’t need to worry about this if you activated through a hosting partner, since they already have mod_cloudflare added to their servers by default.

Step #2

Create a PageRule to exclude the Joomla admin or Joomla login sections from CloudFlare’s caching and performance features. You can access PageRules in your CloudFlare 'Settings' options.

Why do this?

While there is not always an issue, we have seen instances where optional performance features like Rocket Loader may inadvertently break certain functions (editors, etc.) in your Joomla back end.

Step #3

Login to your CloudFlare Threat Control panel and whitelistist IP addresses you want traffic from or expect traffic from. Some common services you probably want to whitelist include:

  • APIs you’re pulling from
  • Monitoring services you use to monitor your site's uptime
  • Security services
  • IP addresses you frequently login from

Why do this?

If CloudFlare has an IP address with a high threat score going to your site, or if you have CloudFlare's Web Application Firewall turned on, you may get challenged working in your back end and/or services you want to access your site may get challenged. Taking the steps to whitelist in the beginning will help prevent future surprises on your site.

Note: We whitelist all known search engine and social media crawlers in our macro list. If you decide to block countries in Threat Control, please use care because you may end up inadvertently blocking their crawlers (blocking the USA, for example, could mean that their crawler gets challenged).

Step #4

Review your basic security settings

If your site is  frequently the target of spam attacks or botnet attacks, changing your security level to a higher setting will help further reduce the amount of spam you get on your site. We default all users to a medium setting when they first add the domain to CloudFlare.

Why do this?

If you want your site to have less security and protection from various attacks, then you would want to change your settings to a lower level (please keep in mind this makes your site more vulnerable). If you want your site to have higher security, please keep in mind that you may get more false positives from visitors complaining about a challenge page that they have to pass to enter your site.

Step #5

If you are using services like .htaccess, firewalls or server mods to manage access to your site from visitors, it is vitally important to make sure requests from CloudFlare’s IP ranges are not being blocked or limited in any way. The number one cause of site offline issues in our support channel is something blocking or restricting requests from our IPs, so please take the time to make sure that all of CloudFlare’s IPs are whitelisted on your server.

Why do this?

Prevent false offline messages from appearing on your site to you or visitors.

Still not finding what you need?

The CloudFlare team is here to help. 95% of questions can be answered using the search tool, but if you can’t find what you need, submit a support request.

Powered by Zendesk