We have many users who’s presence seems to get stuck. Although they log out, they remain as available and logged in. Restarting Mongo and Rocket.Chat will clear this issue, but after many days of running it will once again get stuck. Does anyone else experience this and if so, is there a solution?
You shouldn’t need to restart both mongo and Rocket.Chat. Just restarting Rocket.Chat should do the trick. This is typically an issue of some client not handling session right. What clients do you use with any of the users that get stuck?
I’d also recommend taking a look at 1.1.x some presence issues were fixed there.
I found this issue will happen if 2 accounts use one browser on one computer together, I mean the first account has already log-out after used & then the second account log-in the same browser on the same computer, this issue will happen (the first account will get stuck online).
We had the exact same issue, but it resulted from rebooting the server while clients were connected. I had to manually delete the stuck sessions in MongoDB.
I need to be able to have two separate accounts on the same server, and need to be able to get offline email notifications. The problem is that on Chrome, you stay “online” in both accounts even when you log out of one. This means you need to completely shut all tabs along with the browser and re-open. Is there a way to fix this @aaron.ogle ? Thank you!!
(Running snaps Rocket.Chat Server 1.1.3 with Linux OS)
I noticed related issue with my fresh instance of Rocket Chat - snap 3.2.2. I noticed problem with mobile clients - every time, when user minimizes app on his device, the status immediately changes to away, what is ok, but after ca. 40 sec it goes to offline. Even back app up do not changes status back to online - it still remains offline. Manual change to (in app) to online brings green dot, but as soon as user minimizes app, whole history repeats - first go as away, after ca. 40 sec goes oflline. I must mention, that even user is offline (has offline status), he receive push notifications. In my opinion this is bug, because if user has possibillity to receive push, he is online in some way so he should has “away” status all the time. Offline status suggests, that user is not connected to server and won’t receive any notifications at all. Please fix that.