New Lemmy version doesn't federate outbound with non-Lemmy instances anymore (issue from GitHub)
New Lemmy version doesn't federate outbound with non-Lemmy instances anymore (issue from GitHub)
Requirements Is this a bug report? For questions or discussions use https://lemmy.ml/c/lemmy_support Did you check to see if this issue already exists? Is this only a single bug? Do not put multipl...
![[Bug]: Lemmy 0.18.0 no longer federates outbound with non-Lemmy instances · Issue #3354 · LemmyNet/lemmy](https://lemmy.blahaj.zone/pictrs/image/4aMFJPtFZV.png?format=webp&thumbnail=256)
This is probably related to my post from a few days ago: https://kbin.social/m/kbinMeta/t/131241/What-s-up-with-The-magazine-from-the-federated-server-may
Actually there is now a fix, https://github.com/LemmyNet/lemmy-ansible/pull/114
But it seems that instances that update to the latest RC do not just automatically get that fix into their nginx config. I have worked with a instance owner and he had to, despite updating, manually update the config. After that federation worked again.Ah. Thanks for the update! Hope it resolves
Isn't this fixed in 0.18.1 iirc?
It continues to be a problem as far as I can see
That's already and old version.
Using Memmy, I see all kbin communities as empty, even though I subscribed to them using a Lemmy account and there have been posts since.
Is that a thing that’s going to be fixed in the future, or did Lemmy decide to partially defederate from kbin and all is working as intended?
I really don’t get current Lemmy—kbin relationship and what to expect in the future.