Images can be incredibly costly to page load times; fortunately, Cloudflare can dramatically help improve image load times. You can find these features in the Speed app of the Cloudflare dashboard.
Plugin Support
Velda
(@supernovia)
Thread Starter
vipini
(@vipini)
You’re welcome to use Jetpack and Cloudflare together if you’d like:
https://jetpack.com/support/getting-started-with-jetpack/configure-jetpack-cloudflare/
Should we still disable cloudflare for wp-admin??
I will always and forever recommend disabling all caching systems in wp-admin, and that includes Cloudflare.
When you’re working in your admin, you want the latest information at your finger tips at all times, and you don’t want to be constantly questioning whether or not you’re seeing old cached data.
Thread Starter
vipini
(@vipini)
I will always and forever recommend disabling all caching systems in wp-admin, and that includes Cloudflare.
When you’re working in your admin, you want the latest information at your finger tips at all times, and you don’t want to be constantly questioning whether or not you’re seeing old cached data.
so only disabling cache option for wp-admin only , not other features , right?
Plugin Support
Velda
(@supernovia)
Yup. You’ll want to exclude your wp-admin, and ensure you’re using the Cloudflare SSL, as we recommend here:
https://jetpack.com/support/getting-started-with-jetpack/configure-jetpack-cloudflare/
Thread Starter
vipini
(@vipini)
Ok i think no need to disable security for wp-admin via cloudflare but other disablings are ok.
Let us know how that goes, but experience tells me you’ll still need to whitelist /wp-admin/ in Cloudflare.
Your security protections for wp-admin include your username/password login and Jetpack’s security features which protect against brute force attacks: https://jetpack.com/support/security-features/
If nothing bad can get in, nothing bad can be done.
Over time, you’ll notice Cloudflare’s “protection” interfering with how you work in your Dashboard more than anything else that it does.
Thread Starter
vipini
(@vipini)
I see is jetpack login protection conflicts with wordfence and s2member plugins when used together?
I’m not specifically aware of that, but it’s easy to switch off if you do run into a problem.
Please give it a try and let us know what errors you do encounter (if any).
Thread Starter
vipini
(@vipini)
the most seen problem on jetpack login prot.(along with wordfence&s2member) is : if somebody(real legitimate person) tries many login attempts then jetpack blocks their ip and website operator wont know if the person is banned by jetpack or not.
I think jetpack should show which legitimate users banned by login protection.
Because its really hard to know which banned ip belong to which user.
Ah, that makes sense. I believe that Wordfence has logging for that, but if Jetpack blocks them before Wordfence, then there’s no way for Wordfence to know anything happened.
If you’re happy with Wordfence’s protection of that, then I recommend switching off “Block suspicious-looking sign in activity” at Jetpack > Settings > Security in your site’s Dashboard.
Thread Starter
vipini
(@vipini)
James Huff, which protection is stronger? wordfence or jetpack?
