We’re aware of ongoing federation issues for activities being sent to us by lemmy.ml.
We’re currently working on the issue, but we don’t have an ETA right now.
Cloudflare is reporting 520 - Origin Error when lemmy.ml is trying to send us activities, but the requests don’t seem to properly arrive on our proxy server. This is working fine for federation with all other instances so far, but we have seen a few more requests not related to activity sending that seem to occasionally report the same error.
Right now we’re about 1.25 days behind lemmy.ml.
You can still manually resolve posts in lemmy.ml communities or comments by lemmy.ml users in our communities to make them show up here without waiting for federation, but this obviously is not something that will replace regular federation.
We’ll update this post when there is any new information available.
Update: Federation is resumed and we’re down to less than 5 hours lag, the remainder should be caught up soon.
The root cause is still not identified unfortunately.
You must log in or # to comment.
Removed by mod
Unfortunately not entirely true. They have the largest Linux Community. To be precise, the big one.
ProgrammerHumor is there as well. The Open Source and Privacy communties are very bigs as well there. Completely dwaring their .world counterpart.
I’m not a fan of .ml either but you can’t deny that they have this 3 parts (which very much represent the ideals behind lemmy) covered very well.
The fact of a community being big doesn’t mean that it is good.
I’m out of the loop. is there some post or link you can send me about . ml being malicious
It’s a constant problem on the fediverse, if you search for things like lemmy.ml and CCP, propaganda, censoring etc it’ll get you started.
Hexbear.net and lemmygrad.ml are even worse.
thanks. that’s pretty clear cut
Yeah. If anything the situation has become worse since that time. I was banned from the entire instance for a frank if somewhat critical discussion of Chinese history, even as I was trying to avoid contemporary politics because I knew that would get me in trouble.
Anything other than fawning praise of the Chinese government is labeled racism and results in a ban.
this comment section is not a place to rant about other instances
I don’t see why not.
Yeah a swept clean comment section looks way better…
Removed by mod
I can think of a solution.
Ah, I just today in the morning blocked Lemmy.ml. Seems to have been interesting timing :)
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.
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.
Is there a reason people seem to not like .ml? I only joined because it said the instance was for FOSS enthusiasts
Removed by mod
Lol, flagged as inappropriate 🤣
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.
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Removed by mod
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.
Removed by mod
FWIW the communities on walledgarden.xyz have been having federation issues to lemmy.ml for a few days as well.
Since we were/are working through some things with our host I didn’t want to bother anyone from lemmy.ml about it, but it’s a thing. AFAIK federation is otherwise working normally.
Good luck getting it figured out and resolved!
This probably should explain: https://lemmy.world/post/22166289
Lemm.ee is not loading at all, giving a 503 error. Possibly related?
I doubt it
