Skip to content
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

Bridge to XMPP MUC not functioning after XMPP server restart #1552

Open
appletalk opened this issue Jul 21, 2021 · 2 comments
Open

Bridge to XMPP MUC not functioning after XMPP server restart #1552

appletalk opened this issue Jul 21, 2021 · 2 comments

Comments

@appletalk
Copy link

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):

  • Running in docker, version 1.22.4-dev da4dcec

This might help, it describes the situation going on here.
https://xmpp.org/extensions/xep-0410.html

@appletalk appletalk added the bug label Jul 21, 2021
@southerntofu
Copy link

southerntofu commented Jul 22, 2021

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!

@Neustradamus
Copy link
Contributor

Any news about this ticket?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants