# BYPASS\_MONGO\_VALIDATION=true is not bypassing the MongoDB version check

**URL:** <https://forums.rocket.chat/t/bypass-mongo-validation-true-is-not-bypassing-the-mongodb-version-check/14681>\
**Category:** RaspberryPi and ARM\
**Created:** [August 13, 2022, 11:52am UTC](https://forums.rocket.chat/t/bypass-mongo-validation-true-is-not-bypassing-the-mongodb-version-check/14681 "2022-08-13T11:52:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![m0ahn](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@m0ahn](https://forums.rocket.chat/u/m0ahn)\
**Post date:** [August 13, 2022, 11:52am UTC](https://forums.rocket.chat/t/bypass-mongo-validation-true-is-not-bypassing-the-mongodb-version-check/14681/1 "2022-08-13T11:52:54Z")

</div>

**Description** :

Environment variable BYPASS\_MONGO\_VALIDATION=true is not bypassing the MongoDB version check

**Steps to reproduce** :

1. Install via snap **sudo snap install rocketchat-server** or switch branches to “4.x/stable”
2. Get system message: “MongoDB version 3.6.23 is deprecated, please upgrade your installation.”
3. Add **export BYPASS\_MONGO\_VALIDATION=true** to /etc/profile

**Expected behavior:**

MongoDB version check should be bypassed and Admins DO NOT receive a Rocket.Cat alert

**Actual behavior** :

MongoDB version check runs and Admins DO receive a Rocket.Cat alert

**Server Setup Information** :

- Version of Rocket.Chat Server: 4.1.2
- Operating System: Ubuntu 18.04.5 LTS on Raspberry Pi 4
- Deployment Method: snap
- Number of Running Instances: 1
- NodeJS Version: v12.22.7
- MongoDB Version: 3.6.23 / wiredTiger (oplog Enabled)

**Additional context** :

I have exactly [this issue](https://github.com/RocketChat/rocketchat-server-snap/issues/29) where i’ve upgraded Rocket Chat to 4.1.2 via a Snap and i’m getting the message “ **MongoDB version 3.6.23 is deprecated, please upgrade your installation.** ”.

The thread goes on to state **“The mongo update will happen shortly. You can ignore the deprecation message in the meantime.”** , but that was 9 months ago.

I’ve no issue waiting, however, every Admin is getting frequently spammed with Rocket.Cat alerts in the meantime for which there is no corrective action available to us.

[This post](https://docs.rocket.chat/getting-support#mongodb-versions) states:

_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._

This would seem the best course of action but it doesn’t work. I’ve added the variable to /etc/profile and confirmed it is available before Rocket Chat server starts.

---

<div class="post-metadata">

**Author:** ![trevojnost](https://avatars.discourse-cdn.com/v4/letter/t/85f322/32.png) [@trevojnost](https://forums.rocket.chat/u/trevojnost)\
**Post date:** [August 5, 2025, 7:59am UTC](https://forums.rocket.chat/t/bypass-mongo-validation-true-is-not-bypassing-the-mongodb-version-check/14681/2 "2025-08-05T07:59:53Z")

</div>

Was struggling with these notifications and finally found another flag `SKIP_MONGODEPRECATION_CHECK=true` to skip banner \ admin notifications. `BYPASS_MONGO_VALIDATION` just allows you to run rocket on older versions of MongoDB.

Fount it here [Rocket.Chat/apps/meteor/server/startup/serverRunning.js at 0ab304de5fd9e34133ae95e546bacb67270ae814 · RocketChat/Rocket.Chat · GitHub](https://github.com/RocketChat/Rocket.Chat/blob/0ab304de5fd9e34133ae95e546bacb67270ae814/apps/meteor/server/startup/serverRunning.js#L102)

---

<div class="post-metadata">

**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\
**Post date:** [August 5, 2025, 10:48am UTC](https://forums.rocket.chat/t/bypass-mongo-validation-true-is-not-bypassing-the-mongodb-version-check/14681/3 "2025-08-05T10:48:04Z")

</div>

That really isn’t a good idea.

The real answer is upgrade your Mongo. Yup - Mongo 5+ needs AVX extensions so you may have to upgrade hardware too. This has been known for a long time.

As a sysadmin running unsupported versions of any software is not a great idea.

All versions prior to Mongo 7 are now out of support - that isn’t the fault of Rocket.Chat

It also means no security patches, and Rocket may well use functions that are ONLY supported on newer versions of Mongo.

**A Rocket upgrade could totally bork your install.**

Make sure you have backups……. NB if you have issues then any github issues you open will get closed……

> **[MongoDB Software Lifecycle Schedules](https://www.mongodb.com/legal/support-policy/lifecycles)**
>
> MongoDB Software Lifecycle Schedules
