RocketChat / RocketChat/Rocket.Chat

Users getting session timeout and don't recieve messages/sent messages are greyed out

Open
#12,206 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

Diverse users are getting in different times a session timeout although expiration day is set to 90 days.
After reconnecting there are several problems with sending and receiving messages in direct message and channels. Occurs in web browser as well as in rc-client.

Steps to reproduce:
  1. User A gets disconnected and logs in again.
  2. User A sends a message to any User B.
  3. The sent message is greyed out for user A/User B receives message ordinarily.
  4. Now if user B sends a message to user A, he can see "User B is typing" and he gets a new message notification, but there are no new messages visible for User A in chat window.
  5. Refreshing browser cache or relogin solves this bug.
Expected behavior:
  • Session timeout should apply after 90 days.
  • Messages should be sent and received ordinarily after session timeout.
Actual behavior:
  • Users getting timeout several times a weeks.
  • Sent messages are buggy after session timeout.
Server Setup Information:
  • Version of Rocket.Chat Server: 0.68.3
  • Operating System: Debian 9
  • Deployment Method: tar
  • Number of Running Instances: 1
  • DB Replicaset Oplog: No
  • NodeJS Version: 8.11.3
  • MongoDB Version: 3.2.11
Additional context

In browser console for the greyed out message:
id=123xyz“ class=“message background-transparent-dark-hover own temp“

Relevant logs:

Couldn't lookup logs yet.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is identified in the report. Start by reproducing the reconnect sequence in the browser and inspect the console entry for the greyed-out temporary message; done means sessions follow the configured 90-day expiration and direct or channel messages send and appear normally after reconnecting.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.