Debugging federation issues
Debugging federation issues
I've been trying to subscribe to magazines/communities from lemmy.ca.
I recall seeing on kbin.social that people were having trouble seeing communities from lemmy.ca as well, but it was attributed to the DDoS protections that were enabled. From what I can tell, fedia.io does not seem to have the same protections enabled, but I still cannot see communities from lemmy.ca (e.g. I was able to find [email protected], but not [email protected]).
On lemmy.ca, it seems like fedia.io should be federated with them.
Does anyone have any guidance on how to track down the issue? Thanks in advance!
EDIT: After a few days of trying, I was finally able to discover [email protected], [email protected], and [email protected]. (But [email protected] still doesn't work... Hopefully soon)
You're viewing a single thread.
I haven't even been able to connect to magazines on other kbin instances. I've been trying to sign up for [email protected] and [email protected] since yesterday but I still can't get either group to appear in the search from here at fedia.io. I also tried entering the full URL to those groups as the search (which is what works on lemmy). Maybe kbin needs a different format but I think the bang-names were correct here?
I suspect those magazines aren't showing up due to the DDoS protection that's enabled for kbin.social. I think they're still working on fixing the federation issues over there.
I'm having the same problem. This needs sorting out quickly as it's completely defeating the point of a federated model - kbin.social is the biggest Kbin instance and if we can't see its magazines from other instances then they're encouraging everyone to just sign up there instead - which they don't seem able to accommodate anyway...