-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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
Problem with the federation. "SynapseError: 403 - You are not invited to this room" #34112
Comments
This issue arises from desynchronization between Rocket.Chat and Synapse in a federated setup, particularly affecting group membership. Did you make sure that both Synapse servers use compatible Matrix protocol version ? and that Easy fix- |
Everything was set up strictly according to the documentation of the RC. |
@MostlyKIGuess But I roughly tracked some cases when it works and when a problem occurs:
|
Please fill out a bug template properly as per this (use the template, fill it in and and paste here - don't create new issue) Note this as well. |
Hello!
There was a problem with the federation.
Most likely, there was a desynchronization of data in the synapse database.
When I add a user to a group on one RC server, I see error "SynapseError: 403 - You are not invited to this room" in the logs on the second RC server.
In RC, user gets into the room, but in Synapse it hangs in the invite state and must accept it manually.
The user can write messages in RC, but no one will see him on another RC server, since in the matrix he hangs in the invitation state. If you accept the invitation manually through the matrix API, everything starts working. At the same time, direct messages in federation works fine. The problem is only with groups/rooms.
Has anyone encountered such a problem? How did you solve the problem?
Thanks you in advanced
The text was updated successfully, but these errors were encountered: