This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Error: not invited when joining too quickly #2367
Labels
A-Federated-Join
joins over federation generally suck
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Comments
Seems I got same problem when inviting bots from other homeserver, here are logs:
After adding 3 sec delay on remote bot side, it invites normally to my (new) room. |
babolivier
added a commit
to babolivier/matrix-poll-bot
that referenced
this issue
Jul 4, 2019
Otherwise we bump into matrix-org/synapse#2367
Same problem with https://github.com/progserega/voice2textMatrix bot, adding 1sec delay workaround works well. |
Related to #10066 |
MadLittleMods
added
the
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
label
Nov 10, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
A-Federated-Join
joins over federation generally suck
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
On the Matrix-IRCnet bridge some people have trouble sending a message to a person.
The cause seems to be that if the invited party joins too quickly, the inviting homeserver denies the join.
The bridge automatically joins, resulting in 307 ms between sending the invite and receiving the join.
The resulting response is
SynapseError: 403 - You are not invited to this room
.log.txt contains the debug log for the two requests (creating/inviting and joining).
On the server, I see the following events:
The server then creates (and signs) the following event.
Note that the
prev_events
is actually one event too early.The text was updated successfully, but these errors were encountered: