motowebmaster
Well-known member
I use CloudFlare on my sites.
As previously suggested, I too keep the security settings low - and the caching aggressive. On CF-Free's normal security settings, some valid corporate proxy servers were being blocked; users couldn't gain access at from their work environments (like motorcycle gab has a place in work
). On the low security setting, there haven't been any complaints. My XF site is being supported by the free version of Cloudflare along with a few other domains, but I have a vb3 and a IPB site that are on CloudFlare Pro. My primary motivation for doing the Pro version was give a growing site more resources. My traffic has increased since the change to Cloudflare, as well as my ad revenue. It appears to have increased further since the upgrade to Pro on the two domains, but am still waiting on more data to confirm.
I don't use many of the added features of Cloudflare, but am interested in features currently in beta. They worked well with Chrome and Firefox, but IE didn't like them. My tests of these features didn't involve my XF site.
If you try it, disable all features except basic security (low) and caching (basic or aggressive - whatever works for you). Then work from there and enable features individually after you're accustomed. If you're using a forum feature that serves content from another provider, I'd recommend that you change it back to being served your own host and let Cloudflare pick that up as well (it improved my user's experience). I don't enable Cloudflare on mail, or my ad server.
If you rely on actual user IP addresses, there are some steps you'll need to take, otherwise you'll see Cloudflare network IPs for every user.
For some, a straightforward CDN may be the better solution, but I like the way Cloudflare works.
As previously suggested, I too keep the security settings low - and the caching aggressive. On CF-Free's normal security settings, some valid corporate proxy servers were being blocked; users couldn't gain access at from their work environments (like motorcycle gab has a place in work
). On the low security setting, there haven't been any complaints. My XF site is being supported by the free version of Cloudflare along with a few other domains, but I have a vb3 and a IPB site that are on CloudFlare Pro. My primary motivation for doing the Pro version was give a growing site more resources. My traffic has increased since the change to Cloudflare, as well as my ad revenue. It appears to have increased further since the upgrade to Pro on the two domains, but am still waiting on more data to confirm.I don't use many of the added features of Cloudflare, but am interested in features currently in beta. They worked well with Chrome and Firefox, but IE didn't like them. My tests of these features didn't involve my XF site.
If you try it, disable all features except basic security (low) and caching (basic or aggressive - whatever works for you). Then work from there and enable features individually after you're accustomed. If you're using a forum feature that serves content from another provider, I'd recommend that you change it back to being served your own host and let Cloudflare pick that up as well (it improved my user's experience). I don't enable Cloudflare on mail, or my ad server.
If you rely on actual user IP addresses, there are some steps you'll need to take, otherwise you'll see Cloudflare network IPs for every user.
For some, a straightforward CDN may be the better solution, but I like the way Cloudflare works.
That's one of the reasons why we challenge visitors that are probably infected & prevent them with options to clean up with an AV product.
