This repository was archived by the owner on Apr 11, 2025. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 104
Why do some spaces join effortlesly but others return M_NOT_FOUND: Room with alias not found #702
Labels
Comments
Made an account on matrix.org and that server joined effortlessly to plenty of the spaces I have issue with. At this point it seems like rolling the dice if the room will show as not found. Anybody see anything wrong with federation setup for neonpxl.com? |
I recommend running debug mode and reviewing logs to see if it says anywhere why it failed to resolve the alias remotely. |
I stumbled upon this issue with conduwuit space. This is what I see in the logs:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Like I can't join many of the popular rooms because of that. Have to keep to smaller ones.
For example, from other servers I can join #lemmy-space:matrix.org but not from my own.
I have /.well-known/matrix/client and server variant setup.
https://federationtester.matrix.org/ shows no issue at all.
But the severity of M_NOT_FOUND is making using my server unbearable. 75% of room just error out.
The text was updated successfully, but these errors were encountered: