-
Notifications
You must be signed in to change notification settings - Fork 378
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
Handle 404 in join from invite #5640
Labels
Comments
ulope
added
Severity / Medium
Component / Transport
Transport related issues
Type / Bug
labels
Jan 13, 2020
2 tasks
closed by #5709 |
I'm hitting this issue on current
|
We don't use matrix rooms, anymore. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Definition
(Reported in #5504, thanks @nephix)
When the MatrixTransport receives in invite to a room with an invalid server name part (e.g. the server isn't in the federation whitelist (anymore) or the domain no longer exists) the Synapse server will respond with a
MatrixRequestError: 404: {"errcode":"M_UNKNOWN","error":"No known servers"}
.We need to handle this case.
Ideally we'd also reject the invite to avoid re-receiving it on the next restart.
The text was updated successfully, but these errors were encountered: