-
Notifications
You must be signed in to change notification settings - Fork 619
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
Mattermost on Kubernetes with multiple replicas does not reliably report messages to bridge #2187
Comments
I can confirm that outgoing webhooks resolved the above issue. I ultimately had to use two bridges, one for 'in' and one for 'out. Here is a sample from my toml, where
|
Hello. I have a same problem with mattermost and telegram. [[gateway]]
|
Describe the bug
When a message is written in mattermost, if the Kubernetes replica is not the same one matterbridge is logged into, then it does not capture and transmit the message.
To Reproduce
Expected behavior
Messages should hit the bridge in both directions.
Environment (please complete the following information):
Additional context
I believe this can be solved by using a webhook in one direction and the bot in the other direction. I will try this and perhaps submit a PR to the readme regarding this if it works.
The text was updated successfully, but these errors were encountered: