Cloud Flare - Block spam, proxies, cyber attacks, and most unwanted cyber bots

Originally Posted by Octavius.

I had to stop using cloudflare on my main forum because it would make my pages unavailable often. It was very annoying. I got it working on another site but people rarely visit that one so it's all good.

How was it making the pages unavailable? It is very important to make sure requests from CloudFlare aren't being blocked or limited at the hosting provider or server level.

[Lee G]

Im looking at using cloudflare on my forum.
What settings are you guys using that use it?
Best and optimal performance

So far the only thing you need to edit is one file from what I have read, if you run a 3.8 forum

On my low level, static page, websites, so far it looks good with limited testing

"So far the only thing you need to edit is one file from what I have read, if you run a 3.8 forum"

More than happy to answer any questions about CloudFlare. You do want to make that change if you want original visitor IP returned to you & this is actually kind of important because all visitors would like our IPs without making that change to VB (which can impact a variety of things, including the ability to block by IP).

Some helpful tips:
CloudFlare and forums
Tips for new users

[Princeton]

please keep support for cloudflare off of vbulletin.org

[forum4]

Sorry to bring up an old thread, but back to topic. I've been using Cloudfare, and all I had to do was edit that one file. Everything else went smooth.

I read MaxCDN wasn't so fast in Europe, so I didn't sign up for their free offer when I bought vBseo. I hadn't really thought much about a CDN until checking into it further. Having no interest in paying for something that I could have gotten for free, I went with Cloudfare. All seems fine so far.

[Max Taxable]

Originally Posted by forum4

Sorry to bring up an old thread, but back to topic. I've been using Cloudfare, and all I had to do was edit that one file. Everything else went smooth.

I read MaxCDN wasn't so fast in Europe, so I didn't sign up for their free offer when I bought vBseo. I hadn't really thought much about a CDN until checking into it further. Having no interest in paying for something that I could have gotten for free, I went with Cloudfare. All seems fine so far.

It's been working well for me too. I do fear however, that it won't stay free.

Originally Posted by Max Taxable

It's been working well for me too. I do fear however, that it won't stay free.

We always plan to offer a free service. We have other ways of monetizing the service (features, apps) so we can offer free services.

--------------- Added [DATE]1332354882[/DATE] at [TIME]1332354882[/TIME] ---------------

Originally Posted by Princeton

please keep support for cloudflare off of vbulletin.org

Sorry, I'm not trying to spammy at all (just addressing specific issues relative to CloudFlare so you don't have to). Drop me a line, if you wish (just saw the above post).

[tafreeh]

OKay, Imma give it a shot. I m using vb4* DO I still need to edit that file with same code ?

[forum4]

I did notice that I have to bypass Cloudflare to get to the cpanel, and that's kind of a pain.

Plus, my Living Avatars won't work anymore as it's not picking up the cookie or something. It just kept saying I had to log into the forum, which I already was. It kind of reminded me about the cpanel issue. If you don't bypass Cloudlfare, it will keep making you log in over and over.

I know there are issues about chat as well. The recommendation was to install the chat on a subdomain, which I don't think we can do with Living Avatars.

Update: Totally not using Cloudflare anymore. For some odd reason vbseo changes the url of the sigpic, and Cloudflare can't find it when it's turned on. That and I don't think there's a way to use it with Living Avatars...bummer. Having to log in over and over was another annoyance.

[final kaoss]

Just one thing to note, rocketloader & the vb4 ckeditor do not play nicely. When enabled, the toolbars for the editor fail to load. Disable rocketloader, leave the page & reload the editor, voila, working again.