Why do I see a MongoDB deprecated warning immediately after an update?
The installed version of 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?
Firstly, make a full backup of your database. Then, check which MongoDB version is supported by the Rocket.Chat release you’re upgrading to. Use the official MongoDB documentation to perform the upgrade. It’s important to note that upgrades between major versions (like 2.x → 3.x or 3.x → 4.x) often require extra steps, so plan accordingly.
Why do I receive a question about the Unique ID change detected?
Unique ID is the unique identifier of a server. It's a hash created when the Rocket.Chat's deployment starts for the first time.
To prevent Unique ID duplication caused by deployment clones, splits, etc., when the database is copied to start a new deployment, the Unique ID record is also copied, and it becomes the same for the old and new deployments. Rocket.Chat implements a fingerprint solution to help admins identify when those cases happen by mistake.
The fingerprint is composed of the site URL setting and database connection string. When some parts of these two change, the fingerprint changes to a pending state. The admins are then requested to validate the fingerprint again by deciding if the change is, in fact, an expected update of the current workspace or a new workspace deployment.
Configuration update
If the change detected was expected to be a normal workspace configuration change, like a site URL change or a database string change, it's safe to confirm it. By confirming the update, nothing will change and the new fingerprint will become validated.
If the change is a new workspace, by confirming it as an update, it can generate issues with statistics reporting, license validation, push notifications, marketplace access, etc. since more than one workspace is accessing the cloud services using the same unique ID.
New workspace
If the change detected, in fact, means a new deployment has been done, by confirming a new workspace, all the identification information will be reset:
Unique ID: A new unique hash will be generated.
Cloud connection: All cloud connections will be reset.
Cloud workspace: The cloud workspace data linking a cloud instance to the deployment will be reset.
Cloud license: Any license provided by the cloud portal will be reset.
If the change is not a new workspace, confirming a new workspace can generate issues when connecting the deployment to the cloud workspace.
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:
Download the matching edition to your OS.
Install the app.