Enterprise Support
Requirements for official support from the Rocket.Chat team
In order to obtain official support from our team, we have a minimum set of requirements. These requirements are necessary for us to access the essential system information, provide an SLA, answer questions, or provide a solution for the problem.
Only installations matching these minimum requirements can be covered by our SLAs and our paid Support Policy. Some requirements may vary depending on the installation size as described in the following sections.
We require the installation to run the Docker image provided by the Rocket.Chat team, this makes it possible to isolate external factors. It ensures that the support request refers to our application and not to the following factors.
- 1.Problems during the compilation process
- 2.Problems during the installation process
- 3.Missing or outdated dependencies
- 4.Installation of non-official versions
This ensures we can provide quick fixes and a more efficient way to reproduce problems leading to the most efficient support flow possible.
Rocket.Chat provides support for, at least, 3 months for each release. Rocket.Chat provides support for 6 months to the latest releases of each major version, e.g. 1.3 is the latest release of major version 1.x before major version 2.0. Rocket.Chat may provide a longer period of support depending on the necessity, check the table below to verify the final support date of each release version.
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.
In case of security-relevant bugs, we might decide to backport patches to older releases on a case-by-case basis. Please understand though, that those will be rare exceptions. If you want to play it safe, upgrade to the latest stable.
Rocket.Chat Release | Latest Version | Released At | End of Life |
|---|---|---|---|
6.0 | 6.0.1 | Mar 2023 | Jun 2023 |
5.4 (LTS) | 5.4.5 | Mar 2023 | Jun 2023 |
5.3 | 5.3.5 | Nov 2022 | Feb 2023 |
5.2 | 5.2.1 | Oct 2022 | Jan 2023 |
5.1 | 5.1.4 | Sep 2022 | Dec 2022 |
5.0 | 5.0.7 | July 2022 | Oct 2022 |
4.8 (LTS) | 4.8.1 | May 2022 | Nov 2022 |
4.7 | Apr 2022 | July 2022 | |
4.6 | Mar 2022 | Jun 2022 | |
4.5 | Feb 2022 | May 2022 | |
4.4 | Jan 2022 | Apr 2022 | |
4.3 | Dec 2021 | Mar 2022 | |
4.2 | Nov 2021 | Mar 2022 | |
4.1 | Oct 2021 | Jan 2022 | |
4.0 | Sep 2021 | Dec 2021 | |
3.18 (LTS) | Aug 2021 | Mar 2022 | |
3.17 | Jul 2021 | Oct 2021 | |
3.16 | Jun 2021 | Sep 2021 | |
3.15 | May 2021 | Aug 2021 | |
3.14 | Apr 2021 | Jul 2021 | |
3.13 | Mar 2021 | Jun 2021 | |
3.12 | Feb 2021 | May 2021 | |
3.11 | Jan 2021 | May 2021 | |
3.10 | Dec 2020 | Mar 2021 | |
3.9 | Nov 2020 | Feb 2021 | |
3.8 | Oct 2020 | Jan 2021 | |
3.7 | Sep 2020 | Dec 2020 | |
3.6 | Aug 2020 | Nov 2020 | |
3.5 | Jul 2020 | Oct 2020 | |
3.4 | Jun 2020 | Sep 2020 | |
3.3 | May 2020 | Aug 2020 | |
3.2 | Apr 2020 | Jul 2020 | |
3.1 | Mar 2020 | Jun 2020 | |
3.0 | Jan 2020 | Apr 2020 | |
2.4 (LTS) | Dec 2019 | Jun 2020 | |
2.3 | Nov 2019 | Feb 2020 | |
2.2 | Oct 2019 | Jan 2020 | |
2.1 | Sep 2019 | Dec 2019 | |
2.0 | Aug 2019 | Nov 2019 | |
1.3 (LTS) | Jul 2019 | Jan 2020 | |
1.2 | Jun 2019 | Sep 2019 | |
1.1 | May 2019 | Aug 2019 | |
1.0 | Apr 2019 | Jul 2019 |
Always update to the latest stable version before reporting any bugs or before ask for help from the community.
LTS means Long Time Support and it's used to identify the last minor version before a major version, e.g. 2.4 is the last minor before 3.x. A new major version means that the version introduced a breaking change and requires attention on the upgrade, so we maintain the support of the previous version for a longer time in order to give you more time to plan and test the upgrade.
Rocket.Chat manages upgrades and provides support to Rocket.Chat Cloud users regardless of the release version. If a Rocket.Chat Cloud user with an outdated server version sends in a support request, his server might be upgraded to the latest stable version without acknowledgment to ensure the best performance.
Rocket.Chat Services include services such as our push gateway, the marketplace, and other services managed by Rocket.Chat.
October 1st our services will no longer continue to guarantee support for Rocket.Chat 0.x. After this date, you may receive errors or warnings about incompatibility.
3 months after a new major release, e.g. 2.x, the last major release, e.g. 1.x, will have the Services support deprecated and you may receive warnings about the deprecation. 5 months after the deprecation the support will be removed and you may receive errors and warnings about incompatibility.
Rocket.Chat Release | Deprecation Date | End of Life Date |
|---|---|---|
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 |
Each Rocket.Chat release supports different versions of MongoDB, the table below presents the support of MongoDB versions for each major Rocket.Chat release in addition to the deprecated version that will be removed on the next or subsequent versions.
Rocket.Chat only adds or removes support of MongoDB versions on major releases so the minor versions are ommited on table below.
Rocket.Chat Release | Supported Versions | Deprecated Version |
|---|---|---|
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 variableBYPASS_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.
The ecosystem of browsers has been and still is, an ever-evolving field of change. Since the rate of change is tremendous, we also have to limit the support to recent browsers. We're usually quite good with that but some older browsers just don't support some features that we build upon. That is why we limit or support for browsers in the following way:
We support the following desktop browsers and versions:
Browser | Supported Versions |
|---|---|
Google Chrome | Latest 3 versions |
Mozilla Firefox | Latest 3 versions |
Apple Safari | Latest 2 versions |
Microsoft Edge | Latest 2 versions |
Microsoft Internet Explorer | Latest version only |
There may be small exceptions in rare cases.
That being said, here's how you can find out if your browser version is still supported (all lists include an indication of a specific browser version is still supported or not):
The support is limited to installations matching the requirements described in the Minimum ​Hardware Requirements page.
We require monitoring for all supported installations. All installations must continually collect Metrics regarding the installation's instances and database. Rocket.Chat supports the industry-standard Prometheus + Grafana monitoring stack. Grafana dashboards required for support are available in the Metrics repository.
Explanations about each metric/graph which help reading and interpreting the data can be found in this dedicated document here.
We do not require access to the servers, instances, or databases to provide support, but we may require access to the logs if we consider them necessary to identify the problem.
Types of logs we may require:
- 1.Server logs
- 2.Web browser logs
- 3.Mobile logs
Last modified 6d ago