Open matrixbot opened 3 weeks ago
This comment was originally posted by @ashkitten at https://github.com/matrix-org/dendrite/issues/2522#issuecomment-1236536425.
i'm seeing this issue as well, dendrite 0.9.6
This comment was originally posted by @ashkitten at https://github.com/matrix-org/dendrite/issues/2522#issuecomment-1237094682.
this seems like it may be related to these complement tests that are currently skipped:
at a guess, it feels like it may be checking the wrong room for membership. instead of checking the space from the join rules, if it checked the target room then it would fail.
This comment was originally posted by @arenekosreal at https://github.com/matrix-org/dendrite/issues/2522#issuecomment-1729664016.
I think this problem is existing on dendrite 0.13.2
The room #archlinux-cn-offtopic:nichi.co
requires people join their space #archlinux-cn-space:nichi.co
first. When one of my friends @phantomfutaba:data.haus
tried to join the room and do everything required, he absolutely succeeded joining the room. However, dendrite thoughts that join_authorised_via_users_server
in his join event is someone who cannot invite people, so dendrite treats my friend as an invalid user and ignores everything my friend says.
This is dendrite's log when my friend joins the room:
time="2023-09-21T07:49:01.163132251Z" level=warning msg="Event $1-f9XIPhMlikLhN6ejqsLsofQq-b05l-awVsfKDaRG8 not allowed by auth events" context=missing error="eventauth: the nominated 'join_authorised_via_users_server' user \"@lanmengcha:data.haus\" does not have permission to invite (0 < 50)" event_id="$1-f9XIPhMlikLhN6ejqsLsofQq-b05l-awVsfKDaRG8" kind=KindOutlier origin="" room_id="!TczZJIbozgTQfqUYBA:nichi.co" type=m.room.member
This is the log when my friend speaks:
time="2023-09-21T05:31:56.518791962Z" level=warning msg="Event $9MbjYBkfUQrdUlysaZxFV3YqrFkHrXpWvnMVE19tQjY not allowed by auth events" context=missing error="eventauth: sender \"@phantomfutaba:data.haus\" not in room" event_id="$9MbjYBkfUQrdUlysaZxFV3YqrFkHrXpWvnMVE19tQjY" kind=KindNew origin=data.haus room_id="!umlJmbWNOMWEaVlphw:matrix.org" type=m.room.message
time="2023-09-21T05:31:56.525458066Z" level=warning msg="Stored rejected event" context=missing error="eventauth: sender sender \"@phantomfutaba:data.haus\" not in room" event_id="$9MbjYBkfUQrdUlysaZxFV3YqrFkHrXpWvnMVE19tQjY" kind=KindNew origin=data.haus room_id="!umlJmbWNOMWEaVlphw:matrix.org" type=m.room.message
time="2023-09-21T05:31:56.525504940Z" level=warning msg="Roomserver rejected event" error="eventauth: sender \"@phantomfutaba:data.haus\" not in room" event_id="$9MbjYBkfUQrdUlysaZxFV3YqrFkHrXpWvnMVE19tQjY" room_id="!umlJmbWNOMWEaVlphw:matrix.org" type=m.room.message
The reason why my friend speaks before he joins is that the join log is get after an instance restart while the speak log is obtained before the restart.
This comment was originally posted by @jackmaninov at https://github.com/matrix-org/dendrite/issues/2522#issuecomment-2332017404.
I am also seeing this issue (I believe).
In my case I am seeing failed to find the membership event for 'join_authorised_via_users_server' user
referencing the second of two space administrators, who happens to not be in a subset of the rooms in that space. Adding that admin to the rooms allows other users to join.
Affected users had not been invited to the space by this second administrator, so it is not clear to me why Dendrite would expect that admin to be involved in the room join at all. Is perhaps the most recently added/promoted administrator being referenced?
This issue was originally created by @luk3yx at https://github.com/matrix-org/dendrite/issues/2522.
Background information
go version
: 1.18.3Description
The user that it says isn't joined to the room is not necessarily the same user that is attempting to join the room. This only seems to affect some rooms in the space.
Steps to reproduce
For some reason the room shows as "unnamed room" for the second Dendrite user at this point:
Possibly relevant logs:
Edit: I've tried again with Dendrite v0.8.8 and still got this error, although it only occurred the second time I tried to reproduce it with a newly created space. I got different log messages this time, maybe the previous logs were irrelevant.