Deployment and Update FAQ

Prev Next

What are the different deployment options?

Rocket.Chat supports the following deployment methods:

  • Air-gapped deployment with Docker to use Rocket.Chat in an isolated environment.

  • Cloud-hosted workspace with tiers of various hosting services.

  • Self-managed workspaces where you can deploy Rocket.Chat yourself using Docker, Kubernetes, Snaps, or other methods like Ubuntu and DigitalOcean.

Updating Rocket.Chat

How do I update a Rocket.Chat deployment?

For a deployment-specific update instructions, see the following resources:

Additional resources:

Why am I seeing a message about a “Unique ID change detected”?

This message appears when Rocket.Chat detects changes that may indicate a new deployment or a significant workspace configuration update. To prevent issues caused by cloned or duplicated deployments, Rocket.Chat uses a system called a fingerprint to verify the identity of each workspace.

What is the Unique ID?

The Unique ID is a hash that uniquely identifies a Rocket.Chat server. It is generated automatically the first time the server starts. This ID helps ensure that cloud features (e.g., license validation, push notifications) are only associated with a single workspace.

Why would the Unique ID trigger a warning?

If a database is copied, for example, to clone, migrate, or scale a deployment, the Unique ID is copied too. This can unintentionally cause two deployments to share the same ID.

To detect and prevent this, Rocket.Chat uses a fingerprint, which is based on:

  • The Site URL setting

  • The database connection string

If either of these values changes, the fingerprint becomes invalid, and admins are asked to confirm whether the change was expected or part of a new deployment.

What should I do?

If this is an expected configuration change (e.g., you updated the site URL or changed database settings):

  • It's safe to confirm the update.

  • The fingerprint will be validated again.

  • Nothing else will change.

If this is actually a new deployment (e.g., a cloned or duplicated instance):

  • You should confirm it as a new workspace.

In this case, Rocket.Chat will:

  • Generate a new Unique ID

  • Reset all cloud connections

  • Clear the cloud workspace link

  • Reset the cloud license

Note: Confirming a new workspace when it’s not actually new can lead to issues with statistics, cloud services, and licensing. Be sure before confirming.

Updating MongoDB

Why do I see a MongoDB deprecated warning immediately after an update?

This warning appears when your MongoDB is not compatible with your current Rocket.Chat version. To resolve this, upgrade MongoDB to a version supported by the Rocket.Chat release you're targeting.

Are there any recommendations for updating MongoDB?

Updating MongoDB safely is essential to avoid data loss or compatibility issues. Here’s what we recommend:

  1. Back up your database: Before doing anything else, create a complete backup of your MongoDB data.

  2. Check compatibility: Identify which MongoDB versions are supported by the Rocket.Chat version you’re upgrading to.

  3. Follow official guidance: We recommend using the official MongoDB documentation to guide your upgrade process.

  4. Plan for major version jumps: Upgrades between major versions (like 2.x → 3.x or 3.x → 4.x) often involve additional steps or migration requirements. Be sure to read the release notes and plan accordingly.

Refer to the following documents for further information:

Updating desktop app

Why can't I update my desktop app to version 2.17.0 or above?

In some cases, for version 2.17.0 and above, you may need help with updating your app. If you click on the Install Update button and nothing happens for one minute, then you need to follow the steps below: