1801

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

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

427 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

[-] michael@lemmy.perthchat.org 10 points 1 year ago

Hmmm, we're getting a fuckload of web requests on our Lemmy too... I think I'll enable CloudFlare too! :)

[-] Da_Boom@iusearchlinux.fyi 5 points 1 year ago

Just make sure you do your research before you do - people have broken federation by enabling it without due care in the past.

[-] xavier666@lemm.ee 4 points 1 year ago

people have broken federation by enabling it without due care in the past

Any links regarding this? It sounds concerning and my instance admin uses Cloudflare as well.

[-] AphoticDev@lemmy.dbzer0.com 3 points 1 year ago

If your instance uses Cloudflare, then you have nothing to worry about, as your admin clearly has federation working. You wouldn't be posting here if they didn't.

[-] xavier666@lemm.ee 2 points 1 year ago

That seems troublesome. Is it more of an issue with Cloudflare or just improper configuration by the instance admin?

[-] AphoticDev@lemmy.dbzer0.com 2 points 1 year ago

I would assume improper configurations on the part of the admin. I've never tried setting up Lemmy, but if I had to take a wild guess people aren't configuring the SSL right and other instances aren't talking to them because the domain on the cert is wrong.