January 11, 20242 yr 1 hour ago, 9BAR said: So, rocket.chat's putting more and more features behind their enterprise paywall (I mean, user roles are now a paid feature?!). Now, with their arbitrary 25-user limit for the community edition, my group has decided to move on. I've begun to migrate to Matrix. We've been using rocket.chat for close to four years, and I'm trying to make the transition as painless as possible. Has anyone had any luck federating their rocket.chat instance with their Matrix home server on Unraid? There's a built-in Matrix bridge -- I'm wondering what that configuration would look like for an RC and Matrix server hosted on the same Unraid machine. Alternatively, a method to import rocket.chat's chat history into Matrix. I know that's probably a tall order.
May 13, 20242 yr On 1/11/2024 at 12:39 PM, 9BAR said: So, rocket.chat's putting more and more features behind their enterprise paywall (I mean, user roles are now a paid feature?!). Now, with their arbitrary 25-user limit for the community edition, my group has decided to move on. I've begun to migrate to Matrix. We've been using rocket.chat for close to four years, and I'm trying to make the transition as painless as possible. Has anyone had any luck federating their rocket.chat instance with their Matrix home server on Unraid? There's a built-in Matrix bridge -- I'm wondering what that configuration would look like for an RC and Matrix server hosted on the same Unraid machine. Federation is a premium feature. Just the icing on the cake.
May 19, 20251 yr On 1/29/2025 at 6:31 AM, Kulis said: Does anyone have instructions on how to install Rocket.chat in 2025? I just finished adding / fixing this to unriad v7 due to some concerns to run a discord like chat... I just updated and added the Maintainers official dockers to the Unraid CA. and I decided to go host for database, as that is my norm when running database on unraid... I decided to go custom ipvlan/macvlan for rocket chat. or you can go with rocket.chat docker compose... with the docker compose plugin... https://docs.rocket.chat/docs/deploy-with-docker-docker-compose Please install the MongoDB-Rocketchat as this will install v6 of mongo that is compatabile with latest server version per their github./docs.. You will need to wait and make sure mongdb is full initialized. It is best to add a replica key and or add a mongdb root password. (my template ships with a password less) enviroment variables on in the overview and additional requirements! it more getting the mongdb connection line in rocket chat... rare as mong can silety fial check docker logs... May need mong comand run to make sure its inatlized... docker console while running mongosh rs.initiate({ _id: "rs0", members: [ { _id: 0, host: "localhost:27017" } ] }) to fix any initialization issues... if you want a passwrod protected mongdb then you will need to add 2 key variables so at bottom of template add: MONGODB_ROOT_PASSWORD and MONGODB_REPLICA_SET_KEY and updating your 2 keys in the rocketcaht docker to conect to the mongodb Tying to make it as close to a one click install and workig out of the box as possible as the other mongdb ca required other stuff to make it function with rocket chat now. Rocket chat is free for under 50 users for text... https://www.rocket.chat/pricing
May 20, 20251 yr Seeing as this is multi docked meaning its a stack and need to run multiple dockers to be working... so lets look at docker compose...I assume you already have the docker compose plugin installed...I assume the default data path...step 1 pre make the unraid docker compose stack..# Run this on your Unraid terminalmkdir -p /mnt/user/appdata/rocketchat/mongodbmkdir -p /mnt/user/appdata/rocketchat/rocketchatstep 2 make a new stack.set a name and chose /mnt/user/appdata/rocketchat as the location for the env / docker compose file to exist.step 3 edit the stack*This will use a env file and a copose file...Compose file:Foling the rocket.chat maintainers.. https://docs.rocket.chat/docs/deploy-with-docker-docker-composenew forum made it harder to do iline past of code... code link auto braek yaml syntaxing....-As unraid has some small edits and feature that are nice in a compose for unraid... web ui, pictures at top, autofill icons adn web ui.... etc...save the compose and hit ok-Note with the unraid updated compose edits, the data is already filled in for you...This compose will auto make a new docker network bridge I've set the port to be unraid ip at port 60080 to no cause conflicts with other existing dockers...<inline code of compose file (may now be an attachment moving forward as I don't get the box before hand anymore>We also have a ENV file we need to use... not the comose is calling info and not actually filled in.... the env file has that data...so edit stack env file...Here is where we can change and set data such as the ports hostname and compose environment variables called in the docker compose file...<inline code of ".env" file (may now be an attachment moving forward as I don't get the box before hand anymore>with that saved... we are now ready to compose up and start the docker......you will now see 2 docker at the top in the docker tab of the web ui...go to the web ui and complete your first time configurations...
May 20, 20251 yr .envdocker-compose.ymlcompose file: yaml spacing... new forum inline code sucks....#version: "3.8"services: rocketchat: image: registry.rocket.chat/rocketchat/rocket.chat:${RELEASE} container_name: rocketchat restart: always networks: rocketchat_net: ipv4_address: 172.20.0.10 environment: MONGO_URL: "mongodb://${MONGODB_ADVERTISED_HOSTNAME}:${MONGODB_INITIAL_PRIMARY_PORT_NUMBER}/rocketchat?replicaSet=${MONGODB_REPLICA_SET_NAME}" MONGO_OPLOG_URL: "mongodb://${MONGODB_ADVERTISED_HOSTNAME}:${MONGODB_INITIAL_PRIMARY_PORT_NUMBER}/local?replicaSet=${MONGODB_REPLICA_SET_NAME}" ROOT_URL: ${ROOT_URL} PORT: ${PORT} DEPLOY_METHOD: docker ports: - "${HOST_PORT}:${PORT}" volumes: - /mnt/user/appdata/rocketchat/rocketchat:/app/uploads depends_on: - mongodb labels: net.unraid.docker.webui: "http://[IP]:[PORT:60080]" net.unraid.docker.icon: "https://raw.githubusercontent.com/bmartino1/unraid-docker-templates/refs/heads/main/images/rocketchat.png" folder.view: "rocketchat" net.unraid.docker.managed: "composeman" mongodb: image: bitnami/mongodb:${MONGODB_VERSION} container_name: mongodb restart: always networks: rocketchat_net: ipv4_address: 172.20.0.11 volumes: - ${MONGODB_HOST_PATH}:/bitnami/mongodb environment: MONGODB_REPLICA_SET_MODE: primary MONGODB_REPLICA_SET_NAME: ${MONGODB_REPLICA_SET_NAME} MONGODB_PORT_NUMBER: ${MONGODB_PORT_NUMBER} MONGODB_INITIAL_PRIMARY_HOST: ${MONGODB_INITIAL_PRIMARY_HOST} MONGODB_INITIAL_PRIMARY_PORT_NUMBER: ${MONGODB_INITIAL_PRIMARY_PORT_NUMBER} MONGODB_ADVERTISED_HOSTNAME: ${MONGODB_ADVERTISED_HOSTNAME} MONGODB_ENABLE_JOURNAL: true ALLOW_EMPTY_PASSWORD: yes labels: net.unraid.docker.icon: "https://raw.githubusercontent.com/bmartino1/unraid-docker-templates/refs/heads/main/images/rocketchatmongo.png" folder.view: "rocketchat" net.unraid.docker.managed: "composeman"networks: rocketchat_net: driver: bridge ipam: config: - subnet: 172.20.0.0/16 gateway: 172.20.0.1env file# Rocket.Chat configRELEASE=latestPORT=3000 # Port inside containerHOST_PORT=60080 # Port exposed on Unraid hostBIND_IP=0.0.0.0 # Bind to all interfaces (or Unraid host IP if preferred)ROOT_URL=http://rocketchat.local:60080# MongoDB configMONGODB_VERSION=6.0MONGODB_HOST_PATH=/mnt/user/appdata/rocketchat/mongodbMONGODB_REPLICA_SET_NAME=rs0MONGODB_INITIAL_PRIMARY_HOST=mongodbMONGODB_INITIAL_PRIMARY_PORT_NUMBER=27017MONGODB_PORT_NUMBER=27017MONGODB_ADVERTISED_HOSTNAME=mongodb# Traefik (optional)#DOMAIN=rocketchat.local#[email protected]
May 20, 20251 yr With the Maintainers compose file out of the way, I just need to update the docker CA templates to reflect this a bit...As with adding tail scale integration and/or constricting a docker stack that requires more than 1 docker to function. Using the CA template can be a pain.Some setting do transfer nicely from building the docker cli and some option doesn't exit such as the docker compose depends on to make sure xyz is running before this docker runs to not cascade and cause data issues...almost all are a docker network misconfiguration and how xyz talks to docker xyz....so in order to use the CA over the docker compose. as mentioned above.step 1go to the unraid CA and install the mongdb maintainers docker image...note the requirement!as there are some small hiccups to make a template for all following the CA best practices guide.I chose to use docker network host... as seen in the compose able that used docker bridge... You can use bridge, custom ip with the macvlan/ipvlan ip etc...Just not this may change ip/hostname needed latter that is needed to make the rocket.chat dockers mongo database connection...I went with host to guarantee a ip for documentation as i will use unraids IP in my case my unraid is static set to 192.168.2.251this means this docker when installed will be at 192.168.2.251 at its database port the container is running by default mongodb uses port 27017 this port can be changed with docker variables as other docker stack may already have a MongoDB running for other..So I have to make large assumptions when making CA apps to make one click install and it works for others... This may also go against the best security practices as usually you would set a root mongdb password which would change the mongdb line need to connect to the mongdb with in the rocket.chat database...PLEASE READ! and follow the guide or not at all Your mongdb connection have been outlined for a quick overview, not how you should connect to it between dockers! You have been warned!!!As explained above its best to add additional docker variables and turn off passwordless connection to MongoDB. due to guide write ease of 1 click, I will not go over that... go ask ai if you need help construing your network and MongoDB connection... It's explained in rocket chat docs and noted in the additional requirement breakdown!Now that the acknowledgement and warning is out of the way...There is a semi know issue with creating a mongdb. Assuming unraid default data path /mnt/user/appdata<docekrname>Their is a appdata path in the template, and we need to make and fix file permission otherwise the docker log will error permission errormkdir /mnt/user/appdata/mongodb/chmod 777 -R /mnt/user/appdata/mongodb/so we need to open the web terminal inside the docker following the additional requirements!this will fix the permission issue setting the unriad docker default permissionNext review the docker network... (see signature going over docker networks to learn more on that)For me I like to run database at the host level. this guarantees vlan and other cross network traffic can talk to the database.I also usual go advance to see additional advance settings...note the extra parmthe hostname should be a FQDN in my case my FQDN would be mongodb.home.arpa due to tailscale some docker may require additional internet dns to connect and access resources. so I added the hostname and dns options to the extra parmThey are optional as in the end I prefer static IP and to know that If i go this ip i reach this docker/services...Note the template is set to use this as the default hostname for other variables... we are using bitnami mongdb docker imagehttps://github.com/bitnami/containers/tree/main/bitnami/mongodbAdditional docker variable to set mongdb setting exist. as the other mongdb dockers have issue making the database need for rocket.chat to run...the unraid CA template ships with a passwordless setup... As I'm just converting the working docker compose into a Docker run CLI and using the unraid docker template to construct the docker cli to make the docker and function...NOTE the extra parm hostname IF that is changes (AND IT SHOULD!) you need to update the hostname in the template options...so I would set initial primary host and advertised hostname to mongodb.home.arpa my FQDN for my network ... some default would be generated by your router and could be .local, .localdomain, .lan.... As mentioned earlier, the Mongdb app data config... we needed to create the folder beforehand and make sure unraid docker safe permission are applied...as mentioned earlier in the forum sometimes even with these setting you will get a error database not initialized. Yellow text will keep spamming the log...so you will need to force a initializationwith the database initialized... green /white text log not being spammed and stops... the docker is full functional and ready to connect...as mentioned before... my unraid ip is 192.168.2.251 so i now have mongdb at 192.168.2.251we have 2 mongodb url that need constructed for rocket chat..MONGO_OPLOG_URL with no template changes would result in a connection line of mongodb://mongodb:27017/local?replicaSet=rs0andmongo URL with no template changes would result in a connection line of mongodb://mongodb:27017/rocketchat?replicaSet=rs0Info Breakdown example:mongodb:// hostname / IP address of unraid if using hostmode: /local?replicaSet= so my connection line is mongodb://192.168.2.251:27017/rocketchat?replicaSet=rs0as its all about getting this mongdb and how you can conect to the MongoDB within rocetchat!so now that you have a running instance of mongdb setup and running, lets look at the rocket chat CAwith advance togle note the extra parm... These are optional but are needed for use with tailscale and helps with root URLI decided to go custom br0 so I set lan idenity this mean rocekt chat will be at 192.168.2.240 so I can port forward, tailscale, and easily port forward rocket chat for public use if needed... also helps set lan identity for reverse proxies such as nginx proxy manger...you will note 192.168.x.xTHIS IS ON PURPOSE!As you need to fill in the necessary data...so mongo for me is my unraid ip 192.168.2.251rocket chat url will become 192.168.2.240red token if you went paid for other features... first startup with making admin account will also go over other setting and configurations..its all on how you setup your docker networks to have dockers talk...review the post i made on the different docker networks:https://forums.unraid.net/topic/188695-docker-network-issue/#findComment-1541042review the rocket.chat doc...https://docs.rocket.chat/docs/mongodb-configurationand to watch the github and rocket.chat upgrade cyclehttps://docs.rocket.chat/docs/supported-mongodb-versionsCurrently, rocket chat v7.3 is compatible with mongdb v6I can't make it any simpler it all on how you setup your docker networks and build your mongdb connection line...Please read the DOCs: https://docs.rocket.chat/docs/mongodb-uri-authentication
May 22, 20251 yr so mongdb may need some console commands to get working...first initalize the mongdbwhile runnign console into the mong db docker:mongoshrs.initiate({ _id: "rs0", members: [ { _id: 0, host: "localhost:27017" } ] })then giving that i'm going hostname/ip we may need to tell the database to use the ip and/or hostname...IN my example I'm using a docker custom bridge ip so i'm static set rocket.chat to 192.168.2.240I need to allow the mongdb to connect via the ipthis makes the URL and oplogURL to thisso lets fix the mondb and edit the config...docker console comands set to your ip!mongoshcfg = rs.conf()cfg.members[0].host = "192.168.2.251:27017"rs.reconfig(cfg, {force: true})rs.status()then update your temapte rocket.chat mongo URL lines MONGO_URL mongodb://192.168.2.251:27017/rocketchat?replicaSet=rs0MONGO_OPLOG_URLmongodb://192.168.2.251:27017/local?replicaSet=rs0
September 21, 2025Sep 21 its easier to use a compose for this....Volume bind mount needs folder to exist first.mkdir -p /mnt/user/appdata/rocketchat/mongodbCompose file #version: "3.9" name: rocketchat services: rocketchat: image: ${IMAGE:-registry.rocket.chat/rocketchat/rocket.chat}:${RELEASE:-latest} restart: always depends_on: - mongodb environment: ROOT_URL: ${ROOT_URL:-http://localhost} PORT: ${PORT:-3000} DEPLOY_METHOD: docker DEPLOY_PLATFORM: compose # REG_TOKEN is optional for Cloud registration; leave blank if not using REG_TOKEN: ${REG_TOKEN:-} # Required: MongoDB RS connection string MONGO_URL: ${MONGO_URL:-mongodb://mongodb:27017/rocketchat?replicaSet=rs0} # No TRANSPORTER set => monolith mode (no NATS) ports: - "${BIND_IP:-0.0.0.0}:${HOST_PORT:-3000}:${PORT:-3000}" labels: net.unraid.docker.webui: "http://[IP]:[PORT:3000]" net.unraid.docker.icon: "https://raw.githubusercontent.com/bmartino1/unraid-docker-templates/refs/heads/main/images/rocketchat.png" folder.view: "rocketchat" net.unraid.docker.managed: "composeman" #"com.centurylinklabs.watchtower.enable=true" networks: - rocketchat mongodb: image: docker.io/bitnami/mongodb:${MONGODB_VERSION:-6.0} restart: always environment: # Single-node replica set so Rocket.Chat can start MONGODB_REPLICA_SET_MODE: ${MONGODB_REPLICA_SET_MODE:-primary} MONGODB_REPLICA_SET_NAME: ${MONGODB_REPLICA_SET_NAME:-rs0} MONGODB_PORT_NUMBER: ${MONGODB_PORT_NUMBER:-27017} MONGODB_INITIAL_PRIMARY_HOST: ${MONGODB_INITIAL_PRIMARY_HOST:-mongodb} MONGODB_INITIAL_PRIMARY_PORT_NUMBER: ${MONGODB_INITIAL_PRIMARY_PORT_NUMBER:-27017} MONGODB_ADVERTISED_HOSTNAME: ${MONGODB_ADVERTISED_HOSTNAME:-mongodb} MONGODB_ENABLE_JOURNAL: ${MONGODB_ENABLE_JOURNAL:-true} # For quick start; replace with proper root/password secrets later ALLOW_EMPTY_PASSWORD: ${ALLOW_EMPTY_PASSWORD:-yes} volumes: - mongodb_data:/bitnami/mongodb:rw ports: - "${MONGODB_BIND_IP:-127.0.0.1}:${MONGODB_PORT_NUMBER:-27017}:${MONGODB_PORT_NUMBER:-27017}" labels: net.unraid.docker.icon: "https://raw.githubusercontent.com/bmartino1/unraid-docker-templates/refs/heads/main/images/rocketchatmongo.png" folder.view: "rocketchat" net.unraid.docker.managed: "composeman" #"com.centurylinklabs.watchtower.enable=true" networks: - rocketchat networks: rocketchat: volumes: # Unraid bind mount into appdata mongodb_data: driver: local driver_opts: type: none device: /mnt/user/appdata/rocketchat/mongodb o: bind env file:# Web #ROOT_URL=http://localhost ROOT_URL=http://192.168.1.254:3000 #set me to unirad ip address HOST_PORT=3000 PORT=3000 BIND_IP=0.0.0.0 # Rocket.Chat image IMAGE=registry.rocket.chat/rocketchat/rocket.chat RELEASE=latest REG_TOKEN= # Mongo connection (single-node RS) MONGO_URL=mongodb://mongodb:27017/rocketchat?replicaSet=rs0 # MongoDB (bitnami) basics MONGODB_VERSION=6.0 MONGODB_BIND_IP=127.0.0.1 MONGODB_PORT_NUMBER=27017 MONGODB_REPLICA_SET_MODE=primary MONGODB_REPLICA_SET_NAME=rs0 MONGODB_INITIAL_PRIMARY_HOST=mongodb MONGODB_INITIAL_PRIMARY_PORT_NUMBER=27017 MONGODB_ADVERTISED_HOSTNAME=mongodb MONGODB_ENABLE_JOURNAL=true ALLOW_EMPTY_PASSWORD=yes for a quick bare min off and running
December 13, 2025Dec 13 On 5/19/2025 at 3:30 PM, bmartino1 said:I just finished adding / fixing this to unriad v7 due to some concerns to run a discord like chat... I just updated and added the Maintainers official dockers to the Unraid CA. and I decided to go host for database, as that is my norm when running database on unraid...I decided to go custom ipvlan/macvlan for rocket chat.or you can go with rocket.chat docker compose...with the docker compose plugin...https://docs.rocket.chat/docs/deploy-with-docker-docker-composePlease install the MongoDB-Rocketchat as this will install v6 of mongo that is compatabile with latest server version per their github./docs..You will need to wait and make sure mongdb is full initialized.It is best to add a replica key and or add a mongdb root password.(my template ships with a password less) enviroment variables on in the overview and additional requirements! it more getting the mongdb connection line in rocket chat...rare as mong can silety fial check docker logs... May need mong comand run to make sure its inatlized...docker console while runningmongoshrs.initiate({ _id: "rs0", members: [ { _id: 0, host: "localhost:27017" } ] }) to fix any initialization issues... if you want a passwrod protected mongdb then you will need to add 2 key variablesso at bottom of template add:MONGODB_ROOT_PASSWORDandMONGODB_REPLICA_SET_KEY and updating your 2 keys in the rocketcaht docker to conect to the mongodb Tying to make it as close to a one click install and workig out of the box as possibleas the other mongdb ca required other stuff to make it function with rocket chat now.Rocket chat is free for under 50 users for text...https://www.rocket.chat/pricing I've added the passwords to the mongodb:// like is listed here but am getting an error that the root user does not exist on the database when I start up rocket chat, do you know what may be causing that error?it works fine if I set the allow empty password variable to yes and remove the username and password{"t":{"$date":"2025-12-13T06:59:07.117+00:00"},"s":"I", "c":"ACCESS", "id":5286307, "ctx":"conn36","msg":"Failed to authenticate","attr":{"client":"10.69.69.100:56952","isSpeculative":true,"isClusterMember":false,"mechanism":"SCRAM-SHA-256","user":"root","db":"rocketchat","error":"UserNotFound: Could not find user \"root\" for db \"rocketchat\"","result":11,"metrics":{"conversation_duration":{"micros":283,"summary":{"0":{"step":1,"step_total":2,"duration_micros":267}}}},"doc":{"driver":{"name":"nodejs|Meteor","version":"6.16.0|[email protected]"},"platform":"Node.js v22.16.0, LE","os":{"name":"linux","architecture":"x64","version":"6.12.54-Unraid","type":"Linux"},"env":{"container":{"runtime":"docker"}}},"extraInfo":{}}} Edited December 13, 2025Dec 13 by epilot5280
December 13, 2025Dec 13 12 hours ago, epilot5280 said:I've added the passwords to the mongodb:// like is listed here but am getting an error that the root user does not exist on the database when I start up rocket chat, do you know what may be causing that error?it works fine if I set the allow empty password variable to yes and remove the username and password{"t":{"$date":"2025-12-13T06:59:07.117+00:00"},"s":"I", "c":"ACCESS", "id":5286307, "ctx":"conn36","msg":"Failed to authenticate","attr":{"client":"10.69.69.100:56952","isSpeculative":true,"isClusterMember":false,"mechanism":"SCRAM-SHA-256","user":"root","db":"rocketchat","error":"UserNotFound: Could not find user \"root\" for db \"rocketchat\"","result":11,"metrics":{"conversation_duration":{"micros":283,"summary":{"0":{"step":1,"step_total":2,"duration_micros":267}}}},"doc":{"driver":{"name":"nodejs|Meteor","version":"6.16.0|[email protected]"},"platform":"Node.js v22.16.0, LE","os":{"name":"linux","architecture":"x64","version":"6.12.54-Unraid","type":"Linux"},"env":{"container":{"runtime":"docker"}}},"extraInfo":{}}}I do not. I kinda abanded the project due to issues with MongoDB and an ability to share good working version to use docker... how to get it up and working reliably... has been a challenge... its has and will always be a issue with commands to mongdb to get it working...My CA unraid templates have not been maintained nor checked on this in a while (so i'm not sure if what is posted will work...) and was more to bring the dockers back into unraid for template editing to futz with for other users that build and use this on unraid...For me to go back and redo this... I would essential have to make and monitor my on mongodb database9Which i nether have the time nor the ability to allocate to this) with custom scritps to fix, montitor and do zxy... where it was neither worth my timer pressuring nor fighting to get it working...IDK also, what changed and stopped following rocket chat due to there new subscription requirements and there other weird requirements to set one up. The best I can do is direct you to earlier in the forum with my mong db commands to fix the mongdb... The templats and OG post when I tried to resurrect this application on how to setup and run mongdb are needed from the earlier in post. I can get it working for myself... (As I know some of the inner working due to rocket chat and having access to other support channels and data from mongodb and rocket chat themselves... But that doesn't mean its stable running like this on unriad.. nor should be ran the way due to last communications form rocket chat devs... its is. Last Comunciations with rocket chat, they didn't want this to be contanierzed and in a docker env. They rather you install it mongo and others in a liunx env. so vm/lxc...ATM, My focus atm is more on immich and not this project. Sorry I can't help. to use there supported via github docekr version (teh rocket chat app it self...)https://github.com/RocketChat/rocketchat-compose/blob/main/compose.ymlI would move the project into compose and not unraid CA docker splitting due to needing and setingup mongo and a gurantee if passed with theses setting and data it will work reliably..Please review rocket chats documentation... again The CA dockers in my repo was only to help bring them into Unraid and not a stable working model due to mongodb configurations... at this time....https://www.rocket.chat/installhttps://docs.rocket.chat/docs/additional-deployment-methodsmore on mongo as I understand it the rocketchat docker in in debain as such following the vm/lxc for mongodb setup...https://docs.rocket.chat/v1/docs/deploy-on-debian#set-up-mongodbas I'm still waitng on mongdb to get back to me on a good way to deply and set these via docker run (which is how unraids CA template generates the dockers in unraid... CA temaptles construct the docker run line and execute them....your issues appears to be stemming from a missing option data or mongodb configuration. IDK mongodb enough to assist further. and would point you towards dev recommendation of a VM / ICH777 debain LXC.
January 6Jan 6 I've just updated the templates and some work to make a rocket.chat and mongdb AIO all in one tempate for unraid for easy 1 click run and installthis is due to issues with setting up the mongdb database that is needed for rocket.chat.I would still recoend running your own mongdb and the rocket.chat docker. https://github.com/bmartino1/rocket.chat/tree/main/unraidAIO
January 7Jan 7 10 hours ago, bmartino1 said:I've just updated the templates and some work to make a rocket.chat and mongdb AIO all in one tempate for unraid for easy 1 click run and installthis is due to issues with setting up the mongdb database that is needed for rocket.chat.I would still recoend running your own mongdb and the rocket.chat docker. https://github.com/bmartino1/rocket.chat/tree/main/unraidAIOIm having issues getting this running. I have attached my install settings. When I try to open up the logs it just opens and closes right away. Here is the logs when I access them via SSH. I also noticed that the mongo folder has nothing it in (Appdata). root@Klauss:~# docker logs Rocket.ChatAIO [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 15 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 13 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 13 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 13 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. [AIO] Starting MongoDB... about to fork child process, waiting until server is ready for connections. forked process: 14 ERROR: child process failed, exited with 1 To see additional information in this output, start without the "--fork" option. Edited January 7Jan 7 by rh535
January 7Jan 7 read the adational notes. you ran somting inteh continer. this works out of the box...you dind't set teh corect chat url at first run anda fo bared the mongo db you MUST DELTE THE FOLDER and let the AIO mange Mongdb...
January 7Jan 7 YOU MUST FIRST RUN SET THE CORECT IP for the ROOT_URL the connection IP to access your Rocket.chat Web interface!!! Otherwise you will need to delete the mongdb folder and start again!using bridge: i use my unraid ip: ...so you messede up as it writes the root url for guarantee connections...I prefer to manualy make my directory before hand know where the data is stored...root@BMM-Tower:/mnt/user/appdata# mkdir -p /mnt/user/appdata/rocket.chat/mongdb/root@BMM-Tower:/mnt/user/appdata# ls /mnt/user/appdata/rocket.chat/mongdb/root@BMM-Tower:/mnt/user/appdata# expected docker log:############################################strict mode: use allowUnionTypes to allow union type keyword at "#/properties/count" (strictTypes)strict mode: use allowUnionTypes to allow union type keyword at "#/properties/offset" (strictTypes)strict mode: missing type "object" for keyword "additionalProperties" at "#" (strictTypes)strict mode: missing type "object" for keyword "properties" at "#" (strictTypes)strict mode: missing type "object" for keyword "required" at "#/oneOf/0" (strictTypes)strict mode: missing type "object" for keyword "required" at "#/oneOf/1" (strictTypes)Wed, 07 Jan 2026 19:03:42 GMT body-parser deprecated undefined extended: provide extended option at app/app.js:135830:64Wed, 07 Jan 2026 19:03:42 GMT body-parser deprecated undefined extended: provide extended option at app/app.js:135831:57(node:1) NOTE: The AWS SDK for JavaScript (v2) is in maintenance mode.SDK releases are limited to address critical bug fixes and security issues only.Please migrate your code to use AWS SDK for JavaScript (v3).For more information, check the blog post at https://a.co/cUPnyil(Use `node --trace-warnings ...` to show where the warning was created)strict mode: missing type "object" for keyword "additionalProperties" at "#" (strictTypes)[AIO] Starting MongoDB...about to fork child process, waiting until server is ready for connections.forked process: 14child process started successfully, parent exiting[AIO] Waiting for MongoDB...[AIO] Initializing replica set...test> ... ... ... { ok: 1 }test> [AIO] Starting Rocket.Chat on 0.0.0.0:3000 ...LocalStore: store created at LocalStore: store created at LocalStore: store created at {"level":40,"time":"2026-01-07T19:03:48.942Z","pid":1,"hostname":"rocketchataio","name":"VoIPAsteriskService","msg":"Voip is not enabled. Cant start the service"}[2026-01-07T19:03:57.344Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/BROKER: Moleculer v0.14.35 is starting...[2026-01-07T19:03:57.345Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/BROKER: Namespace: <not defined>[2026-01-07T19:03:57.345Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/BROKER: Node ID: a86c9afd-d561-42ab-a494-c656fcfa91d9[2026-01-07T19:03:57.345Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/REGISTRY: Strategy: RoundRobinStrategy[2026-01-07T19:03:57.346Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/REGISTRY: Discoverer: LocalDiscoverer[2026-01-07T19:03:57.347Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/BROKER: Serializer: EJSONSerializer[2026-01-07T19:03:57.350Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/BROKER: Validator: FastestValidator[2026-01-07T19:03:57.352Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/BROKER: Registered 13 middleware(s).[2026-01-07T19:03:57.352Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/BROKER: Transporter: TcpTransporter{"level":51,"time":"2026-01-07T19:03:57.364Z","pid":1,"hostname":"rocketchataio","name":"DatabaseWatcher","msg":"Using change streams"}{"level":30,"time":"2026-01-07T19:03:57.381Z","pid":1,"hostname":"rocketchataio","name":"homeserver","name":"DatabaseConnectionService","msg":"Connected to MongoDB database: rocketchat"}{"level":30,"time":"2026-01-07T19:03:57.381Z","pid":1,"hostname":"rocketchataio","name":"homeserver","msg":"EventEmitterService: External emitter injected"}ufs: temp directory created at "/tmp/ufs"+--------------------------------------------------+| SERVER RUNNING |+--------------------------------------------------+| || Rocket.Chat Version: 7.13.2 || NodeJS Version: 22.21.0 - x64 || MongoDB Version: 7.0.28 || MongoDB Engine: wiredTiger || Platform: linux || Process Port: 3000 || Site URL: http://192.168.2.248:3000 || ReplicaSet OpLog: Enabled || Commit Hash: 72fe118ea7 || Commit Branch: HEAD || |+--------------------------------------------------+[2026-01-07T19:03:58.363Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/TRANSIT: Connecting to the transporter...[2026-01-07T19:03:58.364Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/TRANSPORTER: TCP server is listening on port 45477[2026-01-07T19:03:58.364Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/TRANSPORTER: UDP Discovery is disabled.[2026-01-07T19:03:58.364Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/TRANSPORTER: TCP Transporter started.[2026-01-07T19:03:58.869Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/REGISTRY: '$node' service is registered.[2026-01-07T19:03:58.870Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/REGISTRY: 'matrix' service is registered.[2026-01-07T19:03:58.870Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/$NODE: Service '$node' started.[2026-01-07T19:03:58.870Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/MATRIX: Service 'matrix' started.[2026-01-07T19:03:58.870Z] INFO a86c9afd-d561-42ab-a494-c656fcfa91d9/BROKER: ✔ ServiceBroker with 2 service(s) started successfully in 507ms.###################thats it finish the wizard and setup for rocket chat...I can't make it any easier... Iv'be seen no other mongdb issues and a problem after wizzard setup to use the platform... full features require paid support form rocket.chat...
January 7Jan 7 so i can only asume you have fubared your database:so you must deelte this folder and start again...I can manually reproduced due to contains restart and how mongdb loads slower then rocket.chat I am implementing a fix to the docker image atm. Edited January 7Jan 7 by bmartino1 found / made reporduceable error.
January 7Jan 7 Just to add to this I have followed what you have said and get the same result as rh535.. I didnt need to change the port for my install either. I tried it twice, deleting all files before trying the 2nd time with the same results. Literally identical results to rh535.Essentially from the first pull I just inputted my unraid ip address where it states. bridge mode was set as default as was everything else. Always the same result.
January 8Jan 8 AIO has been heavily changed and updated due to recent issues and chagnes to rocket.chat lattest image....There is a new CA updated new template options...Again the seen before forks issues is a docker carsh restart loading somnthign before rocket.chat...That I can manual triger but don't experience.... any atempts to use the image today have been heavily redone... mutiple times thorugh out the day tags, images and other have beendone so earlier testing is not applicable...the AIO will install smtp(postfix), mongdb v8, the lastest version of rocket.chat form there github... dependacy per npm javascript node22 deno and metora the backbone framework to run the bare min to get up and working. testing have shown no issues even with a docker restart crash...Example of a working AIO instance after final testing and data pushed:Docker log example:[AIO] Starting Postfix......done.[AIO] Sending local SMTP test email...[AIO] Starting NATS...[AIO] Starting MongoDB...[AIO] Waiting for MongoDB socket...[AIO] Replica set already initialized.[AIO] Starting Rocket.Chat on 0.0.0.0:3000 ...LocalStore: store created atLocalStore: store created atLocalStore: store created at{"level":40,"time":"2026-01-08T00:32:31.079Z","pid":7,"hostname":"rocketchataio","name":"VoIPAsteriskService","msg":"Voip is not enabled. Cant start the service"}{"level":51,"time":"2026-01-08T00:32:31.130Z","pid":7,"hostname":"rocketchataio","name":"Migrations","msg":"Not migrating, already at version 318"}NetworkBroker started successfully.{"level":51,"time":"2026-01-08T00:32:33.760Z","pid":7,"hostname":"rocketchataio","name":"License","msg":"License installed","version":"3.0","hash":"VrKgWnx0"}{"level":30,"time":"2026-01-08T00:32:33.778Z","pid":7,"hostname":"rocketchataio","name":"homeserver","name":"DatabaseConnectionService","msg":"Connected to MongoDB database: rocketchat"}{"level":30,"time":"2026-01-08T00:32:33.778Z","pid":7,"hostname":"rocketchataio","name":"homeserver","msg":"EventEmitterService: External emitter injected"}+--------------------------------------------------------------+| SERVER RUNNING |+--------------------------------------------------------------+| || Rocket.Chat Version: 7.13.2 || NodeJS Version: 22.21.0 - x64 || MongoDB Version: 8.0.17 || MongoDB Engine: wiredTiger || Platform: linux || Process Port: 3000 || Site URL: http://192.168.2.248:3000 || ReplicaSet OpLog: Not required (running micro services) || Commit Hash: 72fe118ea7 || Commit Branch: HEAD || |+--------------------------------------------------------------+Proof of concept:THE AIO IS FOR FRESH INSTALLS ONLY!*Warning no proxy / https is in the image! this is due to other proxy integrations for use on unraid... tests where with browser Google Chrome where the setup wizard and registration worked flawlessly...However, new developments to rocket.chat may requires http / proxy setups to use now... I can still use the applicaiotn as seen above with http and by using an expermiental chrome flag by editing and adding to chrome flag.chrome://flags/#unsafely-treat-insecure-origin-as-secureI highly recommend deleting the mongdb folder and try again with the latest pushed docker tag image. Future updates / Release should not require the mongdb to be deleted. Edited January 8Jan 8 by bmartino1
January 8Jan 8 tests where with google chrome the setup wizard and registration worked flawlessly...once you use the docker webui option and sucesfuly register your workspacethen get when going to the home location this is a https crypto issue due to changes in the rocket.chat code.chrome://flags/#unsafely-treat-insecure-origin-as-secureotherwise use in conjunction with a reverse proxy and update your Root_URL! Edited January 8Jan 8 by bmartino1
January 8Jan 8 I otherwise highly recommend running and using the docker compose method... rocket.chat is still updating documentation due to recent changes in code and project. alot has changed...https://github.com/RocketChat/Rocket.Chatas seen here:https://raw.githubusercontent.com/RocketChat/Docker.Official.Image/refs/heads/main/compose.ymland due to changes from dev of rocket.chat:https://github.com/RocketChat/rocketchat-composewhich requires the database compose and standard compose to run (the inspiration behind the AIO image...)https://docs.rocket.chat/docs/deploy-with-ubuntu and the v7.12 docker file per the repo pull That said rocket.chat is still transition and fixing things so i highly recommend the compose option...But the stack as a whole is lot and quite a bit that has my concers for udpates form npm, to node to javascritp 3 to rocket.chat needing to revamp for new codes...so here is a all in one unraid ready comopse file pulling rocket.chats copsoe files.Directory Layout (Recommended)rocketchat-unraid/ ├── compose.yml └── .envUnraid Compose Manager works best when everything is flat.docker-compose.yml (Unraid-ready)version: "3.8" services:# =====================================================# NATS# =====================================================nats: image: docker.io/nats:${NATS_VERSION:-2.11-alpine} container_name: rocketchat-nats restart: unless-stopped command: --http_port 8222 ports: - "${NATS_BIND_IP:-127.0.0.1}:${NATS_PORT_NUMBER:-4222}:4222" labels: folder.view: "rocketchat" net.unraid.docker.managed: "composeman" net.unraid.docker.webui: "" net.unraid.docker.icon: "${UNRAID_ICON}" # =====================================================# MongoDB (Replica Set – auto-initialized)# =====================================================mongodb: image: docker.io/bitnamilegacy/mongodb:${MONGODB_VERSION:-6.0} container_name: rocketchat-mongodb restart: unless-stopped volumes: - /mnt/user/appdata/rocketchat/mongodb:/bitnami/mongodb environment: MONGODB_REPLICA_SET_MODE: primary MONGODB_REPLICA_SET_NAME: rs0 MONGODB_PORT_NUMBER: 27017 MONGODB_INITIAL_PRIMARY_HOST: mongodb MONGODB_INITIAL_PRIMARY_PORT_NUMBER: 27017 MONGODB_ADVERTISED_HOSTNAME: mongodb MONGODB_ENABLE_JOURNAL: "true" ALLOW_EMPTY_PASSWORD: "yes" ports: - "${MONGODB_BIND_IP:-127.0.0.1}:27017:27017" labels: folder.view: "rocketchat" net.unraid.docker.managed: "composeman" net.unraid.docker.webui: "" net.unraid.docker.icon: "${UNRAID_ICON}" # =====================================================# Rocket.Chat# =====================================================rocketchat: image: ${IMAGE:-registry.rocket.chat/rocketchat/rocket.chat}:${RELEASE:-latest} container_name: rocketchat restart: unless-stopped depends_on: - mongodb - nats environment: ROOT_URL: ${ROOT_URL:-http://192.168.2.42:3000} PORT: ${PORT:-3000} DEPLOY_METHOD: docker DEPLOY_PLATFORM: compose REG_TOKEN: ${REG_TOKEN:-} # Mongo MONGO_URL: mongodb://mongodb:27017/rocketchat?replicaSet=rs0 MONGO_OPLOG_URL: mongodb://mongodb:27017/local?replicaSet=rs0 # NATS TRANSPORTER: "nats://nats:4222" # Metrics (optional, harmless if unused) LICENSE_DEBUG: "true" OVERWRITE_SETTING_Prometheus_Enabled: "true" OVERWRITE_SETTING_Prometheus_Port: "${METRICS_PORT:-9458}" ports: - "${BIND_IP:-0.0.0.0}:${HOST_PORT:-3000}:3000" - "${BIND_IP:-0.0.0.0}:${METRICS_PORT:-9458}:${METRICS_PORT:-9458}" volumes: - /mnt/user/appdata/rocketchat/uploads:/app/uploads labels: folder.view: "rocketchat" net.unraid.docker.managed: "composeman" net.unraid.docker.webui: "http://192.168.2.42:${HOST_PORT:-3000}" net.unraid.docker.icon: "${UNRAID_ICON}"Minimal .env (Recommended)# ===================================================== # Rocket.Chat # ===================================================== IMAGE=registry.rocket.chat/rocketchat/rocket.chat RELEASE=latest ROOT_URL=http://192.168.2.42:3000 HOST_PORT=3000 PORT=3000 BIND_IP=0.0.0.0 REG_TOKEN= # ===================================================== # MongoDB # ===================================================== MONGODB_VERSION=6.0 MONGODB_BIND_IP=127.0.0.1 # ===================================================== # NATS # ===================================================== NATS_VERSION=2.11-alpine NATS_PORT_NUMBER=4222 NATS_BIND_IP=127.0.0.1 # ===================================================== # Metrics (optional) # ===================================================== METRICS_PORT=9458 # ===================================================== # Unraid # ===================================================== UNRAID_ICON=https://raw.githubusercontent.com/RocketChat/Rocket.Chat.Artwork/master/Logos/icon.svg Edited January 8Jan 8 by bmartino1 compose file form tests
February 13Feb 13 while Ill leav the aio alone I will most likely not update it due to rocket.chat chagnes. that and I'm looking into a more free solution...so ill be workign more on a matrix setup as seen here:https://forums.unraid.net/topic/127917-guide-matrix-synapse-w-postgres-db-chat-server-element-web-client-coturn-voice/page/3/#findComment-1607898and not be as much assistance for this rocket.chat docker.https://github.com/bmartino1/matrix-textvoicevideo
February 15Feb 15 Hello I have Rocketchat and Mongodb working as sep instances. I am not able to get video working, and the instance of RocketChat is at 8.0.1 so not latest.Can anyone advise how to add video/voip services to the original CA? Since the AIO is no longer supported as per message above, I am using the original CA.I don't get any errors, Im just not sure how to add it. Jitisi is not available and neither is Rocket Meet within the app, so I am not sure where to go from thereThanks in advance
February 15Feb 15 5 hours ago, korefuji said:Hello I have Rocketchat and Mongodb working as sep instances. I am not able to get video working, and the instance of RocketChat is at 8.0.1 so not latest.Can anyone advise how to add video/voip services to the original CA? Since the AIO is no longer supported as per message above, I am using the original CA.I don't get any errors, Im just not sure how to add it. Jitisi is not available and neither is Rocket Meet within the app, so I am not sure where to go from thereThanks in advanceits more issues with how to continue to support what i'm willing to support and waht teh main project documenttion will allow...as explin in previous post the issues has and will always be isseus with the mong db.AIO - issues with to many moving parts and teh need of a RP (I'm not going to support a turn key for that...AIO - Will eventaul break due to changes on rocket.chat and tehre miss of documentations.Rocket.chat wnats it eitehred installed in a linux enviroment or run there compose stack.which i'm all for due to the nature of theere sytem. but htey are not 100% free either and I'm not fully wantign to support intergrations without dues...So the best I can do to assit users, new uesr to stay on track witht he rocket.chat mainteners is have users use compose... (info already shared on this post...) as I atempted to due CA seperate instances, a copose file in teh past and ended with a quick short term AIO solution. (atempted to have them support a AIO givein the changes they are workign on...) they refused... as they wanted teh code and teh authoship of every coponet that is used in there stack... (esental taking others works and legay stealing them with nor support form them and all legal algory on the dev... SO I'm against Rocket.chat for there S*** Practices and given what they were to what they are now and what they are tryign to do I DON"T RECOMEND THEM! Nor willign to support or try to support interaction on it..since the AIO was more a proff of concept due to there BS of documentation and non of the rocket.chat stuff documented nor exmplained in such a way to run... So simalr to imich and other stacks where I will galdy assit where I can but ultimatle things built were built for my use and shared witht eh comunicty on what, how and why come...BUT! I still highly recomned running compose!https://github.com/bmartino1/unraid-rocket.chatTo install and use rocket.chat per the mainteiners... (as I'm at teh will of what they will allow and support!)git clone https://github.com/bmartino1/unraid-rocket.chat.git \ /mnt/user/appdata/unraid-rocket.chatcd /mnt/user/appdata/unraid-rocket.chat chmod +x setup.sh ./setup.sh as again I don't have a good way to expalin and edit nor share a good turn key solution to docker stacks that require more then 1 docker and setup instance..when it is easer to maintin and beter used per teh mainterners recomendation...so...Why Not AIO?The AIO (all-in-one) image bundled MongoDB, NATS, Postfix, and Rocket.Chat into a single container. While convenient, it had significant drawbacks:Update friction — MongoDB and Rocket.Chat update on different cycles. A single image meant rebuilding everything for any update.MongoDB replica set issues — Running mongod inside the app container led to PID management problems and unreliable replica-set initialization on Unraid.Debugging difficulty — All logs mixed together, health checks couldn't target individual services.Upstream drift — Rocket.Chat's own compose structure changed significantly (new NATS requirement, MongoDB 8 support, deprecated old compose files), making the AIO increasingly brittle.The multi-container approach lets each service use its official image, get independent updates, and fail/restart independently...Sorry But I'm esental done being peoples support...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.