[Krew]

Damnit, that sucks. Would you advise other webmasters to use Sucuri over CloudFlare as well? I assume you would since Cloudflare has clearly been lacking.

[Gook]

Is there no other option then cloudflare/Sucuri for you?
How can such a big company let something like this happend, its a serious "bug/exploit"

Are all attacks to HF done like this?

[Krew]

*ignored

Anyway, I am getting this more than often & results in page freezes.
https://imgur.com/BPczxbI

[Milk™]

Important to spend time with your family ofc. But I'm so thankful that you made this community :)

[+One]

As xadamx said, you're really working hard to improve the website. This will also make it easier for you to maintain the website at its best. Cheers 🤝

[Abraham Lincoln]

Are you still planning on using the Google service or is that a entirely different topic?

I think that's a different topic. That requires a time to get added to the program, while right now he's just looking for instant protection.

[Gяαη∂тнεfтнσяsε]

If you ask me, you should ditch C.F. completely. I'm not a big web dev but I'm fairly sure you can just copy the files from CF over to a vps with great specs and great ddos protection and staff that actually give a Fuck about what they're doing.

[Joshz]

I received an nginx 405 not allowed error today for around 2 minutes while attempting to pm someone. It's a new error I haven't seen before, only happened once. The regular reported error has happened less but still occasionally.

I don't know much about website protection. That said, maybe consider using something other than cloud flare? They really are quite incompetent.

[Gяαη∂тнεfтнσяsε]

😠

😧

🤫

🙃

🤦‍♂

That was my reaction in smiley version.

I specialize in full retard.

[Repeat]

I am happy that you didn't destroy the website. 😉

[Gяαη∂тнεfтнσяsε]

oh god did you just make all of that up to appear like you had a valid opinion on this subject?
--
oh and i'm slightly confused, the problem is mostly fixed now?

I made that up because I'm stupid

[Repeat]

Have you tried politely asking them to stop the DDoS?

['An0ny]

CloudFlare have been working fine till now, this exploit & the other cf bypass are both working fine to bypass CloudFlare. But there are some rules you could do to prevent it, which hes doing now.

I am using CloudFlare free fine, i think PRO would be more than enough as they've also increased the r/s limit.

['An0ny]

How I'm currently setup the bypass is effective. I relay that info in the first post. The amount of traffic hitting Apache chokes it. So ANY suggestion to use .htaccess or any Apache based rule will not be effective. I've tried to make that clear and people still send me the suggestion.

I think what you are doing now should be fine, hopefully CloudFlare will prevent this. I think that white page / cookie check is annoying people, but i'd rather see a white page here and there than downtime.

Any certain reason you are using Apache? I've had nothing but issues with Apache when getting attacks. It kills it easily. I am using plain nginx my self, and set up my own rule(s) to prevent it which so far seems to work.

['An0ny]

Someone probably hasn't hit your site with a big enough botnet then, Cloudflare Free wont protect your site with that much traffic with or without the exploit.

CloudFlare free or pro or business has no difference if this exploit is out. So I don't understand your statement.