Hi Ben,
Sorry for the late response, I just got back from out of town.
Regarding Cloudflare, I wish I could help but I have never used it. If you wanted to troubleshoot, I could maybe outline a few steps you could try, but the easiest thing to do would be deactivate the plugin to ensure nothing from Cloudflare is blocked.
Hi Jeff
No problem, we all need weekends off!
At the moment, I’ve “Paused” Cloudflare, and kept BBQ active.
That resolves the 522 Error issues for Google
I was wondering if the Pro version of BBQ – which I think allows whitelisting IP addresses – might solve the problem.
What do you think?
Cheers
Ben
Hi Ben,
Actually whitelisting IPs is a feature that I’ll be adding this week to the next version of BBQ Pro, so it should be available very soon. And yes I think that should resolve the issue (and give you better protection as well).
I’ll follow-up on this thread when the new version is available.
Thanks Jeff, much appreciated
Hi;
I work for CloudFlare, so maybe I can help. In order to ensure your IP is being recorded accurately within CloudFlare my recommendation would be to install Mod_Cloudflare on your server.
This will ensure that CloudFlare and Apache will play nicely together, whether it comes to IP Address logging, accurate IP address detection or Flexible SSL. A lot of webhosts have this pre-installed.
Hi Ben,
Just to follow up with this, IP-whitelisting is now an included feature of BBQ Pro (as of v1.5). Should be released within the next couple of days. Thanks for the feedback on this.