Where Do mautrix Bridges Store Config and Data?
mautrix bridges keep per-bridge configs and databases beside each install. Register appservices with Synapse, then back up both together.
Last updated
mautrix bridges connect Matrix to WhatsApp, Discord, Telegram, and others one bridge at a time. Each bridge holds a config file with login sessions plus a database of ghost users and message mappings. Synapse holds the matching appservice registration.
Backups need both halves: bridge data without registration re-registers as a stranger, and registration without data re-puppets every contact. Exact paths may vary by install method, so read the live config locations before scripting. Update bridges with their paired Synapse releases.
Where mautrix Bridges stores this, by platform
/opt/mautrix-bridges/
Config YAML plus database per bridge; registration on the Synapse side. Exact paths may vary by install method. Back up both halves together with bridges stopped.
Frequently asked questions
How do I migrate a mautrix bridge?
Stop the bridge, copy its config YAML plus the database file, then restore both to matching paths on the new host. Tokens must match the Synapse registration or messages stop flowing. Keep bridge and Synapse versions compatible.
How do I register a bridge with Synapse?
Copy the registration YAML into the Synapse config directory and reference it in homeserver.yaml, then restart Synapse before the bridge. Each bridge needs its own registration block. Logs name the missing piece when logins fail.
Notice an outdated path? Let us know.