-
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
Raiden node crashed w/ MatrixRequestError "No known servers" #5504
Comments
Could be an instance of matrix-org/synapse#1533. @nephix Can you reproduce this error? Or was it only the one time? |
Hi @ulope, it still seems to occur on my machine in rc2. To reproduce, I only needed to started the docker container of the rc2 image. I didn't do any transactions from the light client. I also tried to change the matrix server from to and the exception didn't occur, but once I switched back to transport04 I got the exception again after a couple of mins idle time (not sure if this actually helps investigating or was just a coincidence)
|
@nephix Does this only occur with one specific keystore? If yes then from reading the traceback I assume an invite with an invalid server (e.g. not in the federation whitelist) is still stored on the matrix server for your user account. |
@ulope all I can say is that I have removed all my keystores, created new ones and the issue does not seem to occur anymore. So your assumption could be right 👍 |
Ok, thanks. |
Issue to track the underlying cause: #5640 |
Problem Definition
Unfortunately, I don't have any other logs.
System Description
The text was updated successfully, but these errors were encountered: