-
-
Notifications
You must be signed in to change notification settings - Fork 676
mautrix-discord cannot relay messages #3328
Comments
I believe the internal server error is coming from here: dendrite/clientapi/routing/joinroom.go Lines 121 to 125 in 67d6876
|
Actually, looking closer, it looks like there is an error message from dendrite, it was just written to stderr instead of stdout:
|
Just noticed this issue, stumbled onto this myself on a fresh e9deb52 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. |
Are you sure this isn't an issue with the bridge? |
Not sure but my install of Synapse handles it fine, so I don't believe the bridge is outright broken. |
Having same issue and I noticed that DMs work aswell but not guilds. Freshly made Dendrite instance. |
It works if I manually invite the bridged users into the room. |
Gonna echo this above seeing the same thing on dendrite, gonna try to set up synapse instead and see if that works better. |
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 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. |
Changing the option 'restricted_rooms' in mautrix-discord does this automatically, so change that to false in mautrix-discord bypaases the issue. |
I am not sure what exactly causes the not itself to not be in the space, as that option would have to do. |
You just have to make sure to unbridge all rooms, and then recreate them |
Background information
go version
: N/ADescription
Steps to reproduce
Additional Information
#2696 had a similar issue
The text was updated successfully, but these errors were encountered: