this post was submitted on 22 Jul 2023
2315 points (98.8% liked)

Lemmy.World Announcements

29079 readers
245 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 info@lemmy.world e-mail.

Report contact

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

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 2 years ago
MODERATORS
ruud@lemmy.world
lwadmin@lemmy.world
lwCET@lemmy.world
jelloeater85@lemmy.world
Serinus@lemmy.world
lw_mod_notification@lemmy.world
MrKaplan@lemmy.world
2315
Lemmy.world update: Downtime today / Cloudflare (lemmy.world)
submitted 1 year ago by ruud@lemmy.world to c/lemmyworld@lemmy.world
446 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
[โ€“] ItsMyFirstDay@lemmy.world 91 points 1 year ago (1 children)

In case you haven't considered this, some helpful advice. To keep them from the lemmy.world door after the CDN installation

  • Change the public IP addresses
  • rotate your certificates
  • block all traffic appart from the CDN and only allow a limited known good IP addresses (like yours and your support team). These steps will make your server harder to find, hopefully they move on.
[โ€“] daniyyel@lemmy.world 17 points 1 year ago (1 children)

You might have Cloudflare add a request header to the origin request, like x-cloudflare-key: <somesecret>, and then configure nginx on the server to block everything not containing that header.

[โ€“] Ocelot@lemmies.world 5 points 1 year ago

just block ingress to your server from non cloudflare IPs or use argo tunnel.