-
Notifications
You must be signed in to change notification settings - Fork 228
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
"Error: no create event in state" when joining room #17377
Comments
It seems like joining #matrix.to:matrix.org from a new homeserver will no longer work since the original server used to create the room ( You can join that room from an account on matrix.org (or any other server that already has an account which is a member of the room) since those homeservers will have already been able to obtain the signing keys necessary to verify the room's events. Any new homeserver will not be able to fetch the appropriate signing keys, and therefore will not be able to join the room properly. |
Do you have any logs for #FrOSCon:fiksel.info? (I didn't see it in the logs you sent, so I don't know if that room is the same issue or not) |
|
So, if the server creating a room goes away, then no new homeservers can join the room? Should this be considered a bug in the spec? |
That's true only if your server is not configured to use a notary server to fetch server keys. (or if the configured notary server/s doesn't/don't have the key for the appropriate server) There is a provision in the spec that allows for "perspective/notary" key servers to provide server keys on another's behalf. (https://spec.matrix.org/v1.11/server-server-api/#retrieving-server-keys) Have you changed the value of |
Closing due to lack of reply and @devonh already explained a solution to the problem ✅ |
Description
Joining a room will result in "No create event in state" error.
Steps to reproduce
Homeserver
tusooa.xyz
Synapse Version
v1.109.0
Installation Method
Docker (matrixdotorg/synapse)
Database
postgresql; single server; used portdb; restored from backup
Workers
Multiple workers
Platform
Docker swarm across 4 nodes; Ubuntu 22.04
Configuration
No presence
Relevant log output
see the first comment below
Anything else that would be useful to know?
#webrtc:matrix.org
works, even though it's also my first time joining the room. I am wondering whether this is due to the special characters present in the room alias (.
inmatrix.to
and capital letters in FrOSCon).The text was updated successfully, but these errors were encountered: