You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If the connected XMPP server is restarted, Matterbridge loses its connection to the MUC and no messages are sent/received across the bridge until Matterbridge is restarted.
To Reproduce
Configure Matterbridge with an endpoint being an XMPP MUC
Restart the XMPP server that Matterbridge is connected to
No messages are sent/received from the MUC until Matterbridge is restarted
Expected behavior
Matterbridge should detect that it's connection/presence in the MUC has been lost and re-establish it so messages are bridged correctly
Environment (please complete the following information):
I can confirm this bug on my side. I suspected this for a while after seeing matterbridge lose connection to MUC over time.
EDIT: So i tried to restart the MUC server my matterbridge instance is connected to, and it didn't start failing. So i'm not entirely sure if it's because the connection had no time to timeout, or if the problem is elsewhere. Maybe the problem occurs when the homeserver fails, not the MUC server (since the matterbridge client has no direct connection to the MUC server it's plausible)? It would be nice if someone could find how to reproduce this bug!
Describe the bug
If the connected XMPP server is restarted, Matterbridge loses its connection to the MUC and no messages are sent/received across the bridge until Matterbridge is restarted.
To Reproduce
Configure Matterbridge with an endpoint being an XMPP MUC
Restart the XMPP server that Matterbridge is connected to
No messages are sent/received from the MUC until Matterbridge is restarted
Expected behavior
Matterbridge should detect that it's connection/presence in the MUC has been lost and re-establish it so messages are bridged correctly
Environment (please complete the following information):
This might help, it describes the situation going on here.
https://xmpp.org/extensions/xep-0410.html
The text was updated successfully, but these errors were encountered: