[Support] Rocket.Chat

Zeroeth · August 8, 2022

19 hours ago, Zeroeth said:

I've had the exact same problem today, and the above argument seems to have fixed the issue. However, I can see the below error in the logs right after > SERVER RUNNING. Would appreciate any insights on this.

+--------------------------------------------------+
|                  SERVER RUNNING                  |
+--------------------------------------------------+
|                                                  |
|  Rocket.Chat Version: 5.0.1                      |
|       NodeJS Version: 14.19.3 - x64              |
|      MongoDB Version: 5.0.10                     |
|       MongoDB Engine: unknown                    |
|             Platform: linux                      |
|         Process Port: 3000                       |
|             Site URL: https://xxx  |
|     ReplicaSet OpLog: Enabled                    |
|          Commit Hash: xxx                 |
|        Commit Branch: HEAD                       |
|                                                  |
+--------------------------------------------------+
=== UnHandledPromiseRejection ===
MongoServerSelectionError: getaddrinfo ENOTFOUND mongodatabase
    at Timeout._onTimeout (/app/bundle/programs/server/npm/node_modules/mongodb/lib/sdam/topology.js:306:38)
    at listOnTimeout (internal/timers.js:557:17)
    at processTimers (internal/timers.js:500:7)
 => awaited here:
    at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)
    at server/database/DatabaseWatcher.ts:96:3
    at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40 {
  reason: TopologyDescription {
    type: 'ReplicaSetNoPrimary',
    servers: Map(1) { 'mongodatabase:27017' => [ServerDescription] },
    stale: false,
    compatible: true,
    heartbeatFrequencyMS: 10000,
    localThresholdMS: 15,
    setName: 'rs01',
    maxSetVersion: 1,
    maxElectionId: new ObjectId("7fffffff0000000000000034"),
    commonWireVersion: 13,
    logicalSessionTimeoutMinutes: undefined
  },
  code: undefined,
  [Symbol(errorLabels)]: Set(0) {}
}
---------------------------------
Errors like this can cause oplog processing errors.
Setting EXIT_UNHANDLEDPROMISEREJECTION will cause the process to exit allowing your service to automatically restart the process
Future node.js versions will automatically exit the process
=================================

Adding the directConnection=true argument to both the MONGO_URL and MONGO_OPLOG_URL seems to have resolved the issue above.

MONGO_URL:

mongodb://rocketchat:<password>@<localhost>:27017/rocketchat?directConnection=true

MONGO_OPLOG_URL

mongodb://rocketchat:<password>@<localhost>:27017/local?authSource=admin&directConnection=true

Reference:

https://github.com/RocketChat/Rocket.Chat/releases

image.png.2387f526db243e89131fbfe13372303c.png

@9BAR Thanks for the update regarding adding the above argument.

Edited August 8, 2022 by Zeroeth

Mogo · August 8, 2022

I made the changes mentioned above. I don't get the error screen anymore and the startup logs look proper now for rocketchat, however, the web page does not load. I just get a dark blue screen.

Just did a test and it seems like the mobile apps work. It's just the web interface does not. I should clarify that it's the internal web location. The external web location works.

Edited August 8, 2022 by Mogo

Zeroeth · September 15, 2022

Hi!

After the last update for RC and MongoDB, I'm getting the following errors. RC is working, but notifications (both in the browser and app) just don't work anymore.

Quote

{"level":40,"time":"2022-09-15T11:54:21.307Z","pid":1,"hostname":"39f56867de46","name":"Push","msg":"Error sending push to gateway (not authorized) {\"statusCode\":401,\"content\":\"{\\\"code\\\":121,\\\"error\\\":\\\"rocket.chat cloud registration required\\\",\\\"requestId\\\":\\\"0bc27b0d-1e88-4859-b3a4-4a8d3eb88698\\\",\\\"status\\\":401}\",\"headers\":{\"access-control-allow-headers\":\"Content-Type, Authorization, Content-Length, X-Requested-With\",\"access-control-allow-methods\":\"GET, PUT, POST, DELETE, OPTIONS\",\"access-control-allow-origin\":\"*\",\"access-control-expose-headers\":\"Content-Type, Authorization, Cache-Control, Expires, Pragma, X-powered-by\",\"cache-control\":\"private, no-cache, no-store, must-revalidate\",\"connection\":\"close\",\"content-length\":\"126\",\"content-type\":\"application/json; charset=utf-8\",\"date\":\"Thu, 15 Sep 2022 11:54:21 GMT\",\"expires\":\"-1\",\"pragma\":\"no-cache\",\"vary\":\"Accept-Encoding\",\"x-powered-by\":\"Rocket Fuel and Rocketeers\"},\"ok\":false,\"data\":{\"code\":121,\"error\":\"rocket.chat cloud registration required\",\"requestId\":\"0bc27b0d-1e88-4859-b3a4-4a8d3eb88698\",\"status\":401}}"}

I've tried re-registering RC on the cloud and currently it shows the instance is connected. I'm also able to sync it, at least that's the notification that I get :).

image.png.1c534c8103438681f854b960cb81fcbe.png

but I cannot Login to Rocket.Chat Cloud when I click the Login to Rocket.Chat Cloud button. This is the error message that I get:

Quote

{"level":50,"time":"2022-09-15T12:01:09.946Z","pid":1,"hostname":"39f56867de46","name":"System","err":{"type":"Error","message":"failed [401]{\"status\":401}","stack":"Error: failed [401]{\"status\":401}\n at makeErrorByStatus (server/lib/http/call.ts:59:9)\n at server/lib/http/call.ts:168:19\n at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40","response":{"statusCode":401,"content":"{\"status\":401}","headers":{"access-control-allow-headers":"Content-Type, Authorization, Content-Length, Last-Event-ID, X-Requested-With","access-control-allow-methods":"GET, PUT, POST, DELETE, OPTIONS","access-control-allow-origin":"*","access-control-expose-headers":"Content-Type, Authorization, Cache-Control, Expires, Pragma, X-powered-by","cache-control":"private, no-cache, no-store, must-revalidate","connection":"close","content-length":"14","content-type":"application/json; charset=utf-8","date":"Thu, 15 Sep 2022 12:01:09 GMT","expires":"-1","pragma":"no-cache","vary":"Accept-Encoding","x-fleet-version":"-77b34ba","x-powered-by":"Rocket Fuel and Rocketeers"},"ok":false,"data":{"status":401}}},"msg":"failed [401]{\"status\":401}"}
{"level":50,"time":"2022-09-15T12:03:45.303Z","pid":1,"hostname":"39f56867de46","name":"System","msg":"Exception while invoking method cloud:finishOAuthAuthorization 'Invalid state provided [error-invalid-state]'"}

My RC docker log on start:

Would highly appreciate any insights/help to resolve this issue.

Avsynthe · September 26, 2022

Can confirm I and some others are having this issue.

See Zeroeth's support thread here:

https://forums.rocket.chat/t/error-in-push-notifications-cloud-registration-error/14940

There's a user in there on the latest version so it may or not be an unRAID issue as we're out of date at the moment.

Github bug:

https://github.com/RocketChat/Rocket.Chat/issues/26947

Here's the server log entry on error

{"level":50,"time":"2022-09-26T06:17:22.311Z","pid":1,"hostname":"0b8fd1acb48a","name":"System","msg":"Exception while invoking method cloud:finishOAuthAuthorization 'Invalid state provided [error-invalid-state]'"}

Edited September 26, 2022 by Avsynthe

Avsynthe · October 10, 2022

Hey all. Sorry I've been busy but I did end up having that chat with @dudanogueira from Rocket.Chat. Great guy btw!

The solution was to use the docker compose stack that installs rocket.chat and mongodb together. If you're on unRAID like me, you'll need to look at getting Docker Compose enabled first, yes it's a thing and it works great.

Here is the compose file:

volumes:
  mongodb_data: { driver: local }
networks:
  default:
    external: false
  **_YOUR-CUSTOM-DOCKER-NETWORK_**:
    external: true



services:
  rocketchat:
    image: registry.rocket.chat/rocketchat/rocket.chat:${RELEASE:-latest}
    restart: on-failure
    labels:
      traefik.enable: "true"
      traefik.http.routers.rocketchat.rule: Host(`${DOMAIN}`)
      traefik.http.routers.rocketchat.tls: "true"
      traefik.http.routers.rocketchat.entrypoints: https
      traefik.http.routers.rocketchat.tls.certresolver: le
    environment:
      MONGO_URL: "${MONGO_URL:-\
        mongodb://${MONGODB_ADVERTISED_HOSTNAME:-mongodb}:${MONGODB_INITIAL_PRIMARY_PORT_NUMBER:-27017}/\
        ${MONGODB_DATABASE:-rocketchat}?replicaSet=${MONGODB_REPLICA_SET_NAME:-rs0}}"
      MONGO_OPLOG_URL: "${MONGO_OPLOG_URL:\
        -mongodb://${MONGODB_ADVERTISED_HOSTNAME:-mongodb}:${MONGODB_INITIAL_PRIMARY_PORT_NUMBER:-27017}/\
        local?replicaSet=${MONGODB_REPLICA_SET_NAME:-rs0}}"
      ROOT_URL: ${ROOT_URL:-http://localhost:${HOST_PORT:-3001}}
      PORT: ${PORT:-3001}
      DEPLOY_METHOD: docker
      DEPLOY_PLATFORM: ${DEPLOY_PLATFORM}
    depends_on:
      - mongodb
    expose:
      - ${PORT:-3001}
    networks:
      - default
      - YOUR-CUSTOM-DOCKER-NETWORK
    ports:
      - "${BIND_IP:-0.0.0.0}:${HOST_PORT:-3001}:${PORT:-3001}"



  mongodb:
    image: docker.io/bitnami/mongodb:${MONGODB_VERSION:-4.4}
    restart: on-failure
    volumes:
      - mongodb_data:/bitnami/mongodb
    environment:
      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}
      ALLOW_EMPTY_PASSWORD: ${ALLOW_EMPTY_PASSWORD:-yes}

Please note thee sections that read "**_YOUR-CUSTOM-DOCKER-NETWORK_**", this is where you would enter the name of your custom docker network if you use one, there are two sections, one near the top and one under the "networks" parameter after the port is specified further below.

This was one and done, all working. That easily! I was able to register the server and log in to Rocket.Chat cloud from the settings menu with everything working perfectly. Good luck!

Zeroeth · October 15, 2022

On 9/15/2022 at 4:30 PM, Zeroeth said:

Hi!

After the last update for RC and MongoDB, I'm getting the following errors. RC is working, but notifications (both in the browser and app) just don't work anymore.

I've tried re-registering RC on the cloud and currently it shows the instance is connected. I'm also able to sync it, at least that's the notification that I get :).

but I cannot Login to Rocket.Chat Cloud when I click the Login to Rocket.Chat Cloud button. This is the error message that I get:

My RC docker log on start:

Would highly appreciate any insights/help to resolve this issue.

Hi All!

I've finally managed to get RC docker working on mongo:5 with all my previous data restored successfully :).

Notifications are working now and I can connect to the Rocket.Chat cloud.

+--------------------------------------------------+
|                  SERVER RUNNING                  |
+--------------------------------------------------+
|                                                  |
|  Rocket.Chat Version: 5.2.0                      |
|       NodeJS Version: 14.19.3 - x64              |
|      MongoDB Version: 5.0.13                     |
|       MongoDB Engine: wiredTiger                 |
|             Platform: linux                      |
|         Process Port: 3000                       |
|             Site URL: https://my.domain.com      |
|     ReplicaSet OpLog: Enabled                    |
|          Commit Hash: 08f03cc9d8                 |
|        Commit Branch: HEAD                       |
|                                                  |
+--------------------------------------------------+

Posting the steps I followed for anyone who might be facing a similar issue.

#1 Stop RC and backup existing data from your current mongodb docker console

mongodump --archive --gzip > 2022.10.15_rocketchat_mongo_server.dump.archive.gzip

#2 Remove the existing mongodb docker

stop the mongodb docker
rename the /mnt/appdata/mongodb folder to mongodb-backup
remove the mongodb docker.

#3 Install mongodb docker (default) with the following changes

Repository:

mongo:5

(Advanced View)

Extra Parameters:

--hostname mongodatabase

Post Arguments:

--bind_ip_all --replSet "rs0"

#4 Initialise ReplicaSet in mongodb
- open the console and type

mongosh

then on the prompt

test >

type

rs.initiate( {
   _id : "rs0",
   members: [
      { _id: 0, host: "<YOUR-SERVER-IP>:27017" },
   ]
})

- you should see the result as below

test> rs.initiate( {
...    _id : "rs0",
...    members: [
...       { _id: 0, host: "<YOUR-SERVER-IP>:27017" },
...    ]
... })
{ ok: 1 }
rs0 [direct: other] test> 

rs0 [direct: primary] test>

#5 Restore the backup data to the new mongodb instance

copy the backup file from step #1 into the new mongodb appdata folder
open the mongodb console and move into the /data/db dir
then type

mongorestore --archive --gzip < 2022.10.15_rocketchat_mongo_server.dump.archive.gzip

You should see something similar to this on a successful restore (this may take a while depending on your backup file size):

2022-10-15T14:54:16.776+0400    159574 document(s) restored successfully. 0 document(s) failed to restore.

#6 Edit your RC docker settings as below

MONGO_URL

mongodb://rocketchat:<Password>@<YOUR-SERVER-IP>:27017/rocketchat?replicaSet=rs0

MONGO_OPLOG_URL

mongodb://rocketchat:<Password>@<YOUR-SERVER-IP>:27017/local?replicaSet=rs0

That's it.

Start the docker and it should work! Enjoy

Edited October 15, 2022 by Zeroeth

Sinister · November 15, 2022

On 11/11/2017 at 12:46 PM, fanningert said:

Application Name: Rocket.Chat

Application Site: https://rocket.chat/

Docker Hub: https://hub.docker.com/r/library/rocket.chat/

Github: https://github.com/RocketChat/Rocket.Chat

Template-Repository: https://github.com/fanningert/unraid-docker-templates

Requirements:

Mondo-DB (There is a mondoDB docker image for unraid in the CA)

Installation (external MongoDB):

Install and Start MongoDB

Install Rocket.Chat docker

Change the variable "Mono DB" (tech name: MONGO_URL) with the URL of your mongoDB

Start Rocket.Chat and after some second it should be reachable over the Web-Frontend URL

Installation (MongoDB as docker):

Install and Start MongoDB

Install Rocket.Chat docker

Add in the attribute "Extra Parameters" the value "--link "MongoDB:db"". MongoDB is the name of the MongoDB docker container.

Change the variable "Mono DB" (tech name: MONGO_URL) to "mongodb://db/rocketchat"

Start Rocket.Chat and after some second it should be reachable over the Web-Frontend URL

Hints:

By default, the first account to register on Rocket Chat becomes the admin, so if your chat room is public, do this immediately in order to prevent someone else from registering and becoming the administrator.

Does this still apply in 2022 ?

isaacery · January 18, 2023

On 10/10/2022 at 7:56 PM, Avsynthe said:

Hey all. Sorry I've been busy but I did end up having that chat with @dudanogueira from Rocket.Chat. Great guy btw!

The solution was to use the docker compose stack that installs rocket.chat and mongodb together. If you're on unRAID like me, you'll need to look at getting Docker Compose enabled first, yes it's a thing and it works great.

Here is the compose file:

volumes:
  mongodb_data: { driver: local }
networks:
  default:
    external: false
  **_YOUR-CUSTOM-DOCKER-NETWORK_**:
    external: true



services:
  rocketchat:
    image: registry.rocket.chat/rocketchat/rocket.chat:${RELEASE:-latest}
    restart: on-failure
    labels:
      traefik.enable: "true"
      traefik.http.routers.rocketchat.rule: Host(`${DOMAIN}`)
      traefik.http.routers.rocketchat.tls: "true"
      traefik.http.routers.rocketchat.entrypoints: https
      traefik.http.routers.rocketchat.tls.certresolver: le
    environment:
      MONGO_URL: "${MONGO_URL:-\
        mongodb://${MONGODB_ADVERTISED_HOSTNAME:-mongodb}:${MONGODB_INITIAL_PRIMARY_PORT_NUMBER:-27017}/\
        ${MONGODB_DATABASE:-rocketchat}?replicaSet=${MONGODB_REPLICA_SET_NAME:-rs0}}"
      MONGO_OPLOG_URL: "${MONGO_OPLOG_URL:\
        -mongodb://${MONGODB_ADVERTISED_HOSTNAME:-mongodb}:${MONGODB_INITIAL_PRIMARY_PORT_NUMBER:-27017}/\
        local?replicaSet=${MONGODB_REPLICA_SET_NAME:-rs0}}"
      ROOT_URL: ${ROOT_URL:-http://localhost:${HOST_PORT:-3001}}
      PORT: ${PORT:-3001}
      DEPLOY_METHOD: docker
      DEPLOY_PLATFORM: ${DEPLOY_PLATFORM}
    depends_on:
      - mongodb
    expose:
      - ${PORT:-3001}
    networks:
      - default
      - YOUR-CUSTOM-DOCKER-NETWORK
    ports:
      - "${BIND_IP:-0.0.0.0}:${HOST_PORT:-3001}:${PORT:-3001}"



  mongodb:
    image: docker.io/bitnami/mongodb:${MONGODB_VERSION:-4.4}
    restart: on-failure
    volumes:
      - mongodb_data:/bitnami/mongodb
    environment:
      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}
      ALLOW_EMPTY_PASSWORD: ${ALLOW_EMPTY_PASSWORD:-yes}

Please note thee sections that read "**_YOUR-CUSTOM-DOCKER-NETWORK_**", this is where you would enter the name of your custom docker network if you use one, there are two sections, one near the top and one under the "networks" parameter after the port is specified further below.

This was one and done, all working. That easily! I was able to register the server and log in to Rocket.Chat cloud from the settings menu with everything working perfectly. Good luck!

hi there @Avsynthe. I have got this working using unraid docker compose instance, however as i am new to docker compose i cant seem to figure out how to create and mount a volume from the appdata share. i.e. appdata/rocketchat. your script places the data somewhere else that i cant locate. can you please post an example of your script with how to mount a folder from appdata? thank you so much!

Edited January 18, 2023 by isaacery

Ladrek · January 30, 2023

Is it me or does MongoDB break easily?

Ladrek · January 31, 2023

Some indexes for collection 'rocketchat_livechat_visitor' could not be created:


	Index key contains an illegal field name: field name starts with '$'.


Error creating index: rocketchat_room -> { 'livechatData.$**': 1 } MongoServerError: Index key contains an illegal field name: field name starts with '$'.


    at MessageStream.messageHandler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/connection.js:462:30)


    at MessageStream.emit (events.js:400:28)


    at MessageStream.emit (domain.js:475:12)


    at processIncomingData (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/message_stream.js:108:16)


    at MessageStream._write (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/message_stream.js:28:9)


    at writeOrBuffer (internal/streams/writable.js:358:12)


    at MessageStream.Writable.write (internal/streams/writable.js:303:10)


    at Socket.ondata (internal/streams/readable.js:731:22)


    at Socket.emit (events.js:400:28)


    at Socket.emit (domain.js:475:12)


    at addChunk (internal/streams/readable.js:293:12)


    at readableAddChunk (internal/streams/readable.js:267:9)


    at Socket.Readable.push (internal/streams/readable.js:206:10)


    at TCP.onStreamRead (internal/stream_base_commons.js:188:23)


    at TCP.callbackTrampoline (internal/async_hooks.js:130:17) {


  operationTime: new Timestamp({ t: 1675142601, i: 1 }),


  ok: 0,


  code: 67,


  codeName: 'CannotCreateIndex',


  '$clusterTime': {


    clusterTime: new Timestamp({ t: 1675142601, i: 1 }),


    signature: {


      hash: new Binary(Buffer.from("ddd687851700cd15d41c6a1f51be5c2a55b32f8d", "hex"), 0),


      keyId: new Long("7194681051048837124")


    }


  }


}


strict mode: use allowUnionTypes to allow union type keyword at "#/properties/value" (strictTypes)


LocalStore: store created at 


LocalStore: store created at 


LocalStore: store created at 


MessageType.render is deprecated. Use MessageType.message instead. livechat_webrtc_video_call


{"level":40,"time":"2023-01-31T05:23:27.170Z","pid":1,"hostname":"b4d3cd82f168","name":"VoIPService","msg":"Voip is not enabled. Cant start the service"}


{"level":40,"time":"2023-01-31T05:23:28.752Z","pid":1,"hostname":"b4d3cd82f168","name":"VoIPService","msg":"VoIP service already stopped"}


{"level":51,"time":"2023-01-31T05:23:28.954Z","pid":1,"hostname":"b4d3cd82f168","name":"Migrations","msg":"Not migrating, already at version 281"}


{"level":51,"time":"2023-01-31T05:23:28.977Z","pid":1,"hostname":"b4d3cd82f168","name":"DatabaseWatcher","msg":"Using change streams"}


Loaded the Apps Framework and loaded a total of 0 Apps!


+--------------------------------------------------+


|                   SERVER ERROR                   |


+--------------------------------------------------+


|                                                  |


|  Rocket.Chat Version: 5.4.0                      |


|       NodeJS Version: 14.19.3 - x64              |


|      MongoDB Version: 4.0.28                     |


|       MongoDB Engine: unknown                    |


|             Platform: linux                      |


|         Process Port: 3000                       |


|             Site URL: https://r.xxxx.us          |


|     ReplicaSet OpLog: Enabled                    |


|          Commit Hash: 51f456a544                 |


|        Commit Branch: HEAD                       |


|                                                  |


|  YOUR CURRENT MONGODB VERSION IS NOT SUPPORTED,  |


|  PLEASE UPGRADE TO VERSION 4.4 OR LATER          |


|                                                  |


+--------------------------------------------------+

What am i doing wrong?

Edited January 31, 2023 by Ladrek

flyize · February 23, 2023

Anyone got any instructions to make Rocket.Chat work these days?

Maverick_GERMANY · April 1, 2023

I also haven't been able to install mongo and rocket via community apps on my unraid server. I'm also not a professional and don't understand the complex commands that were posted here. my biggest problem is that i'm not very good at english and the english used in instructions is complex. I can't translate entire pages into German either, since English commands are also translated and taken out of context. It is surprising that there is only one video of Spaceinvader on YouTube and it is already two years old. clear that you have changed a lot in the meantime and therefore probably also the reason why it does not work. so my only chance to understand a manual in English is also useless. But I'm lucky and there is help outside of the Unraid forum. I was surprised that it is so easy and runs rocket in three steps! Unfortunately, there is no possibility, as with an installed app, to make settings on the docker afterwards. maybe someone will be able to create a new working guide with the help of the two community apps - I and probably many others would be happy! here the solution:

ich bin auch nicht in der Lage gewesen mongo und rocket via Community Apps auf meinen Unraid Server zu installieren. ich bin da auch kein Profi und verstehe die komplexen Befehle nicht die hier gepostet wurden. mein größtes Problem ist das ich nicht so gut in Englisch bin und gerade das Englisch was in Anleitungen verwendet wird, komplex ist. ich kann auch nicht ganze Seiten in Deutsch übersetzen da dabei englische Befehle auch übersetzt werden und aus dem Zusammenhang gerissen werden. es ist verwunderlich das es bei YouTube gerade mal ein Video gibt von Spaceinvader und das ist schon zwei Jahre alt. klar das dich inzwischen einiges geändert hat und somit wohl auch der Grund warum es nicht funktioniert. somit ist meine einzige Chance eine Anleitung auf englisch nachvollziehen zu können auch unbrauchbar. Aber ich habe Glück und es gibt auch außerhalb vom Unraid Forum Hilfe. das es nun aber so einfach ist und in drei Schritten rocket läuft, hat mich überrascht! leider fehlt die Möglichkeit, wie bei einer installierten App, im nachgang noch Einstellungen am docker zu tätigen. vielleicht schafft es ja jemand mithilfe der beiden Community Apps eine funktionierende Anleitung neu zu erstellen-ich und wahrscheinlich viele andere würden sich freuen! hier die Lösung:

1. docker run --name db -d mongo:4.4 --replSet rs0 --oplogSize 128

2. docker exec -ti db mongo --eval "printjson(rs.initiate())"

3. docker run --name rocketchat -p 8009:3000 --link db --env ROOT_URL=http://localhost --env MONGO_OPLOG_URL=mongodb://db:27017/local -d rocket.chat

Edited April 6, 2023 by Maverick_GERMANY

Maverick_GERMANY · April 3, 2023

On 6/11/2018 at 6:55 PM, vanes said:

It seems I made it work

I found https://rocket.chat/docs/installation/paas-deployments/aws/#5-configure-nginx-web-server-with-tlsssl , then edited file like this

 server {
 listen 443 ssl;
 server_name chat.my.domain.com;
 ssl_certificate /config/keys/letsencrypt/fullchain.pem;
 ssl_certificate_key /config/keys/letsencrypt/privkey.pem;
 ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
 ssl_prefer_server_ciphers on;
 ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
 root /config/www;
 add_header Strict-Transport-Security "max-age=31536000; includeSubDomains";
 index index.html index.htm;
 # Make site accessible from http://localhost/
 server_name localhost;
 location / {
     proxy_pass http://192.168.0.10:3000/;
     proxy_http_version 1.1;
     proxy_set_header Upgrade $http_upgrade;
     proxy_set_header Connection "upgrade";
     proxy_set_header Host $http_host;
     proxy_set_header X-Real-IP $remote_addr;
     proxy_set_header X-Forward-For $proxy_add_x_forwarded_for;
     proxy_set_header X-Forward-Proto http;
     proxy_set_header X-Nginx-Proxy true;
     proxy_redirect off;
 }
 }
 server {
 listen 80;
 server_name chat.my.domain.com;
 return 301 https://$host$request_uri;
 }

now ios app can connect!

ssllab shows A+

I need help accessing HTTPS (SSL) via NGINX.

Of course I want a secure connection to my Unraid server and of course to Rocket.Chat, so I set up NGINX with DuckDns and use it to access the various CA apps such as Nextcloud Openhab Heimdall and Unraid itself, everything works great, just I can't do that with Rocket.Chat. I know that Spaceinvader has a config for swag, but it certainly doesn't work with NGINX. Hence my question, does @vanes' config work? Or what do I have to set or configure where so that I can reach Rocket.Chat via HTTPS?

My domains are structured as follows:
Rocketchat.mydomain.duckdns.org
nextcloud.mydomain.duckdns.org
openhab.mydomain.duckdns.org

etc.

I actually wanted to run Rocket.Chat on port 21443 and had changed it in the RocketChat Docker under WEB Frontend, but since that didn't work, I went back to the basic setting with port 3000. I also don't understand the WebUI entry: http://[IP]:[3000] As soon as I change the entry to https or the IP address of the unraid server, I no longer even get local access to the WebUI

I need your help

THX

Maverick_GERMANY · April 4, 2023

server {
 listen 443 ssl;
 server_name rocketchat.mydomain.duckdns.org;
 ssl_certificate /config/keys/letsencrypt/fullchain.pem;
 ssl_certificate_key /config/keys/letsencrypt/privkey.pem;
 ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
 ssl_prefer_server_ciphers on;
 ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
 root /config/www;
 add_header Strict-Transport-Security "max-age=31536000; includeSubDomains";
 index index.html index.htm;
 # Make site accessible from http://localhost/
 server_name localhost;
 location / {
     proxy_pass http://192.168.212.50:3000/;
     proxy_http_version 1.1;
     proxy_set_header Upgrade $http_upgrade;
     proxy_set_header Connection "upgrade";
     proxy_set_header Host $http_host;
     proxy_set_header X-Real-IP $remote_addr;
     proxy_set_header X-Forward-For $proxy_add_x_forwarded_for;
     proxy_set_header X-Forward-Proto http;
     proxy_set_header X-Nginx-Proxy true;
     proxy_redirect off;
 }
 }
 server {
 listen 80;
 server_name rocketchat.mydomain.duckdns.org;
 return 301 https://$host$request_uri;
 }

Okay I tried this (above) conf file instead of the original NGINX conf file (below) and after that NGINX wouldn't run at all and I couldn't get any access to the other domains

# ------------------------------------------------------------
# rocketchat.mydomain.duckdns.org
# ------------------------------------------------------------


server {
  set $forward_scheme https;
  set $server         "192.168.212.50";
  set $port           3000;

  listen 8080;
#listen [::]:8080;

listen 4443 ssl http2;
#listen [::]:4443;


  server_name rocketchat.mydomain.duckdns.org;


  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-8/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-8/privkey.pem;




# Asset Caching
  include conf.d/include/assets.conf;


  # Block Exploits
  include conf.d/include/block-exploits.conf;







    # Force SSL
    include conf.d/include/force-ssl.conf;




proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;


  access_log /data/logs/proxy-host-7_access.log proxy;
  error_log /data/logs/proxy-host-7_error.log warn;







  location / {

    







    
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    

    # Proxy!
    include conf.d/include/proxy.conf;
  }


  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

Maverick_GERMANY · April 6, 2023

Oh, I forgot to post the instructions here for you to install apps (mongodb/Rocket.Chat) via CA normally. I had accidentally only posted it in a German-speaking article .

Oh ich hatte ganz vergessen euch hier auch die Anleitung zu posten mit der Ihr via CA Apps (mongodb/Rocket.Chat) ganz normal installieren könnt. Ich hatte es versehentlich nur in einem deutschsprechenden Artikel gepostet.

rocket chat instructions - new.txt

REllU · June 5, 2023

EDIT:

Seems that this is my issue. Or atleast part of it:

https://github.com/RocketChat/Rocket.Chat/issues/29382

Original message below:
Here to see if anyone else is experiencing similar oddities..

I seem to have a-lot of issues with files currently. I'm using File System as my storage type, which has been working just fine the past few months.

However, now I'm getting "ENOENT: no such file or directory, stat '/app/uploads//647df273c68d8a46579c7e20'"

Uploading files seems to be working fine. Issue comes when someone is trying to view the file, or delete the file.

A bit of backstory

It started from trying to create a new Team inside the Rocket.Chat, uploading an avatar to said Team, and then removing the avatar in order to replace it with something else.

I noticed that I wasn't able to upload another avatar anymore, so I figured I'd just delete the Team, and start again.

However, now the Team was "gone", but I wasn't able to create another one, since Rocket.Chat was determined that there was already a Team with the same name. I was unable to access it anywhere else, except in the settings menu, where I saw the Team. When trying to remove the Team there, it only resulted in more errors.

Now however, everything related to files uploaded to Rocket.Chat, are behaving.. oddly.

I haven't been able to really pinpoint the issue yet, but basically, only some of my files are loaded, in some client applications. This is very weird, as some files can be loaded on one Client app (such as Windows app, web-app, or mobile app) but for example a file that was uploaded through Android app, was only being displayed on the Web version.

I've recently updated our Rocket.Chat to 6.2, which could be the culprit. But very un-sure.

I've now been googling and banging my head against the wall for half of today, and I haven't really been finding anything.

If anyone's interested, here's the whole error from trying to delete a file:

Spoiler

{"level":50,"time":"2023-06-05T17:23:47.195Z","pid":1,"hostname":"b1850019346f","name":"System","msg":"Exception while invoking method deleteMessage","err":{"type":"Error","message":"ENOENT: no such file or directory, stat '/app/uploads//647df273c68d8a46579c7e20'","stack":"Error: ENOENT: no such file or directory, stat '/app/uploads//647df273c68d8a46579c7e20'\n => awaited here:\n at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n at server/ufs/ufs-local.ts:72:20\n at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\n => awaited here:\n at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n at server/ufs/ufs-store.ts:230:3\n at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\n => awaited here:\n at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n at server/ufs/ufs-local.ts:76:5\n at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\n => awaited here:\n at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n at app/file-upload/server/lib/FileUpload.ts:677:4\n at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\n => awaited here:\n at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n at app/lib/server/functions/deleteMessage.ts:48:13\n at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\n => awaited here:\n at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n at app/api/server/v1/misc.ts:557:17\n at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40","errno":-2,"code":"ENOENT","syscall":"stat","path":"/app/uploads//647df273c68d8a46579c7e20"},"msg":"ENOENT: no such file or directory, stat '/app/uploads//647df273c68d8a46579c7e20'"}

Edited June 14, 2023 by REllU
Added a GitHub link

jcamer · July 19, 2023

I see on that link it was fixed in version 6.2.4, and that there is a 6.2.9 out now as well as 6.3 RC's. Did you try to move to 6.2.4 or newer? I just ran into this on 6.2. Not sure what to do as the docker website shows the official image as only being released as 6.2 so far.

Sinister · August 20, 2023

Im hoping that this is an easy fix but i cant seem to upload files even slightly larger than 100MB in rocket chat. I have it reverse proxied using Swag and believe i made the correct changes inside rocket chat itself. removing the file size limit. making sure the site url is correct and even making sure client max body size 0; is set in the nginx.conf file and rocketchat proxy conf. been at this forever and would appreciate a hand

i-B4se · September 23, 2023

Hello,

since a few days I have problems with Rocket Chat and MongoDB. Perhaps you can help me further.

I updated the two Dockers and since then MongoDB no longer starts with the following error message:

Unrecognized option: storage.journal.enabled
try 'mongod --help' for more information

Unfortunately I can not find a solution to start the database again.

Thank you in advance.

i-B4se · September 29, 2023

Does no one have an idea what this could be? 😅

lukad · October 5, 2023

On 9/29/2023 at 6:24 PM, i-B4se said:

Does no one have an idea what this could be? 😅

hey, responded in mongodb thread https://forums.unraid.net/topic/54895-support-jasonbean-mongodb/?do=findComment&comment=1313389

Maverick_GERMANY · October 25, 2023

I need your help - before I completely lose my mind or my wife breaks up with me because I swear so much. I just can't get Rocket.Chat to work and I really don't know what the problem is.

The error in MongoDB: Unrecognized option: storage.journal.enabled try 'mongod --help' for more information I was able to fix it and added it to the current instructions (attachment).

I was able to install MongoDB and Rocket.Chat and they are running, but I cannot open Rocket.Chat via the WebUI. In the original Spaceinvader instructions it says to change the network type to proxynet.

But I only have HOST/BRIDGE/CUSTOM br:0 Is this perhaps the reason for the error?

What I also saw or cannot assign is the IP address in mongod.conf The network interface says bindIp: 127.0.0.1 Do I need to adjust it if necessary?

Can I safely change the web frontend port in Rocket.Chat? Port 3000 is used by AdGuard Home by default.

Ich brauche eure Hilfe - bevor ich endgültig den Verstand verliere oder meine Frau sich von mir trennt, weil ich so sehr am Fluchen bin. Ich bekomme Rocket.Chat einfach nicht zum laufen und weiß gerade auch echt nicht woran es liegt.

Den Fehler in MongoDB:
Unrecognized option: storage.journal.enabled
try 'mongod --help' for more information
Konnte ich beheben und habe das auch in der aktuellen Anleitung (Anlage) eingefügt.

MongoDB und Rocket.Chat konnte ich installieren und die laufen auch, aber ich kann Rocket.Chat nicht über die WebUI öffnen.

In der Ursprünglichen Anleitung von Spaceinvader sagt er, das man den Netzwerk Type auf proxynet umstellen soll. Ich habe aber nur HOST/BRIDGE/CUSTOM br:0

Liegt daran evtl. der Fehler?

Was ich auch gesehen habe bzw. nicht zuordnen kann ist die IP Adresse in der mongod.conf
Bei network interface steht bindIp: 127.0.0.1

Muß ich die ggf. noch anpassen?

Kann ich in Rocket.Chat den Web Frontend Port unbedenklich ändern? Der Port 3000 wird von AdGuard Home standartmässig verwendet.

rocket chat instructions - new.txt

Maverick_GERMANY · November 3, 2023

What information do you need to help me, how or where can I read/retrieve it?
Welche Informationen benötigt Ihr um mir zu helfen, wie oder wo kann ich diese Auslesen/Abrufen?

Rocket.Chat and MongoDB are running - marked with the green triangle in Unraid. Rocket.Chat has no errors in the log but MongoDB keeps showing red sections in the log:
Rocket.Chat und MongoDB laufen - werden mit dem grünen Dreieck in Unraid gekennzeichnet. Rocket.Chat hat keine Fehler im Protokol aber MongoDB zeigt immer wieder Rote Abschnitte im Protokol:

{"t":{"$date":"2023-11-03T08:08:26.175+01:00"},"s":"I", "c":"COMMAND", "id":51803, "ctx":"conn113","msg":"Slow query","attr":{"type":"command","ns":"rocketchat.rocketchat_notification_queue","command":{"findAndModify":"rocketchat_notification_queue","query":{"$and":[{"$or":[{"sending":{"$exists":false}},{"sending":{"$lte":{"$date":"2023-11-03T07:03:26.007Z"}}}]},{"$or":[{"schedule":{"$exists":false}},{"schedule":{"$lte":{"$date":"2023-11-03T07:08:26.007Z"}}}]},{"error":{"$exists":false}}]},"remove":false,"new":false,"upsert":false,"sort":{"ts":1},"update":{"$set":{"sending":{"$date":"2023-11-03T07:08:26.007Z"}}},"lsid":{"id":{"$uuid":"709a2e54-a525-41fd-af92-62716b1b8779"}},"$clusterTime":{"clusterTime":{"$timestamp":{"t":1698995303,"i":1}},"signature":{"hash":{"$binary":{"base64":"NXBqpofiWlfTNVDFsBAoYKVQX2U=","subType":"0"}},"keyId":7293813294287028225}},"$db":"rocketchat"},"planSummary":"IXSCAN { ts: 1 }","keysExamined":0,"docsExamined":0,"nMatched":0,"nModified":0,"nUpserted":0,"numYields":0,"reslen":217,"locks":{"ParallelBatchWriterMode":{"acquireCount":{"r":1}},"FeatureCompatibilityVersion":{"acquireCount":{"r":2,"w":1}},"ReplicationStateTransition":{"acquireCount":{"w":3}},"Global":{"acquireCount":{"r":2,"w":1}},"Database":{"acquireCount":{"w":1}},"Collection":{"acquireCount":{"w":1}}},"flowControl":{"acquireCount":1},"readConcern":{"level":"local","provenance":"implicitDefault"},"writeConcern":{"w":"majority","wtimeout":0,"provenance":"implicitDefault"},"waitForWriteConcernDurationMillis":167,"storage":{},"cpuNanos":361706,"remote":"192.168.212.5:34578","protocol":"op_msg","durationMillis":167}}

OR

{"t":{"$date":"2023-11-03T08:20:47.462+01:00"},"s":"I", "c":"COMMAND", "id":51803, "ctx":"conn101","msg":"Slow query","attr":{"type":"command","ns":"rocketchat.rocketchat_notification_queue","command":{"findAndModify":"rocketchat_notification_queue","query":{"$and":[{"$or":[{"sending":{"$exists":false}},{"sending":{"$lte":{"$date":"2023-11-03T07:15:47.184Z"}}}]},{"$or":[{"schedule":{"$exists":false}},{"schedule":{"$lte":{"$date":"2023-11-03T07:20:47.185Z"}}}]},{"error":{"$exists":false}}]},"remove":false,"new":false,"upsert":false,"sort":{"ts":1},"update":{"$set":{"sending":{"$date":"2023-11-03T07:20:47.185Z"}}},"lsid":{"id":{"$uuid":"97d1ced4-1096-4047-a07d-ce1294449eb7"}},"$clusterTime":{"clusterTime":{"$timestamp":{"t":1698996043,"i":1}},"signature":{"hash":{"$binary":{"base64":"QH00ZgFg4/zmLqNwHtv6RljxQ04=","subType":"0"}},"keyId":7293813294287028225}},"$db":"rocketchat"},"planSummary":"IXSCAN { ts: 1 }","keysExamined":0,"docsExamined":0,"nMatched":0,"nModified":0,"nUpserted":0,"numYields":0,"reslen":217,"locks":{"ParallelBatchWriterMode":{"acquireCount":{"r":1}},"FeatureCompatibilityVersion":{"acquireCount":{"r":2,"w":1}},"ReplicationStateTransition":{"acquireCount":{"w":3}},"Global":{"acquireCount":{"r":2,"w":1}},"Database":{"acquireCount":{"w":1}},"Collection":{"acquireCount":{"w":1}}},"flowControl":{"acquireCount":1},"readConcern":{"level":"local","provenance":"implicitDefault"},"writeConcern":{"w":"majority","wtimeout":0,"provenance":"implicitDefault"},"waitForWriteConcernDurationMillis":277,"storage":{},"cpuNanos":355066,"remote":"192.168.212.5:40788","protocol":"op_msg","durationMillis":277}}

At first glance there are always the same errors, the only thing that changes is the port of the IP address

So auf dem ersten Blick sind es immer die selben fehler, das einzige was sich ändert ist der Port der IP Adresse

Edited November 3, 2023 by Maverick_GERMANY

Curiosity · December 29, 2023

Is there currently a complete and working guide on how to install Rocket.Chat on Unraid so that it works?

9BAR · January 11

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.

[Support] Rocket.Chat

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

MattFaz

HojojojoWololo

jm9843

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation