-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't join a room with room membership access over federation #501
Comments
Yeah this happens to me. If one add another space hosted on Synapse to the access list, others can join. |
What do you mean by this? This is very vague. What does "add another space hosted on Synapse" imply? What's a "space" in this context? A room? Does that mean join another room from the remote server running Synapse to a user on the Conduwuit server (local)? |
No, I mean that a remote server (only tried Synapse) cannot join a room which is hosted on conduwuit and is restricted to a space on conduwuit.
Upon adding a space hosted on Synapse to the allow list, other servers’ users can join.
This is very weird and discovered when I host some bridges for the Arch community.
…--
Sincerely,
Kimiblock
|
Is this still an issue? |
Yup, same error on 16014e1. |
Trying to join a room with access set to space members over federation results in:
MatrixError: [403] Answer from example.com: [403 / M_FORBIDDEN] M_FORBIDDEN: Event is not authorized.
Steps to reproduce:
Visible to space members
Doing this with 2 accounts on a single homeserver seems to work fine.
The text was updated successfully, but these errors were encountered: