CloudFlare API error

WordPress 3.5.1
W3TC 0.9.2.8 alone ==> “Unable to communicate with CloudFlare API
tried several times to save settings, regenerated API key
was working ok with exactly same settings, didn’t change nothing

using WP Super Cache and CloudFlare plugin works ok, without “Unable to communicate with CloudFlare API”, but only got Page Speed 87% (B) while 95% (A) with W3TC, we need 0.9.2.9 with a fix.

The new update was actually breaking my theme (making it show up bad in Firefox). I deactivated this plugin since it was doing it, and my Yslow score actually went up and my site works great now. I miss the original W3TC before this past update :-/

I tried & tried again (re-typed e-mail, regenerated API key, saved different settings,…) : no way, still have “Unable to communicate with CloudFlare API: Setting: zone_settings Invalid token or email.” with W3TC 0.9.2.8 alone.

Is possible that CloudFlare dropped support to W3 Total Cache for this irriverent and not elegant message that appears on WordPress Dashboard after W3 total Cache / CloudFlare configuration:

CloudFlare plugin detected. We recommend removing the plugin as it offers no additional capabilities when W3 Total Cache is installed. This message will disappear when CloudFlare is removed.

Is Really Possible? :)-

When you are using W3TC you don’t need the Cloudflare plugin because W3TC have Cloudflare functionality inside, so you can remove that plugin to free resources, but you still using Cloudflare and W3TC recommends it, so Cloudflare should not be angry. ??

It’s not essential to remove the Cloudflare plugin, it’s just important that you try not to change settings in both places. Using either plugin to change settings or report spam is fine.

Hi

I actually have the issue, Is there any solution??

Best Regards

Same issue here – taken all the possible steps above, but the message prevails:

“Unable to communicate with CloudFlare API: Setting: zone_settings Invalid token or email.”

Any ideas appreciated!

I am also getting this problem.

I had this issue, fixed it by updating the account email address and Cloudflare API Key field.

Hi, has anyone got an answer for this? I was getting this message…

“CloudFlare plugin detected. We recommend removing the plugin as it offers no additional capabilities when W3 Total Cache is installed. This message will disappear when CloudFlare is removed.”

…so I deactivated the CloudFlare plugin. I then immediately got the “Unable to communicate with CloudFlare API: Setting: minify Unknown token or email” message.

I reactivated the supposedly unneccessary CloudFlare plugin to see if the message would go away. Which now leaves me with both messages and no idea what’s going on!

Can I ignore the “Unable to communicate….” message, or does it mean there is indeed something wrong with my CloudFlare set-up?

Any help would be much appreciated. Thanks!

@tgdtgd

There are cases of the error coming up but the setup still working fine but also cases when the setup is really broken.

To see which of the two you are experiencing:

1) Run a Page Speed and YSlow test.

2) Now go to your Cloudflare panel, click the “Gear shaped” button all to the right of the relevant website of yours. Select “Pause Cloudflare”.

There are other ways (like using direct.your domain.com etc.) but this one is the easiest.

3) Repeat the tests. If they are worse, then you are just experiencing a message display issue. If they are the same, your setup is not working. You might try and create a new Cloudflare API key and enter that in W3 TC but there may be adverse consequences on your other websites at doing that. You’ll have to put that API in each of them and some might stop working.

OK, this is my opinion: why disable official cloudflare plugin and use integrated W3 Total Cache support to it?

IMHO is not necessary. The official cloudflare plugin work fine and is up to date with latest features developed directly from cloudflare team.

W3 Total Cache support implement only cloudflare API, but developed from third part person, not cloudflare team.

This is my personal opinion and i have disabled W3 Total Cache support, using only offical cloudflare plugin, because i have conflict with another plugin Bad Behaviour.

If W3 Total Cache cloudflare support is enabled and official cloudflare plugin is not enabled Bad Behaviour failed IP, i have correctly configured reverse proxy on Bad Behaviour, and maliciuos IP was not recognized and blocked. Witout W3 Total Cache cloudflare support and official cloudflare plugin active all word fine!

Another issue is cleaning cache with W3 Total Cache cloudflare support enabled: when W3 Total Cache clean your caching (defaul 1 hour) also cleaning cloudflare cache. This is not good! Cloudflare work as CDN and not as caching. Cleaning recoursively (1hour) is not the way for best CDN performances. Cloudflare rebuild your files, after one cache cleaning, on 24/48 hours. If you cleaning it 1 hour recoursively put cloudflare cache on MISS status!

I have write to cloudflare team and your reply is that W3 Total Cache cloudflare support is not assisted and supported from cloudflare team.

My best configuration now is:

W3 Total Cache: browser cache, basic caching and basic html minify enabled. All other function disabled. All my public js, css, have manually minified and compressed, and also all public graphics files was manually compressed, and separately served directly from cloudflare CDN and not from W3 Total Cache! I have also setting Object Caching APC to work with third party plugin: i use APC CACHING PLUGIN SEPARATELY from W3 Total Cache … I have testing it on somes cheap hosting (shared, vps, cloud, dedicated) and for me is best config for all situations; db caching have troubles issues on shared hosting (slowness) and enhanced disk caching failed and annoyng me to configure on same host with multiple sites or with WordPress multisite.

Cloudflare plugin enabled. (work fine!)

Bad Behaviour enabled with reverse cloudflare config support enabled. (work fine!)

Test your own if W3 Total Cache cloudflare support work: on your statistic if your IP are only original cloudflare IP cloudflare support not work, but if IP on your statistic was translated with original IP cloudflare support work.

??