How configure Rocket Chat and MongoDB in separatelly hosts?

Community Support
8

i think I could solve this issue.

I just remove the ‘replica Set Name’ from the environment variables on MONGO_URL and MONGO_OPLOG_URL

so, here is my result below:

vagrant@app:~$ MONGO_URL=mongodb://192.168.10.17:27017/rocketchat MONGO_OPLOG_URL=mongodb://192.168.10.17:27017/local ROOT_URL=http://0.0.0.0:3000 PORT=3000 node /opt/Rocket.Chat/main.js
Setting default file store to GridFS
LocalStore: store created at 
LocalStore: store created at 
LocalStore: store created at 
Setting default file store to GridFS
ufs: temp directory created at "/tmp/ufs"
Loaded the Apps Framework and loaded a total of 0 Apps!
Updating process.env.MAIL_URL
Using GridFS for custom sounds storage
Using GridFS for custom emoji storage
Browserslist: caniuse-lite is outdated. Please run next command `npm update`
➔ System ➔ startup
➔ +--------------------------------------------+
➔ |               SERVER RUNNING               |
➔ +--------------------------------------------+
➔ |                                            |
➔ |  Rocket.Chat Version: 3.0.9                |
➔ |       NodeJS Version: 12.14.0 - x64        |
➔ |      MongoDB Version: 4.0.17               |
➔ |       MongoDB Engine: mmapv1               |
➔ |             Platform: linux                |
➔ |         Process Port: 3000                 |
➔ |             Site URL: http://0.0.0.0:3000  |
➔ |     ReplicaSet OpLog: Enabled              |
➔ |          Commit Hash: b7f307df1e           |
➔ |        Commit Branch: HEAD                 |
➔ |                                            |
➔ +--------------------------------------------+

It seems the ‘?replicaSet=rs01’ on url, was causing some problem when the applications tried to connect with mongodb.

For now, I don’t understand what is the impact to not specify the replica set name on url.

I’ll check this and see what happens to consider my app connect this way