Oh no... it sure would be terrible if this problem couldnโt be solvedโฆ
this post was submitted on 19 Nov 2024
110 points (98.2% liked)
Lemmy.World Announcements
29066 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 [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
Do these things usually happen from time to time?
I've noticed some lemmy.ml communities looking surprisingly "dead" some days here and there but not thought much of it.
I wouldn't say usually, but they can happen from time to time for a variety of reasons.
It can be caused by overly aggressive WAF (web application firewall) configurations, proxy server misconfigurations, bugs in Lemmy and probably some more.
Proxy server misconfiguration is a common one we've seen other instances have issues with from time to time, especially when it works between Lemmy instances but e.g. Mastodon -> Lemmy not working properly, as the proxy configuration would only be specifically matching Lemmys behavior rather than spec-compliant requests.
Overly aggressive WAF configurations tend to usually being a result of instances being attacked/overloaded either by DDoS or aggressive AI service crawlers.
Usually, when there are no configuration changes on either side, issues like this don't just show up randomly.
In this case, while there was a change on the lemmy.ml side and we don't believe a change on our side fell into the time this started happening (we don't have the exact date for when the underlying issue started happening), while the behavior on the sending side might have changed with the Lemmy update, and other instances might just randomly not be affected. We currently believe that this is likely just exposing an issue on our end that already existed prior to changes on lemmy.ml, except the specific logic was previously not used.
this comment section is not a place to rant about other instances
Yeah a swept clean comment section looks way better....
Ah, I just today in the morning blocked Lemmy.ml. Seems to have been interesting timing :)
I've never had a positive interaction with Lemmy.ml. For me it serves as a quarantine space, and a set of pre-tagged users I don't personally enjoy dealing with.
...and I'm not particularly averse to Marxists sentiments either, but they're certainly not good sales people, diplomats, or representative of their cause.
Which is just part of their reputation now. Having a bad experience with a .ml user seems to be part of the lemmy experience. It's kind of comical how consistent it seems.
That said, I'm sure there's good people on .ml.
Yeah, just avoid politics there and it's fine. We all know about their zeal so it's pointless to discuss it.
So it's your fault!
In which case, thank you.
No one said it was a global variable. You can hardly blame the user for poor documentation.
Could it be an issue/compatibility with lemmy.ml running Lemmy v0.19.7 ?
I don't believe it is.
There weren't any network related changes from 0.19.6 to 0.19.7 and we haven't seen this behavior with any of the 0.19.6 instances yet.
The requests are visible with details (domain, path, headers) in Cloudflare, but they're not showing on our proxy server logs at all.
I've read enough posts over at /r/sysadmin, it is always DNS.
