Lemmy.World Announcements

28915 readers

4 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to [email protected] e-mail.

Report contact

DM https://lemmy.world/u/lwreport
Email [email protected] (PGP Supported)

Donations 💗

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Join the team

founded 1 year ago

MODERATORS

[email protected]

2103

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

submitted 1 year ago by [email protected] to c/[email protected]

424 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

[–] [email protected] 7 points 1 year ago (6 children)

You should change the public IP of the server if you haven't already

[–] [email protected] 1 points 1 year ago (5 children)

What happens tomorrow? Change the IP again? And again? It's not a long term solution.

[–] [email protected] 17 points 1 year ago* (last edited 1 year ago) (3 children)

They mean after adding a ddos mitigation like cloudflare, you should rotate the origin server IP so the origin server's IP is no longer publicly known and thus not directly reachable by ddos attackers. The only way to now interact with the application is though Cloudflare's network. You should only have to do this once as long as the origin IP doesn't publicly leak.

Another step would be to add firewall rules to only allow inbound traffic from cloudflare IPs: https://www.cloudflare.com/ips/

[–] [email protected] 2 points 1 year ago (1 children)

I recall a certain amount of overhead in IPTables "allow only from" situations but I'm not sure whether it's enough to make a DDOS any kind of viable on a server in this configuration.

Do you happen to know how effective the strategy is?

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

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

[–] [email protected] 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.

load more comments (1 replies)

load more comments (2 replies)