[Plugin: W3 Total Cache] unable to make cloudflare api request (CloudFlare/W3TC)

Hi,

“ANyway, in trying to connect W3TC with CloudFlare, I keep getting the ‘unable to make cloudflare API request’ error message.”

And you have your CloudFlare API key established, etc.?

Note: You really don’t need to have CloudFlare’s plugin active if you’re using W3TC’s.

Yup, I have my API established. In the cloudflare plugin, it took just fine.

I disabled the cloudflare plugin to see if it made a difference. I still get the same error as above.

If I have minify on through cloudflare for all 3 types, should I be noticing any difference in my source? Nothing looks different

I have the same message, always have. Never have been able to get this to work.

This will probably be hard to troubleshoot directly on the forums. Can you please contact us so we can have the engineer that developed the plugin check it out? We would need to know the domain(s) you’re having an issue with.

Contact CloudFlare

Here’s what our engineer thinks is happening:

The hosting providers are probably blocking php from
being able to make outgoing api calls. This is a security setting
sometimes turned on. A solution would be to use javascript to make the
calls, but this would require a re-write of the cf integration for the W3TC plugin by the author.

OK, let me ask you this; outside of the ability to change a couple of CF settings, is there anything else that the CloudFlare section in W3TC actually does? I already have the CloudFlare plugin installed, so am I really missing anything by not being able to make a CF API request via the W3TC panel?

Similar issue here. However, W3TC only provides three options for the CloudFlare Security Level setting, High, Medium, Low. CloudFlare, on the other hand, provides a fourth setting: Essentially Off.

Only when I set it to “High” inside W3TC is it able to save the setting and can successfully make an API request. Do I set it to Medium or Low, however, it won’t work and keeps displaying the red “unable to make cloudflare API request” message.

Hosting provider is mediatemple, so they shouldn’t be the issue either.

I resolved my issue by leaving godaddy! Everything works perfectly on bluehost. So, it could most definitely be host related

Hmmm, I just switched hosts too, to a new managed VPS, but the problem remains.

There’s gotta be some sort of underlying server setting or something… wish I knew enough to figure out what’s different for me that made it work

I’m having this same issue. As a cloudflare noob, i think I want to go with a medium security setting and then adjust from there, but this simply isn’t possible to change in the w3 setting.

If i change it directly on the cloudflare site, does this override the w3 setting?

Thanks.

I am also on Godaddy linux plan – php 5 – W3 0.9.2.4 – With the CloudFlare plugin and I can only save with high security level.

Why is this?

Hi,

“If i change it directly on the cloudflare site, does this override the w3 setting? “

Yes, it should.

“With the CloudFlare plugin and I can only save with high security level.”
Not sure. Our API developer would need to look into this. Again, we think that there is some sort of limiting happening on the hosting side that is contributing to this:( If you would like to send more details, please send them here: https://support.cloudflare.com/cgi/discussion/new

If you can’t do it via the plugin, I would recommend logging into your CloudFlare account as an option.

I am also on Godaddy linux plan – php 5 – W3 0.9.2.4 – With the CloudFlare plugin and I can only save with high security level.

Why is this?

Because it’s godaddy! Seriously though, certain things just wouldn’t work for me on godaddy regarding w3tc, and also cloudflare’s plugin, or cloudflare as part of w3tc. Luckily you can just set your security setting from your cloudflare panel. I don’t know what it is on godaddy that interferes, but after switching it went away. SO I have to guess that hosting configuration was the issue

Have the same issue, W3TC only works with High setting. Anyway, if it will be overridden by Cloudflare, then great.