CloudFlare is a service that takes a great deal of pride in listening to the feedback of our users. CloudFlare recently had a customer make a very strong case that we build a WordPress plugin for CloudFlare, something we were considering asking a developer to build, but the customer convinced us to build our own. Within a few weeks, Ian built our first iteration of the CloudFlare WordPress plugin that is now live.
Some common FAQs about the CloudFlare plugin can be found below:What does the CloudFlare plugin do?- Restores the original visitor IP to your WordPress logs. Before the plugin the IP addresses would reflect CloudFlare's proxy IP addresses, which confused many blog owners.
- Helps optimize your server database.
- You can report spam in the plugin, which then feeds the report to CloudFlare to make our system smarter at stopping spam for sites on our network (coming by week ending November 13th). How do I install the CloudFlare plugin?
A few clicks are all that is needed to upload the plugin to your blog. Do I need to be a CloudFlare customer to install the WordPress Plugin?
While we would love for you to be a customer of CloudFlare so you get our speed and protection enhancements for your blog, our plugin was designed so that it could be used by any WordPress blog owner. You still receive the benefits of making sure your server database is optimized.Does CloudFlare conflict with Akismet or W3 Total Cache?
No, we've designed our plugin to be complementary to all plugins, including Akismet and W3 Total Cache. Can I use the CloudFlare with a WordPress.com blog?
Wordpress does not allow for modifications to free blogs, which means the plugin will only work for self-hosted blogs. Have a suggestion for improving the CloudFlare plugin? Do you want a plugin for a different blogging platform? Please contact CloudFlare with your suggestions.
Comments (47)
Thanks'
We have solutions for many platforms, including Apache, here: http://www.cloudflare.com/wiki/Log_Files
Installing mod_cloudflare (if possible) is the best possible solution.
May have somebody working on Joomla. We will try to keep you posted.
First time I've heard of a 404 error (generally not an error returned by CloudFlare). Can you send us an email to help [at] cloudflare [dot] com? Would be helpful to know:
CloudFlare account email address
Version of WordPress you're using
I am approaching my server directly (as its on my own subnet) however the plugin claims that cloudflare is not installed (while it is) so I guess the detection method is not entirely accurate, this is nothing big, but probably worth fixing.
Good luck with your service.
Going something like direct.yourdomain.com would trigger that message, unfortunately. It should not be present for domains that are CloudFlare enabled (yourdomain.com, www.yourdomain.com, etc.).
Not only by going to direct, but also in the case where one has his server directly set in hosts file, or any other dns method (such as an internal zone file, such as in my case). again, this is no biggy, I fully understand why it happens etc, but the message may be misleading, and you should probably either change the wording (may not be ....) or change the detection method to query your servers somehow (non-dns)
Thanks for the response.
We'll figure out some solution.
The plugin is 100% optional. I would recommend it, however, if you want to see original visitor IP without having to make modifications to you server. Since we act as a proxy for your site, it means our IPs would reflect without making one of the changes.
"You are not currently using CloudFlare. Sign up for CloudFlare here. Once you are on CloudFlare, this plugin will automatically work.
The most common reason for the message above is that www is not added to your DNS zone file. Please add www under your DNS Settings by making a CNAME record of www as an alias to your domain.com.
Note: This error message will also be displayed if you are on direct.yourdomain.com, or a similar subdomain. "
This is on my main domain.com on a WP multisite, (without www).
Cheers,Harry
That exact cname already exists (as is the Aname for the * wildcard for WP subdomains), so the problem is elsewhere..<o:p></o:p>
From: Posterous [mailto:comment-dFCmDgakJBpiaol@posterous.com]
Sent: vrijdag 10 december 2010 20:59
To: info@exposedplanet.com
Subject: [blog.cloudflare.com] Comment on "Introducing the CloudFlare WordPress Plugin"<o:p></o:p>
The error disappeared after 24 hours and the stopped botnets are appearing so that is good.<o:p></o:p>
The bad thing is that many times I get the CloudFlare black screen of death saying my site is offline, which it is not.<o:p></o:p>
(Site is http://exposedplanet.com) <o:p></o:p>
I have not blocked the IP’s (else it would not work anyway).<o:p></o:p>
One other showstopper is that with using WordPress The Quick Edit function (of posts) does not work anymore, it never saves or sometimes it does, but never end normally (Quick editscreen disappearing). Also the regular edit times out 50% of the times.<o:p></o:p>
I have another WP installation on the exact same server/IP but with the host’s nameservers and there the (Quick) edits work as expected.<o:p></o:p>
Any info on this before I switch CF off again? <o:p></o:p>
Many thanks, Harry<o:p></o:p>
From: Posterous [mailto:comment-dFCmDgakJBpiaol@posterous.com]
Sent: vrijdag 10 december 2010 21:22
To: info@exposedplanet.com
Subject: [blog.cloudflare.com] Comment on "Introducing the CloudFlare WordPress Plugin"<o:p></o:p>
Other problem when I try to edit a theme or plugin in wp-admin of Wordpress, after confirm update, it's redirect me to homepage and nothing happens
Directions for Google MX records here: https://cloudflare.tenderapp.com/kb/adding-sites-cloudflare/how-do-i-add-a-cn...
Can't think of any reason for the other issues & would need more details. Are you using a beta version of a browser?
Thank for your support !
CloudFlare built our plugin to be complementary to services like W3TC (W3 Total Cache) and Akismet. I would recommend utilizing these plugins as well & not removing existing plugins.
I'm new here, and a little bit confused about the concept. I use CloudFlare as my authoritative DNS, and I also use statcounter on my wordpress blog. I notice that CloudFlare is already setup properly because every time I try posting comment from foreign IP, the notification email said that comment is from CloudFlare ip subnet.
But when I check in my statcounter dashboard, I can still see the origin IP of the visitor, not the CloudFlare subnet. Why is that happen? Is that right? I mean, if we post comment to wordpress then it shows the CloudFlare IP's, but why when we just browse the website then it shows the visitor's origin IP?
Thank you very much, any helps would be greatly appreciated!
No need to have both plugins, unless you want the spam reporting capabilities in the CloudFlare WordPress plugin.
One related tip: you might want to use our new beta feature, Page Rules, to disable CloudFlare on the /wp-admin/ directory. https://www.cloudflare.com/preview-page-rules will take you there if logged in to your CloudFlare account.
BTW, direct.thegamemusicguy.com/ works fine for me, so maybe you've solved this already?
My twitter plugin stopped working and none of several ones available seems to work.
My twitter plugin stopped working and none of several ones available seems to work.
No, not directly. If you're using a widget based on JavaScript,
however, beta features like Rocket Loader or Auto Minify may have
impacted it. Does turning them off fix the issue?
http://www.cloudflare.com/wiki/Log_Files
Leave a comment...