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

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

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

That's the problem. If you are running it via gui then read the tutorial again and double-check that you have placed this command in the CMD field before starting the container.

Screenshot 2019-08-09 at 13.08.08.png


You missed the IMPORTANT quote that's stating this. Read more carefully.
 
That's the problem. If you are running it via gui then read the tutorial again and double-check that you have placed this command in the CMD field before starting the container.

View attachment 400

You missed the IMPORTANT quote that's stating this. Read more carefully.

Thanks a lot, works.

what do you mean in this text :Keep in mind that db parameter after @ needs to be the same one as the one that you have
used in the LINKS. Also, the port number needs to be the same one as INTERNAL/container parameter for your mongoDB ?


my configuration is identical to yours but when I type it
MONGO_URL = mongodb://root:xxxx@db:27017/db?authSource=admin
MONGO_OPLOG_URL = mongodb://root:xxxx@db:27017/local?authSource=admin

i have a comunicat :SASL SCRAM-SHA-1 authentication failed for root on admin from client 172.17.0.6:48638 ; UserNotFound: Could not find user root@admin

when I set :MONGO_URL = mongodb://root:xxxx@db:27017
MONGO_OPLOG_URL = mongodb://root:xxxx@db:27017/local?replicaSet=rs0

Error: $MONGO_OPLOG_URL must be set to the 'local' database of a Mongo replica set
MongoNetworkError: failed to connect to server [localhost:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017]


What I must set mongo_oplog_url ?
 
log mongo i have :
2019-08-09T15:33:48.367+0000 I NETWORK [listener] connection accepted from 172.17.0.6:48770 #4 (2 connections now open)
stdout
15:33:482019-08-09T15:33:48.378+0000 I NETWORK [conn4] received client metadata from 172.17.0.6:48770 conn4: { driver: { name: "nodejs", version: "3.1.6" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.4.59+" }, platform: "Node.js v8.11.4, LE, mongodb-core: 3.1.5" }
stdout
15:33:482019-08-09T15:33:48.379+0000 I ACCESS [conn4] Supported SASL mechanisms requested for unknown user 'root@db'
stdout
15:33:482019-08-09T15:33:48.391+0000 I NETWORK [conn4] end connection 172.17.0.6:48770 (1 connection now open)


in rocket.chat :
MongoNetworkError: failed to connect to server [localhost:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017]
 
Hi Rusty thanks for this great tutorial, unfortunately I can't get past the first step even though I set up everything correctly.

Once I finished setting up the mongo container it stops as soon as its launched and shows me this error in the log :

Error parsing command line: unrecognised option '--smallfiles'

Your help would mean a lot!
 

Attachments

  • Capture d’écran 2019-08-24 à 08.27.34.png
    Capture d’écran 2019-08-24 à 08.27.34.png
    218.9 KB · Views: 63
  • Capture d’écran 2019-08-24 à 08.27.40.png
    Capture d’écran 2019-08-24 à 08.27.40.png
    166 KB · Views: 62
  • Capture d’écran 2019-08-24 à 08.27.45.png
    Capture d’écran 2019-08-24 à 08.27.45.png
    13.1 KB · Views: 58
Hi Rusty thanks for this great tutorial, unfortunately I can't get past the first step even though I set up everything correctly.

Once I finished setting up the mongo container it stops as soon as its launched and shows me this error in the log :

Error parsing command line: unrecognised option '--smallfiles'

Your help would mean a lot!
what image are you using and what version of mongo?
 
--smallfiles is no longer supported in 4.2 version. Try and remove the --smallfiles and then run the container or revert to 4.0.4 for example

Thanks to your help I got past that first step, but after setting up Rocket.Chat it only runs for 1 sec then stops, here's the log in the screenshot.
 

Attachments

  • Capture d’écran 2019-08-24 à 15.30.47.png
    Capture d’écran 2019-08-24 à 15.30.47.png
    332.8 KB · Views: 63
Well its looks like it has problems connecting to the mongo container. I will need all the configuration settings from RC in order to detect the problem.

Here you are, please tell me if you need anything else. Thank you for the support!
 

Attachments

  • Capture d’écran 2019-08-24 à 15.44.33.png
    Capture d’écran 2019-08-24 à 15.44.33.png
    78.1 KB · Views: 49
  • Capture d’écran 2019-08-24 à 15.44.49.png
    Capture d’écran 2019-08-24 à 15.44.49.png
    131.5 KB · Views: 50
  • Capture d’écran 2019-08-24 à 15.44.56.png
    Capture d’écran 2019-08-24 à 15.44.56.png
    43 KB · Views: 57
  • Capture d’écran 2019-08-24 à 15.47.49.png
    Capture d’écran 2019-08-24 à 15.47.49.png
    259.8 KB · Views: 53

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Back
Top