RocketChat
Status is incorrect in version 7.7.0
Description:
Teammembers that are 100 % offline are shown as Online or AFK. Same for employees that are working and online. Theire are displayed as AFK an Offline. The Statuses seems to be completely random.
Expected behavior:
The online status of users is shown correctly
- Offline users are shown as Offline
- AFK user as Away
- Users which has set them self to DND are in DND status
-> the status changes correctly if you go offline or online for all other users
Actual behavior:
They randomly displayed as not offline. No one of them is online and not here.
Server Setup Information:
- Version of Rocket.Chat Server: registry.rocket.chat/rocketchat/rocket.chat:7.7.0
- License Type: Community
- Operating System: Ubuntu
- Deployment Method: docker
- Number of Running Instances: 1
- MongoDB Version: 6.0
Client Setup Information
- Desktop App or Browser Version: Browser Chrome latest and App (Snap Ubuntu) latest
- Operating System: Ubuntu
User
Online: 8 DND: 0 Away: 3 Offline: 20 Total: 31
Version 7.7.0 Latest Community Operating within plan limits Version supported until 1. Januar 2026 Workspace registered
Check your websockets & reverse proxy.
This is more likely a support issue than bug.
(Note if you are on CE with more than about 200 users presence gets flaky due to node constraints)
Thank you for the quick answer :)
So you think its a Problem with our Reverse Proxy.
We are using traefik as reverse proxy.
The two things that normally break it are:
200+ users on CE Flaky websockets/connections
I don't guarantee it - not enough info - but that is the place to start looking.
https://gist.github.com/reetp/a66149d5f060f260643a353ca7067a98#websockets
Beyond that what do your logs say?
It seems to be just the automatic detection of the presence status. If we set us to offline manually, it is displayed for all users instantly.
If we just close Rocket.Chat and shut down the computer, the status still online for weeks now.
As soon as the employee with the SSH rights is present, I will take care of log extracts.
I would like to thank you once again for your patience and helpfulness
👍 Same issue here. We've even upgraded to 7.7.3 but no luck.
Not sure if this error is related but it includes some cron stuff 🤷♂️
+----------------------------------------------------+
| SERVER RUNNING |
+----------------------------------------------------+
| |
| Rocket.Chat Version: 7.7.3 |
| NodeJS Version: 22.14.0 - x64 |
| MongoDB Version: 7.0.15 |
| MongoDB Engine: wiredTiger |
| Platform: linux |
| Process Port: 3000 |
| Site URL: https://whoknowns.com |
| ReplicaSet OpLog: Enabled |
| Commit Hash: 8ba78e4da0 |
| Commit Branch: HEAD |
| |
+----------------------------------------------------+
[2025-07-03T11:05:59.021Z] INFO 2feeb53b-4ea0-49b0-93af-37e16ef14176/TRANSIT: Connecting to the transporter...
[2025-07-03T11:05:59.023Z] INFO 2feeb53b-4ea0-49b0-93af-37e16ef14176/TRANSPORTER: TCP server is listening on port 40155
[2025-07-03T11:05:59.023Z] INFO 2feeb53b-4ea0-49b0-93af-37e16ef14176/TRANSPORTER: UDP Discovery is disabled.
[2025-07-03T11:05:59.023Z] INFO 2feeb53b-4ea0-49b0-93af-37e16ef14176/TRANSPORTER: TCP Transporter started.
[2025-07-03T11:05:59.535Z] INFO 2feeb53b-4ea0-49b0-93af-37e16ef14176/REGISTRY: '$node' service is registered.
[2025-07-03T11:05:59.536Z] INFO 2feeb53b-4ea0-49b0-93af-37e16ef14176/REGISTRY: 'matrix' service is registered.
[2025-07-03T11:05:59.536Z] INFO 2feeb53b-4ea0-49b0-93af-37e16ef14176/$NODE: Service '$node' started.
[2025-07-03T11:05:59.536Z] INFO 2feeb53b-4ea0-49b0-93af-37e16ef14176/MATRIX: Service 'matrix' started.
[2025-07-03T11:05:59.536Z] INFO 2feeb53b-4ea0-49b0-93af-37e16ef14176/BROKER: ✔ ServiceBroker with 2 service(s) started successfully in 515ms.
TypeError: Cannot read properties of null (reading 'userNameTable')
at hideUserName (server/lib/dataExport/exportRoomMessagesToFile.ts:16:16)
at getMessageData (server/lib/dataExport/exportRoomMessagesToFile.ts:71:31)
at server/lib/dataExport/exportRoomMessagesToFile.ts:227:25
at Array.forEach (<anonymous>)
at exportRoomMessages (server/lib/dataExport/exportRoomMessagesToFile.ts:226:10)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at exportRoomMessagesToFile (server/lib/dataExport/exportRoomMessagesToFile.ts:284:50)
at continueExportOperation (server/lib/dataExport/processDataDownloads.ts:181:25)
at Module.processDataDownloads (server/lib/dataExport/processDataDownloads.ts:264:2)
at runCronJobFunctionAndPersistResult (/app/bundle/programs/server/npm/node_modules/@rocket.chat/cron/src/index.ts:14:18)
at Object.fn (/app/bundle/programs/server/npm/node_modules/@rocket.chat/cron/src/index.ts:130:4)
at /app/bundle/programs/server/npm/node_modules/@rocket.chat/agenda/src/Job.ts:252:6
... repeated A LOT
We've also verified that the reverse proxy is solid and it does NOT terminate connections, unless it has been inactive for 24 hours. And node's ability to handle websockets shouldn't be a problem
Same issue here.
Possibly.
Please fill out some server info as per the original OP.
Thanks.
Still in 7.8.0 😢 Was no issue in earlier major versions
Server Setup Information:
- Rocket.Chat Server: registry.rocket.chat/rocketchat/rocket.chat:7.8.0
- NodeJS: 22.14.0 - x64
- License Type: Community
- Operating System: Debian
- Deployment Method: docker
- Proxy: behind nginx proxy, websockets, streaming & co working
- Number of Running Instances: 1
- MongoDB Version: 6.0.13
Client Setup Information
- Browser Chrome latest
- Operating System: Windows
It seems that /api/v1/users.presence?ids[]=... returns wrong information even on reloads.
Status seems to work for us after upgrading to version 7.7.4. Notifications still does not:
Server Setup Information:
- Version of Rocket.Chat Server: 7.7.4
- License Type: Community
- Number of Users: 106
- Operating System: Debian GNU/Linux 12 (bookworm)
- Deployment Method: Docker
- Number of Running Instances: 1
- DB Replicaset Oplog: Enabled
- NodeJS Version: v22.14.0
- MongoDB Version: 7.0.15 / wiredTiger (oplog Enabled)
Status seems to work for us after upgrading to version 7.7.4.
Cool.
Notifications still does not:
That is a separate issue. Please don't nix things up. It just confuses people.
Sill an issue here in 7.10.0. Users that are offline are shown as online. Does anybody have a workaround to "reset online status"?
We are seeing the same behavior with our installation (snap with auto-update). This issue should be given high priority, as it causes some frustration due to the incorrect status.
