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
No Known Servers error on trying to join upgraded room #697
Comments
same for me |
My guess is that RiotX is just trying to /join the room ID that's given using the local homeserver, but if another server upgrades the room your local server will not be able to join it without the client telling it which server to ask for information. In the case of room upgrades, the server the client should specify is that of the sender of the tombstone, as their server is the one that upgraded the room. Use this endpoint: https://matrix.org/docs/spec/client_server/unstable#post-matrix-client-r0-join-roomidoralias and provide the sender of the tombstone in the |
The former endpoint doesn't work for joining over federation, the server_name parameter is ignored. Fixes element-hq#697
The former endpoint doesn't work for joining over federation, the server_name parameter is ignored. Fixes element-hq#697 Signed-off-by: Marcus Hoffmann <bubu@bubu1.eu>
The former endpoint doesn't work for joining over federation, the server_name parameter is ignored. Fixes element-hq#697 Signed-off-by: Marcus Hoffmann <bubu@bubu1.eu>
The former endpoint doesn't work for joining over federation, the server_name parameter is ignored. Fixes element-hq#697 Signed-off-by: Marcus Hoffmann <bubu@bubu1.eu>
cc @turt2live
During the mass matrix community room upgrade, I attempted to click on a couple tombstone links but hit No Known Servers on every one.
I've sent a rageshake for my attempt on Synapse Announcements.
The text was updated successfully, but these errors were encountered: