Federation FAQ

To resolve this issue, you can simply restart the Rocket.Chat container with this command:

docker restart rocketchat

Before creating any federated room, you must validate your federation configuration to ensure it’s functioning properly. For detailed instructions, refer to Verify your federation connection status.

Matrix is an open standard for interoperable, decentralized, real-time communication over IP.

Rocket.Chat aims to enable seamless communication and collaboration across platforms, empowering individuals and organizations to connect on their terms and fluently share information with other platforms.

It's an implementation of the Matrix spec, there are some existing homeservers. The most common are Synapse and Dendrite.

• Installing Synapse.

• Configuring federation.

Visit the prerequisite section for deploying a federated Rocket.Chat workspace with Kubernetes.

After deploying and verifying your workspace, refer to Test the federated workspace.

Visit the Federation Access Control guide.

Whenever you invite someone to chat with you either through public, private, or DM rooms, a copy for that external user will be created in your local workspace. A copy for your user will be created on the external (inviter) server as well. From there, every message is stored on both sides.

No, all the copies being created to support the Matrix Bridge feature will NOT be counted as valid seats. Only users you create in your local workspace are counted as valid seats.

No, all the external users created in your local workspace will be created as a user and without an email and password, which means they cannot log in directly to your workspace. The only way for them to communicate with your local workspace is through the open channel you have with them.

Unfortunately, not at this point. When it comes to presence status, the support from Bridges is very unstable, and due to that, we don't support it yet.