2313

Lemmy.world update: Downtime today / Cloudflare (lemmy.world)

submitted 1 year ago by ruud@lemmy.world to c/lemmyworld@lemmy.world

376 comments fedilink hide all child comments

Today, like the past few days, we have had some downtime. Apparently some script kids are enjoying themselves by targeting our server (and others). Sorry for the inconvenience.

Most of these 'attacks' are targeted at the database, but some are more ddos-like and can be mitigated by using a CDN. Some other Lemmy servers are using Cloudflare, so we know that works. Therefore we have chosen Cloudflare as CDN / DDOS protection platform for now. We will look into other options, but we needed something to be implemented asap.

For the other attacks, we are using them to investigate and implement measures like rate limiting etc.

you are viewing a single comment's thread
view the rest of the comments

[-] nuke@yah.lol 3 points 1 year ago* (last edited 1 year ago)

If your origin servers IP is never revealed then all traffic goes through cloudflare regardless. Firewall restricting the IPs is just good practice since cloudflare is the only IP that is supposed to talk to that server anyway, but it's not a requirement.

I can see some overhead if you're maintaining a large blacklist, but I don't see it happening with a small whitelist and default inbound DROP

[-] gerbilOFdoom@lemmy.world 2 points 1 year ago

Oh absolutely, I agree with the best practice! I just didn't know the real world efficacy of dropping packets near the NIC to mitigate DDOS load. There is certainly a performance limit but where that limit exists has been nebulous for me.