-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
"Failed to send_join via any server" with "'coroutine' object has no attribute 'event_id'" #6978
Comments
I think there are two problems here:
|
I'm getting this for other rooms. |
This seems also to be reproducible with Fractal's room #fractal-gtk:matrix.org. At least I'm getting the "Failed to send_join via any server"-message when trying to join the room with two different accounts from two different servers. |
#fractal-gtk:matrix.org is one the rooms that don't work for me too. |
I just tried the two rooms with one of my accounts and I can't join them either. Always fails with "Failed to send_join via any server". |
I think we should consider the signature warning a separate problem. |
Currently having this issue. It seems like it was fixed (since it was moved to Done)? If so, would I have to wait until the next release to correct this issue? Or would temporarily running synapse off of master be enough to correct the issue, which would let me go back to stable? |
After checking my logs, it seems that each time I get this error, I get something like this right before it: This particular error happened when trying to join #Python:matrix.org. Is this related? The error is a bit different. |
the warning is saying that there is an incorrectly-signed event in the room. This bug (fixed in synapse 1.11.1) meant that, instead of recovering gracefully after the warning, the entire join would fail. It is not the only thing that can cause a room join to fail: if you still see "Failed to send_join...", it suggests there is another unrelated problem. There may be additional problems specific to #Python: see #5599. |
I see the same happening at my synapse sever (version v1.20.1):
I got the error message that I couldn't join the room. But it still tries eventually... (I was trying to join the |
On synapse 1.11.0, when you try to join
#synapse:matrix.org
, you get:and later:
The text was updated successfully, but these errors were encountered: