-
Notifications
You must be signed in to change notification settings - Fork 617
FAQ
First, create a basic configuration following https://github.com/42wim/matterbridge/wiki/How-to-create-your-config
Also, read the Features page.
FAQ for:
(From https://github.com/42wim/matterbridge/discussions/1566)
Matterbridge does not relay messages from the user account that it is logged in as. Make sure it has its own account.
Did you set RemoteNickFormat
?
Try adding RemoteNickFormat="<{NICK}>"
If you're using WebhookURL
in your Slack configuration, this is normal.
If you only have Token
configuration, this could be a bug. Please open an issue.
Gitter doesn't send delete events to their API, so we can't pick those up.
When you delete a message on another bridge Slack, they will be deleted on Gitter though. (matterbridge can delete messages on Gitter, but we do not get an event when a message on Gitter is deleted).
So Slack <=> Gitter bridge, deleting messages when on Gitter doesn't get deleted on Slack.
On the same bridge, deleting messages on slack gets also deleted on Gitter.
Did you specify the correct channel name?
Try using the ID instead of the channel name.
You can find the number in the URL of the channel:
https://discordapp.com/channels/number1/number2
Instead of channel="name"
, set channel="ID:number2"
.
Also, make sure your bot hasn't been banned from the server for some reason.
If you want roles/groups mentions to be shown with names instead of ID, you'll need to give your bot the "Manage Roles" permission.
You need permissions on the server to be able to join the bot, if you're allowed to here's how you do it: Click on the bot here: https://discordapp.com/developers/applications/me
Click the "Generate OAUTH" button, copy the URL and paste it into your address bar, open the page and you'll see the drop down menu for adding the bot to any server you have permissions on.
Message editing is not supported by discord using webhooks. If you want message editing, disable webhooks and use token only
Discord changed its API:
See https://github.com/42wim/matterbridge/wiki/Discord-bot-setup#privileged-gateway-intents for a fix
See https://github.com/42wim/matterbridge/issues/1263 for more info
No.
This is a discord limitation: https://github.com/42wim/matterbridge/issues/1558#issuecomment-1030713994
You can do a workaround by setting PreserveThreading=false
See
- https://core.telegram.org/bots#privacy-mode
- https://github.com/yagop/node-telegram-bot-api/issues/174#issuecomment-244632667
If your bot is not getting messages:
Disable privacy mode with @Botfather.
- Go to BotFather send /setprivacy.
- Select the username of the bot.
- Select Disable.
- Kick bot from chat if it's already in it.
- Invite bot to chat.
The order is important.
Bots talking to each other could potentially get stuck in unwelcome loops. To avoid this, we decided that bots will not be able to see messages from other bots regardless of mode.
https://core.telegram.org/bots/faq#why-doesn-39t-my-bot-see-messages-from-other-bots
Because images/stickers/files are from non-public url's, you'll need to setup a mediaserver
Did you enable MessageFormat="HTML"
in your config?
You could be sending invalid HTML. Set it to MessageFormat=""
More info in https://github.com/42wim/matterbridge/blob/master/matterbridge.toml.sample#L836-L838
Telegram doesn't has "deleted messages" metadata, so we don't know which messages are deleted.
Telegram channels will always return unknown users. Telegram groups will show usernames if possible
Did you create a dedicated account for matterbridge? See https://github.com/42wim/matterbridge/wiki/Section-Mattermost-(basic)
By default, matterbridge tries HTTPS to connect to your Mattermost setup.
If you're using a test setup for Mattermost, this will probably listen on HTTP and on port 8065.
Add NoTLS=true
and use Server="yourmattermostserver.domain:8065"
to your Mattermost configuration.
See also https://github.com/42wim/matterbridge/wiki/Section-Mattermost-(basic)
If you're running the webhooks version, this can be fixed by either:
- enabling "override usernames". See mattermost documentation
- setting
PrefixMessagesWithNick
totrue
inmattermost
section of your matterbridge.toml.
If you're running the login/password version, you'll need to:
- setting
PrefixMessagesWithNick
totrue
inmattermost
section of your matterbridge.toml.
Also look at the RemoteNickFormat
setting.
Use personal access tokens that don't expire https://docs.mattermost.com/developer/personal-access-tokens.html or increase the session timeout, see https://forum.mattermost.org/t/solved-removing-the-session-timeout/3033
See https://github.com/42wim/matterbridge/issues/351 and https://support.steampowered.com/kb_article.php?ref=3330-IAGK-7663 Apparently, the account you use needs to make a purchase on Steam for it to work.
Not support by the library we use (https://github.com/keybase/go-keybase-chat-bot/)
Not supported by Microsoft API
Getting started
How to create your config
Discord bot setup
Slack bot setup
MS Teams setup
Deploy
DigitalOcean
Azure
Docker
Heroku
Gateways
Config: basic
Config: channel rules
Discord
Gitter
Hipchat
IRC
Keybase
Matrix
Mattermost
Microsoft Teams
Mumble
Nextcloud Talk
RocketChat
Slack
Sshchat
Steam
Telegram
Twitch
VK
WhatsApp
XMPP
Zulip
Advanced
Mediaserver setup
Service files
Developer
API
Tengo scripting
Making gateways