RocketChat unusable, very slow, hangs etc

Bonjour :wave:


Since somes weeks, we cannot use rocket chat from any client normally.
It’s very very slow, and often, I needed to reload server or disconnect/reconnect.
Empty cache. Etc.
And when It works a little. Sending message took five ~ six seconds each times.

Server Setup Information

  • Version of Rocket.Chat Server: 5.1.4
  • Operating System: Ubuntu 22.04
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: True
  • NodeJS Version: v14.19.3
  • MongoDB Version: 5.0.13 / wiredTiger (oplog Activé)
  • Proxy: Traefik 2.8
  • Firewalls involved: shorewall

Any additional Information

4 vCPU Cores


200 GB SSD

Attachments files in FileSystem storage

And in logs (debug), I had this message every 5 secondes:

{"level":20,"time":"2022-10-16T19:46:17.693Z","pid":1,"hostname":"10b26ce79149","name":"LivechatEnterprise","section":"Queue","msg":"Executing queue Public with timeout of 5000"}

Help! :ring_buoy:
Thanks :slightly_smiling_face:


How many concurrent users? Depending on that you may need to start thinking about scaling it up.

We have some community users/sysadmins that has big deployments and can help you better here:

1 Like


Very little community :sweat_smile:
Max 10 at same time.

30 registered.

I just see in my cloud portal, no notification since two months.


After updating our Rocket.Chat instance to 5.2 (Docker), our chat rooms are very slow (public, private messages) and the messages “bouncing” up and down like if you would scroll permanently.

Here are our instance details:

  • Max users: 25
  • Cores: 4
  • RAM: 8192MB (8GB)
  • MongoDB: 5
  • Proxy: Nginx 18.0

I have the same problem. We went from 3.8.17 (snap) to 3.8.17 (Docker) and then I upgraded step-by-step up to v5 and everything worked on the test server.

Today we did it in production and the whole service is totally unstable. Random 503 errors, time-outs and the service is unusable. We have roughly 450 users but only 40-50 or so active at the same time.

@tobiasreinhard sorry to ping you directly, but how did you solve it?

Any other ideas? I tried to scale up in the Docker swarm but could not manage to do it yet.


You check for the resources usage. With all the new features, it may require more resources than before.

Let me know if this helps or if you were able to find the bottleneck.


We’ve switched to Microsoft Teams internally. Until then, unfortunately, there was no solution to the problem. I’m sorry…