- cross-posted to:
- france@lemmy.world
- france@jlai.lu
- cross-posted to:
- france@lemmy.world
- france@jlai.lu
You must log in or register to comment.
Seems like the CloudFlare protection still isn’t enough. I feel sorry for them to have to deal with this on a Sunday
Still down for me.
Ah, seems it’s down again: http://lemmy-status.org/
Sh.itdoesnt.work
deleted by creator
My understanding (from running an instance) is that this isn’t something cloudflare is going to help with, it’s the database on these instances locking up. It happens to my and multiple other instances too, and i have monitoring from multiple sources so I get notified and can restart the server/docker containers. Improvements should come in the next lemmy versions.
Even better, so they might consider getting rid of CF at some point
I mean they’ll probably benefit from some sort of CDN, and CF being free really helps keep costs down. Are there alternatives you’d suggest?
It kind of amazes me that they’ve not been using one up until recently given their size. I’m anti-lemmy.world but I do sympathise with their technical issues.
Interesting, I assumed that CF was paid, but it seems indeed to be free for the basic tier. That’s quite amazing, actually https://lemmy.nz/comment/1118790
@Blaze @fediverse This is the natural reminder to lemmy people that they should have a few alts on different instances, just in case something like this happens.
Also just populate smaller instances instead of centralizing.
This this this
No no no… This, that, and those other ones…
:)
It would probably make more sense to suggest that more people permanently move off of lemmy.world. it’s growing too quickly. People don’t need accounts on lemmy.world to browse lemmy.world. I’m not on it and i browse it just fine. It’s heavy usage that brings it down. So setting up slts doesn’t fix the problem. It’s changing the curling wallpaper when the problem is the house is on fire. Don’t treat the symptom. It’s the fediverse. Spread out.
@pjhenry1216 @Blaze You’re not wrong that people should move to smaller instances (large instances become prone to censorship), but smaller instances do go down sometimes as well. You want to know where you’re moving to if your instance goes down, and not having a game plan for that is bad.
I always think that with every DoS, some users just create accounts on other servers, see that it’s quite faster than LW, and just keep using it. But yeah, I guess at some point LW will just close registrations.
Of course, as soon as I post, LW is back. That’s good!
Remember a lot of even the largest lemmy instances are hosted on a single vps. No redundancy, no scaling, and the admins barely know what they’re doing. Its volunteer work done as cheaply as possible.
This is true!
My instance just switched to a HA database setup :)
It seems that lemmy.one is still down.
summoning @jonah
@jonah@lemmy.ml @jonah@lemmy.jonaharagon.net @jonah@mastodon.neat.computer
It’s never “[Solved]”, LOL.
Seems to be okay at this moment: http://lemmy-status.org/
Yeah, well, it will be unsolved again and again, because that’s the nature of servers - they experience downtime. I’m just looking ahead of myself and how badly this tag will age for some, haha.
Oh, I see. Let’s say that for the day I posted the issue, it’s now solved
HTTPS not working for me on Firefox Android ☹️
Seems strange
