Open matrixbot opened 2 weeks ago
This comment was originally posted by @Elara6331 at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-1947604111.
I believe the internal server error is coming from here:
This comment was originally posted by @Elara6331 at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-1947654366.
Actually, looking closer, it looks like there is an error message from dendrite, it was just written to stderr instead of stdout:
level=error msg="Failed to join room" error="M_FORBIDDEN: You are not joined to any matching rooms." room_id="!Sk5rRcx0XrZ87BkT:genzedong.xyz" servers="[]" user_id="@discord_<redacted>:genzedong.xyz"
This comment was originally posted by @regalialong at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-1950322566.
Just noticed this issue, stumbled onto this myself on a fresh e9deb5244edd4827234622ea0d3b11678a33b0ac instance. Works on Synapse so might be worth looking into since there seems to be different behavior between the two.
For me, direct messages seemingly bridged fine while guilds failed.
This comment was originally posted by @niebloomj at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-1953325137.
Are you sure this isn't an issue with the bridge?
This comment was originally posted by @regalialong at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-1953450014.
Not sure but my install of Synapse handles it fine, so I don't believe the bridge is outright broken.
This comment was originally posted by @alnmy at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-2016956496.
Having same issue and I noticed that DMs work aswell but not guilds. Freshly made Dendrite instance.
This comment was originally posted by @alnmy at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-2016958918.
It works if I manually invite the bridged users into the room.
This comment was originally posted by @Pyro57000 at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-2080166751.
Gonna echo this above seeing the same thing on dendrite, gonna try to set up synapse instead and see if that works better.
This comment was originally posted by @pathwayx99 at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-2205441110.
Another echo here. Same error messages, same behavior. Direct messages work fine, guilds do not. I can send messages, which appear on the channel (checking using Discord client) but any replies are not received.
Should say I'm running instagram, messenger and whatsapp bridges without issues.
This comment was originally posted by @fbievan at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-2391600850.
This does not seem to be a dendrite issue... From my short research...
If you are affected try setting your power level in a room to 50, then go and edit the room, look at "room access", then change that public, then back to private... This is due to the fact that for some reason is set to space members only, I think an issue upstream is in order.
This comment was originally posted by @fbievan at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-2391616913.
Changing the option 'restricted_rooms' in mautrix-discord does this automatically, so change that to false in mautrix-discord bypaases the issue.
This comment was originally posted by @fbievan at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-2391622524.
I am not sure what exactly causes the not itself to not be in the space, as that option would have to do.
This comment was originally posted by @fbievan at https://github.com/matrix-org/dendrite/issues/3328#issuecomment-2392045948.
Changing the option 'restricted_rooms' in mautrix-discord does this automatically, so change that to false in mautrix-discord bypaases the issue.
You just have to make sure to unbridge all rooms, and then recreate them
This issue was originally created by @Elara6331 at https://github.com/matrix-org/dendrite/issues/3328.
Background information
go version
: N/ADescription
Dendrite doesn't log any errors, it only logs the following message:
Steps to reproduce
Additional Information
2696 had a similar issue