Docker Rocket.Chat - SLACK alternative (with MongoDB as backend)

[Rusty]

Rusty submitted a new resource:

Rocket.Chat - SLACK alternative (with MongoDB as backend) - Tutorial for setting up RocketChat platform via Docker for running your very own, private chat

View attachment 265

Did you hear of SLACK? How about Discord? Microsoft Teams? Great! Then you know what this tutorial will be all about.

In this tutorial, we will focus on running an open source, private alternative to those platforms. Enter, Rocket.Chat

Just in case that you haven't heard about any of those platforms or have never used them, let say in...

Read more about this resource...

 

[WST16]

Desperately trying to find something that works now.
Couldn't go past the first step! I think I'm hopeless when it comes to this mongo thing

This is what I have:

How to do this?! (or is it going to be generated later through all the configurations?)

 

[Rusty]

Desperately trying to find something that works now.
Couldn't go past the first step! I think I'm hopeless when it comes to this mongo thing

This is what I have:

View attachment 271


How to do this?! (or is it going to be generated later through all the configurations?)

View attachment 272

As I said, create a conf file (using a text editor) and then mount it using the volume section. Just use the Add file button, not folder

 

[jeyare]

Rusty, how is the E2E encryption?
Till now we use Syno Chat for “secure” conversation and sensitive data exchange (screenshots, etc) for an immediate action execution within team.
Except Android notifications (it sometimes doesn't work properly). All the rest clients work well (our situation iOS/Win,Lnx). Include data exchange from/to NAS.
Also Private key encryption does work perfect. If you lose your passphrase or private Key, then only admin of the particular chat thread can give you back new authorization with no lose of content.
Applicable for a NDA content.

 

[Rusty]

Rusty, how is the E2E encryption?

Not using it atm, still in beta for the time being. Tried it a bit but it was unstable months back. Would have to give it another go to tell you some concrete info.

 

[jeyare]

Yes, also read about the Beta feature in Rocket. Front end client is nice. But the E2E encryption is must for us. You did again great job!

 

[Rusty]

The main reason why I stopped using it on my server is this:

The mobile apps may not support the encrypted messages (they are implementing it).

Considering that most users are mobile this will have the most sense to implement when it rolls out.

 

[jeyare]

The main reason why I stopped using it on my server is this:
Considering that most users are mobile this will have the most sense to implement when it rolls out.

Syno Chat? It works.

 

[Rusty]

Syno Chat? It works.
View attachment 276

Ofc... I just prefer not to be locked down. Also at one point Chat didnt offer "outside" users but build DSM users that were suppose to use Chat. Didn't like that. Wit ha 3rd party solution I have no connections to it and also I can deploy it anywhere I want (hw and sw independent).

Still, as a solution inside an organization that uses other Syno apps, there is no reason not to use it.

Also are these private channels or encrypted? Or both?

 

[jeyare]

Absolutely right - it is just for our internal comm within team (as I wrote). Then no troubles with outside users.
Private and Encrypted comm.

 

[jeyare]

for all other comm we can use plenty of them - up to customer's wish
But interested to find an aggregation tool - as Smooch for Docker.

 

[Rusty]

Absolutely right - it is just for our internal comm within team (as I wrote). Then no troubles with outside users.
Private and Encrypted comm.

Yeah we also run an RC and Chat in my team as well. But I prefer RC as a private public chat, just to keep new user creation on DSM to a minimum.

 

[Rusty]

Rusty updated Rocket.Chat - SLACK alternative (with MongoDB as backend) with a new update entry:

Rocket.Chat DB backup and restore steps

In case you ever need to restore your RC content to the same or a separate RC instance you might get into a bit of a problem with MongoDB.

Now unless you are using snapshot replication (for local or remote restore) method you will not be able to just copy paste your MongoDB content to a new mongoDB instance for example because that container will not boot up at all.

What you wanna do (if you are restoring your RC setup to a new location for example) is the following:

01. setup a new...

Read the rest of this update entry...

 

[Rockstream]

Thank you so much for your Tutorial, I really tried to find something like this for a long time. Only thing is, I can't get Rocketchat to connect to MongoDB.
I always get this response:

os: { type: "Linux", name: "linux", architecture: "x64", version: "4.4.59+" }, platform: "Node.js v8.11.4, LE, mongodb-core: 3.1.5" }
2019-07-23T09:06:53.653+0000 I ACCESS [conn64] Supported SASL mechanisms requested for unknown user 'root@admin'
2019-07-23T09:06:53.671+0000 I ACCESS [conn64] SASL SCRAM-SHA-1 authentication failed for root on admin from client 172.17.0.5:48900 ; UserNotFound:
Could not find user root@admin

I can log into mongo db directly without any problems

 

[Rusty]

Could not find user root@admin

So you are running mongoDB database instance as "admin"? Not sure whats trying to connect to your admin db as root? At what point are you getting this?

 

[Rockstream]

I've set my Rocketchat Container to
MONGO_URL = mongodb://root:yourRootPass@db:27017/db?authSource=admin
MONGO_OPLOG_URL = mongodb://root:yourRootPass@db:27017/local?authSource=admin

(for testing purposes I even changed the root pwd for the mongodb user to "yourRootPass". so it should be identical to your tutorial)

Rocketchat crashes and I get the message above from the MongoDB Terminal

 

[Rusty]

And you have set up an alias on your RC container towards your mongo container under the name "db"?

 

[Rockstream]

And you have set up an alias on your RC container towards your mongo container under the name "db"?

Yes! I've followed your tutorial, even tried the whole process a second time, but I can't get it to work

 

[mirk0]

I have a problem when executing a command :mongod --smallfiles --oplogSize 128 --replSet rs0
gets a message:

2019-08-09T10:00:43.239+0000 I CONTROL [initandlisten] options: { replication: { oplogSizeMB: 128, replSet: "rs0" }, storage: { mmapv1: { smallFiles: true } } }
2019-08-09T10:00:43.239+0000 I STORAGE [initandlisten] exception in initAndListen: DBPathInUse: Unable to lock the lock file: /data/db/mongod.lock (Resource temporarily unavailabl
e). Another mongod instance is already running on the /data/db directory, terminating
2019-08-09T10:00:43.239+0000 I CONTROL [initandlisten] now exiting
2019-08-09T10:00:43.239+0000 I CONTROL [initandlisten] shutting down with code:100


does anyone know how to solve this?
Thanks
Mirek

 

[Rusty]

I have a problem when executing a command :mongod --smallfiles --oplogSize 128 --replSet rs0
gets a message:

2019-08-09T10:00:43.239+0000 I CONTROL [initandlisten] options: { replication: { oplogSizeMB: 128, replSet: "rs0" }, storage: { mmapv1: { smallFiles: true } } }
2019-08-09T10:00:43.239+0000 I STORAGE [initandlisten] exception in initAndListen: DBPathInUse: Unable to lock the lock file: /data/db/mongod.lock (Resource temporarily unavailabl
e). Another mongod instance is already running on the /data/db directory, terminating
2019-08-09T10:00:43.239+0000 I CONTROL [initandlisten] now exiting
2019-08-09T10:00:43.239+0000 I CONTROL [initandlisten] shutting down with code:100


does anyone know how to solve this?
Thanks
Mirek

How are you running this command exactly? Are you running it after you have started the container or are you starting the container with that command? The idea is to run the container with that command line not run it afterward.