Would it be possible to have an option to utilize your CDN service without the spam protection?
I'd like to be able to get my traffic without interference from the bot prevention tools.The performance and security options for CloudFlare kind of go hand-in-hand (think fewer requests from potentially bad visitors=less bandwidth/requests).
What you could do, however, is change your security settings to "Essentially Off" in your CloudFlare settings (settings->CloudFlare settings) so only the really bad folks are challenged. You can also do some things in CloudFlare's Threat Control Panel to override our behavior.
What would you like to see? Something like: Block exploit attackers only?
I'd like to be able to get my traffic without interference from the bot prevention tools.
I have my own spam prevention service, and as you say, you folks aren't set up to prevent DDoS anyway.
Also (since I have your ear), would it be possible to have images which are uploaded immediately recached, since those images have to go through your servers to be stored on the remote server?
I figured there should be some way to tell that a file is being uploaded, then just recache that file if it's an image. As it is, scripts that overwrite one image with another don't have their images recached right away and it is a bit inconvenient.
I can think of a couple possibilities, but as for the actual mechanics of it, certainly not.Totally game to see how you would like to see this work. Since we don't cache *everything*, any feedback about how we can make it faster/better is much appreciated.
I gave up on cloudflare today. When I installed it, it really did make the website a bit snappier, but it just seemed that there were always server issues somewhere in their network. I received a lot of complaints from usersstating they were looking at the "website offline" notice (while i'm surfing fine from my location). The reliability hit just wasn't worth it for the mild performance gain I received. I did submit a ticket, and then another one. I got a response a couple days later. I think cloudflare has potential, but it isn't quite there yet.
Did you add mod_cloudflare? It could be the server blocking cloudflare IPs, I used to get the site offline error back when I first started to use CloudFlare but those errors have since disappeared(probably due to the fact that they keep on improving the QoS.I gave up on cloudflare today. When I installed it, it really did make the website a bit snappier, but it just seemed that there were always server issues somewhere in their network. I received a lot of complaints from usersstating they were looking at the "website offline" notice (while i'm surfing fine from my location). The reliability hit just wasn't worth it for the mild performance gain I received. I did submit a ticket, and then another one. I got a response a couple days later. I think cloudflare has potential, but it isn't quite there yet.
I gave up on cloudflare today. When I installed it, it really did make the website a bit snappier, but it just seemed that there were always server issues somewhere in their network. I received a lot of complaints from usersstating they were looking at the "website offline" notice (while i'm surfing fine from my location). The reliability hit just wasn't worth it for the mild performance gain I received. I did submit a ticket, and then another one. I got a response a couple days later. I think cloudflare has potential, but it isn't quite there yet.
Interesting, I haven't come across this issue yet. There doesn't seem to be server issues from what I can see on the status board.
My host has got a CloudFare link the cPanel and I did get an email for it as well. I have signed up but I haven't seen much of an improvement but it also hasn't slowed down my site loading time. I have static content on my site that would benefit from the cloudfare service should my host go down, because our shoutcast server would still run so people would still be able to tune in!
I was not using mod_cloudflare, but instead using the xenforo edits. Like I mentioned, it did make the website slightly faster, but it seems one of the datacenters always had an issue. The response and time to respond to my ticket was not quite as good as I would have hoped... maybe support for paying members is better.The site offline error message only appears in two circumstances:
1. Your server is actually having issues.
2. Your host or server is blocking connections from our IPs because of rules. Things to check:
Tips to ensure CloudFlare's IPs are accepted by your server If your server origin is online, then: 1) Make sure that you're not blocking CloudFlare IPs in .htaccess, iptables , or your firewall. 2) Make sure your hosting provider isn't rate limiting or blocking IP requests from the CloudFlare IPs and ask them to whitelist the IP addresses below:
• 204.93.240.0/24 (204.93.240.0 - 204.93.240.255) • 204.93.177.0/24 (204.93.177.0 - 204.93.177.255) • 199.27.128.0/21 (199.27.128.0 - 199.27.135.255) • 173.245.48.0/20 (173.245.48.0 - 173.245.63.255) • 103.22.200.0/22 (103.22.200.0 - 103.22.203.255) • 141.101.64.0/18 (141.101.64.0 - 141.101.127.255)
Also: I strongly recommend installing mod_cloudflare (or equivalent) to make sure original visitor IP is getting passed to your server.
If hosts see a bunch of requests from our IPs, which would be the case if you didn't see the original visitor IP because we're acting as
a reverse proxy, they might start blocking requests from those IPs.
I was not using mod_cloudflare, but instead using the xenforo edits. Like I mentioned, it did make the website slightly faster, but it seems one of the datacenters always had an issue. The response and time to respond to my ticket was not quite as good as I would have hoped... maybe support for paying members is better.
its not feasible to do that with xf uploads. besides, that would defeat the entire point of the waf as it would open an attack vector.Uploads can trigger the WAF. Options:
Turn WAF off or whitelist the IP address.
Create a subdomain for uploads & then add the subdomain so we don't proxy it.
those hitting the dataserver are the ones to complain, and if there are always problems with a datacenter then i am always fielding complaints and being asked to troubleshoot something that is out of my depth; networking.One thing to keep in mind is that an issue in one datacenter doesn't mean all of your site visitors are having issues (only those hitting that datacenter). And we generally resolve most datacenter issues very quickly.
We use essential cookies to make this site work, and optional cookies to enhance your experience.