The db is like the holy grail for a lemmy instance. Heavily backed up and fortified. :)
I dont think so since the traffic came from China and came from 951,466 unique ips. :)
Alright, https://old.lemmy.today/ is back up, as well as the other alternative user interfaces mentioned in the sidebar.
I have blocked more chinese ip ranges found in the log files, so hopefully it helps.
I think we are unfortunantly heading in that direction of blocking more and more of them...
And no, no mandarin user base. :)
Yeah its very common. Some instances block the entire Chinese internet for this reason...
We have some alternative user interfaces that you can use when you use the browser (info in the sidebar). But now they are down temporarily. :)
Done! We are now on latest. :)
We have been on hetzner for years at this point and had no problems. Not sure what content would be censored here. Its just memes and discussions.
They will, unfortunately. I hate these things but I know that as soon as influencers make them cool, the shame will go away.
I really want to be wrong about this.
I was fixing one thing today with old.lemmy.today but it shouldnt affect lemmy.today.
old.lemmy.today was putting all visitors under the same IP so lemmy was rate limiting everyone randomly who used old.lemmy.today. But that is fixed today. It doesnt sound like the same thing as your problem though, unless lemmy.today was also overloaded because of its rate limiting old.lemmy.today.
We will see if you get the same thing today then!
It works! I discovered way too late that lemmy was rate limiting traffic from mlmym, because it wasnt part of my nginx config. It was lemmy itself that was doing rate limiting since all requests came from the same docker ip.
But forwarding the real ip headers fixed that, so very good. Huge thanks!















