rms/mirrors-mautrix-telegram
1
0
Fork 0
mirror of https://github.com/mautrix/telegram.git synced 2026-05-16 23:15:45 +03:00
Code Issues Packages Projects Releases Wiki Activity
Page: Troubleshooting
Pages
Authentication Bridge setup with Docker Bridge setup Creating and managing chats Database management system migration End‐to‐bridge encryption Home Management commands Manhole Migrating from Telematrix Optional dependencies Provisioning API Relay bot Troubleshooting
Clone
1
Troubleshooting
Tulir Asokan edited this page 2020-06-29 13:53:01 +03:00
Table of Contents

Why is the bridge bot not accepting invites?

If the bridge starts up successfully, but inviting the bot doesn't work and the logs don't show any errors, it usually means the homeserver isn't sending events to the appservice. There are a few potential reasons this can happen:

  • There was a misconfiguration in the appservice address/hostname/port config or the homeserver can't reach the appservice for some other reason. The homeserver logs should contain errors in this case (grep for transactions in Synapse's homeserver.log).
  • The bridge was down for longer than a few minutes and the homeserver backed off. The homeserver should retry after some time. If it still doesn't work after an hour or so (exact backoff depends on how long the bridge was down), check the homeserver logs.
  • Synapse messed up and silently broke the appservice. This is quite rare, but you should check matrix-org/synapse#1834 if nothing else works.

Wiki deprecated

mautrix-telegram docs are now on docs.mau.fi