Enterprise Support and Version Durability
Requirements for official support from the Rocket.Chat team
Requirements for official support from the Rocket.Chat team
Rocket.Chat 6.0 is our most secure and scalable version yet. It includes 10 security patches, 9 brand-new features, and 25+ overall platform enhancements. Visit our to learn more about what’s new in this latest version. !
Rocket.Chat 6.0 is the latest, most secure, and scalable version, featuring security patches, new features, and platform enhancements.
To obtain official support, installations must meet specific requirements, ensuring that the support request pertains to the Rocket.Chat application and not external factors. The installation should run the Docker image provided by the Rocket.Chat team to ensure this.
Rocket.Chat requires the installation to run on their Docker image to isolate external factors. This approach ensures efficient support by avoiding issues like:
Compilation problems.
Installation issues.
Missing or outdated dependencies.
Use of non-official versions.
Rocket.Chat Versions
Legacy server versions are being deprecated. To continue using mobile and desktop applications and access cloud services after October 1, 2023, workspaces must stay within the supported window.
Rocket.Chat will support the prior minor release for 3 months and the prior major release for 6 months. For instance, version 1.2.x will be supported for 3 months after the release of 1.3.0. Version 1.3.x will be supported for 6 months after the release of 2.0.0.
We are deprecating cloud services, mobile and desktop applications for legacy server versions with the introduction of the new policy, which will take effect on October 1, 2023. For all the Community and Enterprise workspaces to continue using our mobile and desktop applications and access cloud services after October 1st, they must stay within the supported window.
By support, we mean that Rocket.Chat will provide only security fixes and answer support tickets related to configuration and usage for the below-mentioned versions. Bugs not related to security issues will be fixed only in new versions.
Check the table below to verify the final support date of each release version.
6.4
Sep 2023
TBD
6.3
Jul 2023
Dec 2023
6.2
Apr 2023
Oct 2023
6.1
Mar 2023
Jul 2023
6.0
Feb 2023
Jun 2023
5.4 (LTS)
Nov 2022
Aug 2023
5.3
Oct 2022
Feb 2023
5.2
Sep 2022
Jan 2023
5.1
Aug 2022
Dec 2022
5.0
Jul 2022
Nov 2022
4.8 (LTS)
May 2022
Jan 2023
4.7
Apr 2022
Aug 2022
4.6
Mar 2022
Jul 2022
4.5
Feb 2022
Jun 2022
4.4
Jan 2022
May 2022
4.3
Dec 2021
Apr 2022
4.2
Nov 2021
Mar 2022
4.1
Oct 2021
Feb 2022
4.0
Sep 2021
Jan 2022
3.18 (LTS)
Aug 2021
Mar 2022
3.17
Jul 2021
Nov 2021
3.16
Jun 2021
Oct 2021
3.15
May 2021
Sep 2021
3.14
Apr 2021
Aug 2021
3.13
Mar 2021
Jul 2021
3.12
Feb 2021
Jun 2021
3.11
Jan 2021
May 2021
3.10
Dec 2020
Apr 2021
3.9
Nov 2020
Mar 2021
3.8
Oct 2020
Feb 2021
3.7
Sep 2020
Jan 2021
3.6
Aug 2020
Dec 2020
3.5
Jul 2020
Nov 2020
3.4
Jun 2020
Oct 2020
3.3
May 2020
Sep 2020
3.2
Apr 2020
Aug 2020
3.1
Mar 2020
Jul 2020
3.0
Jan 2020
Jun 2020
2.4 (LTS)
Dec 2019
Jul 2020
2.3
Nov 2019
Mar 2020
2.2
Oct 2019
Feb 2020
2.1
Sep 2019
Jan 2020
2.0
Aug 2019
Dec 2019
1.3 (LTS)
Jul 2019
Feb 2020
1.2
Jun 2019
Oct 2019
1.1
May 2019
Sep 2019
1.0
Apr 2019
Aug 2019
Always update to the latest stable version before reporting any bugs or before asking for help from the community.
Rocket.Chat manages upgrades for Cloud users regardless of the release version. Outdated server versions might be upgraded to the latest stable version for optimal performance.
Services such as the push gateway and marketplace are managed by Rocket.Chat. Three months after a new major release, the last major release will have its Services support deprecated. Five months post-deprecation, support will be removed, leading to potential errors and warnings about incompatibility.
Before the end of the deprecation period, we strongly recommend all the workspaces on Community and Enterprise editions to upgrade to a supported version (version 6.0.0 or higher) for continued access to cloud services, mobile and desktop apps. If you do not wish to upgrade, Rocket.Chat provides workspace owners with a variety of options for managing their workspaces in the manner of your choosing. If you choose to remain on a version of Rocket.Chat that is outside of our LTS, you must implement the following alternatives to our cloud services and published apps:
Mobile and desktop apps: You must compile each app from our open-source code and publish your own builds to relevant app stores.
Push notifications: You will need to deploy your own push notification server.
Apps: You will be required to develop and sideload your own applications instead of installing them through our Marketplace.
0.x
Aug 2019
Jan 2020
1.x
Nov 2019
Apr 2020
2.x
May 2020
Oct 2020
3.x
Jan 2022
Jun 2022
4.x
TBD
TBD
5.x
TBD
TBD
6.x
TBD
TBD
Each Rocket.Chat release supports different MongoDB versions. It's essential to follow the official MongoDB documentation for upgrade guides, ensuring no versions are skipped during the upgrade process.
Rocket.Chat only adds or removes support of MongoDB versions on major releases so the minor versions are ommited on table below.
1.x
3.2, 3.4, 3.6, 4.0
3.2
2.x
3.4, 3.6, 4.0
3.4
3.x
3.4, 3.6, 4.0
3.4
4.x
3.6, 4.0, 4.2, 4.4, 5.0
3.6, 4.0
5.x
4.2, 4.4, 5.0
4.2
6.x
4.4, 5.0, 6.0
The upgrade guides available from the official MongoDB documentation are listed below. Bear in mind that it's not possible to skip a version when upgrading, e.g. to upgrade from 3.2 to 3.6 it's necessary to upgrade from 3.2 to 3.4 first and then to 3.6.
It's possible to bypass the MongoDB version check by using the environment variable
BYPASS_MONGO_VALIDATION=true. Bare in mind that this work around should be used only when extrictly necessary and may prevent some functionalities to work properly or even prevent the server to start.
Support is limited to recent browsers due to the rapid evolution in the browser ecosystem. Supported browsers include the latest three versions of Google Chrome and Mozilla Firefox, the latest two versions of Apple Safari and Microsoft Edge, and the latest version of Microsoft Internet Explorer.
While Rocket.Chat doesn't require server or database access, they might need access to logs to identify issues. Potential logs include server logs, web browser logs, and mobile logs.
Support is limited to installations that meet the requirements described in the guide.
Monitoring is required for all supported installations, with Rocket.Chat supporting the .