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)

Well done!

Regarding accessing it you need to use the URL that you have defined in your ROOT_URL variable in Docker.

If you haven't changed the parameter then it will expect access on localhost:3000 as the image presents. But ofc that will not work as localhost will in your case mean the device you are accessing it from, and there is no RC instance there.

What did you configure your ROOT_URL to?
Now, I not change ROOT_URL with default value --> I need change it to my nas IP?
 
Unless you want to have it accessible from the outside of your LAN
It still can not access on my LAN, I check the log don't see any issue
My NAS IP in LAN is 192.168.0.254 --> I access on chrome browser http://192.168.0.254:3000 it still not work.
==> http://192.168.0.254:5000 is work
I changed the URL_ROOT to http://192.168.0.254:3000
Please help me check the log and my container config.
1626964116625.png


1626964225836.png

1626964309367.png

and final, the log of Mongo
1626964633451.png
 
It still can not access on my LAN, I check the log don't see any issue
My NAS IP in LAN is 192.168.0.254 --> I access on chrome browser http://192.168.0.254:3000 it still not work.
==> http://192.168.0.254:5000 is work
I changed the URL_ROOT to http://192.168.0.254:3000
Please help me check the log and my container config.
View attachment 4038

View attachment 4039
View attachment 4040
and final, the log of Mongo
View attachment 4043
The only problem I see is the MONGO_OPLOG_URL value of the Db. It should point to the local db value. Double check it. Still not sure how it is still working and starting the server that way.

Not sure if your container is actually working as it should or is this the problem. Try and alter it and let’s see if you are still unable to connect.

Also, do you have any other container running so far?
 
The only problem I see is the MONGO_OPLOG_URL value of the Db. It should point to the local db value. Double check it. Still not sure how it is still working and starting the server that way.

Not sure if your container is actually working as it should or is this the problem. Try and alter it and let’s see if you are still unable to connect.

Also, do you have any other container running so far?
Thanks for your support, I change the value of MONGO_OPLOG_URL it work now.
 
Hi Rusty - after much trial and error I got the containers running on my system but I can't connect RC to the server. I keep getting no valid server at the URL. Attached is the setting I've used. Can anyone help?
 

Attachments

  • RC Server Issue pic 3.PNG
    RC Server Issue pic 3.PNG
    23.7 KB · Views: 8
  • RC Server Issue pic 2.PNG
    RC Server Issue pic 2.PNG
    9.9 KB · Views: 9
  • RC Server Issue pic 1.PNG
    RC Server Issue pic 1.PNG
    13.1 KB · Views: 9
  • RC Server Issue pic 4.PNG
    RC Server Issue pic 4.PNG
    10 KB · Views: 9
  • RC Server Issue pic 5.PNG
    RC Server Issue pic 5.PNG
    29.3 KB · Views: 9
  • RC Server Issue pic Log.PNG
    RC Server Issue pic Log.PNG
    39.2 KB · Views: 9
Hi Rusty - after much trial and error I got the containers running on my system but I can't connect RC to the server. I keep getting no valid server at the URL. Attached is the setting I've used. Can anyone help?
Guessing you are running this behind a reverse proxy or in lan? Also if you are using official apps (ios/android) you will need to have it configured using an https url with a valid cert.

Also, if you are going behind reverse, make sure to have websocket configured.

So from what client are you testing this and how?
 
Guessing you are running this behind a reverse proxy or in lan? Also if you are using official apps (ios/android) you will need to have it configured using an https url with a valid cert.

Also, if you are going behind reverse, make sure to have websocket configured.

So from what client are you testing this and how?
Trying to run it over my LAN to make sure I've got everything set up correctly with Docker (it's my first time using Docker). Been doing everything on Synology's web software and trying to connect with RC's desktop app on my Windows PC.

After this, I'll set up a reverse proxy and attach to my custom domain name to get my mobile apps set-up.
 
Trying to run it over my LAN to make sure I've got everything set up correctly with Docker (it's my first time using Docker). Been doing everything on Synology's web software and trying to connect with RC's desktop app on my Windows PC.

After this, I'll set up a reverse proxy and attach to my custom domain name to get my mobile apps set-up.
Almost certain the desktop app will not allow http connections as well.

Are you trying using http://your_nas_ip:3000? What exact error do you get?
 
99% it's an HTTPS problem. Considering that your instance is running just change the ROOT_URL and configure it to an HTTPS URL with a valid certificate (using reverse proxy for example), then just rerun it. Should fix it. Also, don't forget to configure websocket for your reverse host entry.
 
99% it's an HTTPS problem. Considering that your instance is running just change the ROOT_URL and configure it to an HTTPS URL with a valid certificate (using reverse proxy for example), then just rerun it. Should fix it. Also, don't forget to configure websocket for your reverse host entry.
Okay will do! Time to get on that reverse proxy then. Thanks for the help.
 
Rusty updated Rocket.Chat - SLACK alternative (with MongoDB as backend) with a new update entry:

RC and Mongo docker-compose examples

Rocket.Chat

YAML:
version: '3.1'
services:
  rocketchat:
    image: rocketchat/rocket.chat:latest
    container_name: rocketchat
    network_mode: "bridge"
    ports:
      - "3000:3000"
    volumes:
      - /volume1/docker/rocketchat:/app/uploads
    environment:
      MONGO_OPLOG_URL: mongodb://root:mongorootpass@NAS_IP_ADDRESS:27017/local?authSource=admin
      MONGO_URL: mongodb://root:mongorootpass@NAS_IP_ADDRESS:27017/rocketchatdb?authSource=admin...

Read the rest of this update entry...
 

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!

Back
Top