Earlier quoted context omitted.
Which is why you mirror your small blog across multiple networks. Use Tor, I2P, etc. Most blogs are git repos so it's very easy to distribute it
How does one "mirror using Tor" (which is a network, not a file hosting service)?
Do not put your site behind Cloudflare if you don't need to
231–240 of 391 posts
Re: Do not put your site behind Cloudflare if you don't need to
#232Earlier quoted context omitted.
> I'm not too worried about someone DDOSing my personal site. Yeah, they could do it. And then what? Who cares? Have you experienced a targeted DDoS attack on your personal site? I have. I too had this attitude like yours when I didn't know how nasty targeted DDoS attacks can get. If you're not too worried about someone DDoSing your personal site, then your host taking your website down and then you having to run cir…
You keep saying stuff like "the fallout" and "the repercussions" but then the only example you can provide is talking to customer service to bring your stuff back online. Is that it? Honestly speaking, not being sarcastic at all.
Re: Do not put your site behind Cloudflare if you don't need to
#233Cloudflare is still down and now its been 5+ hours. Having said that, the thing about "if you don't need to" is not that simple. FOr personal sites/blogs, I can agree but then it really doesnt matter for those. For a real business, the value of cloudflare (As centralized as it gets) is the proxy especially against attacks. The other stuff like CDN/Caching etc are bonus on top. Unless there is a better option, just as…
Re: Do not put your site behind Cloudflare if you don't need to
#234The lesson I learned is it's OK to put your site with Cloudflare. It's not ok to put your DNS on a registrar who is also on Cloudflare. We got locked out because our registrar is also on Cloudlfare, and now I can't even switch DNS to get the site back up. Keep your domain name registrar, DNS service provider and application infrastructure provider separately.
This works up until you discover that your domain registrar and dns provider are all using cloudflare to protect their websites.
Re: Do not put your site behind Cloudflare if you don't need to
#235I get constantly attacked. Usually it's big actors like Facebook, Azure and OpenAI who bombard my servers without any respect or logic. I need to update my access rules constantly to keep them away (using Cloudflare) Sometimes it's clustered traffic, more classic DDoS, from China, Russia or America. That I could easily filter with the DDos protection from my hosting (which is cheaper than cloudflare anyway) What shou…
Back in 2001/2002 my personal website was “slashdotted” several times…
… which I learned about after the fact by seeing myself on slashdot.
It was not noticeable as it occurred and my services were not impacted.
So perhaps you need a p3-500 with 64 megabytes of ram and Apache 1.x and an old copy of cgi-lib.pl ?
Re: Do not put your site behind Cloudflare if you don't need to
#236> For your small blog with one hundred visitors per month, it's probably the same: "no one will burn their DDoS capabilities on you!" If this is their core argument for not using CDN, then this post sounds like a terribly bad advice. Hopes and prayers do not make a valid security strategy. Appropriate controls and defenses do. The author seems to be completely missing that it takes only a few bucks to buy DDoS as a s…
You think someone would DDoS you because you made a comment like this on HN? Seems a bit overly cautious.
Re: Do not put your site behind Cloudflare if you don't need to
#237I get constantly attacked. Usually it's big actors like Facebook, Azure and OpenAI who bombard my servers without any respect or logic. I need to update my access rules constantly to keep them away (using Cloudflare) Sometimes it's clustered traffic, more classic DDoS, from China, Russia or America. That I could easily filter with the DDos protection from my hosting (which is cheaper than cloudflare anyway) What shou…
“Hundreds of concurrent requests…” Back in 2001/2002 my personal website was “slashdotted” several times… … which I learned about after the fact by seeing myself on slashdot. It was not noticeable as it occurred and my services were not impacted. So perhaps you need a p3-500 with 64 megabytes of ram and Apache 1.x and an old copy of cgi-lib.pl ?
It seems to find the slowest endpoints (well it does like my search and category pages, but sometimes it really hammers a single page for an hour), builds up until your site goes into its knees and instead of going slower it starts to hammer from other IP ranges until you have them all banned. This can go on for hours (or days even) if I don't create new rules to ban it.
It reminds me of a slowloris dos but at large scale and concurrency.
Sure if my website didn't have any dynamic content, or not millions of database lines it would be less of an issue :)
Re: Do not put your site behind Cloudflare if you don't need to
#238Good luck with your bill if you have a DDOS attack. If they don't close your account at least.
Re: Do not put your site behind Cloudflare if you don't need to
#239Earlier quoted context omitted.
In my experience hetzner DDoS protection doesn't work
As long as the hoster doesn’t actively make things worse by disconnecting you, any further help is just a happy accident. The bar is very low.
Re: Do not put your site behind Cloudflare if you don't need to
#240Earlier quoted context omitted.
I was hoping you could share some of the factual evidence you apparently possess to make such bold claims, alas it seems my hopes will go unfulfilled. Have a good rest of the day!
Hey, s1mplicissimus, hope you are well! Dud(ett)e, it's a message board comment, not a scientific study. But do you really doubt that most ISPs will gladly disable your 1Gb/s home-slash-SMB connection for the rest of the month in face of an incoming 1Tb/s DDOS? Sure, they'll refund your €29,95, but... that's about it, and you should probably be happy they don't disconnect you permanently?