RocketChat / RocketChat/Rocket.Chat
Chat message not shown as sent nor received message displayed until page is refreshed
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
- Running rocket chat on docker behind nginx reverse proxy and Plesk
- Using rocketchat version 6.5.3
- Case 1: When I am in a direct chat with another user and I send a message, it is not shown as sent (changing color from grey to black) until I manually refresh the page
- Case 2: When I am in that chat and another user sends a message to me, it is shown shown until I refresh the page
Steps to reproduce:
- Access a user chat
- Send a message to another user
or
- Access a user chat
- Wait for a user to send you a message
- Refresh page
Expected behavior:
I would expect new messages to show up automatically
Actual behavior:
New or sent message are only shown once page is reloaded
Server Setup Information:
- Version of Rocket.Chat Server: 6.5.3
- Operating System: Docker containter
- Deployment Method: docker
- Number of Running Instances: 1
- DB Replicaset Oplog: unknown
- NodeJS Version: as per docker container
- MongoDB Version: latest
Client Setup Information
- Desktop App or Browser Version: Chrome Version 121.0.6167.85 (Official Build) (arm64)
- Operating System: macOS
Additional context
Rocketchat runs in container behind nginx reverse proxy
Relevant logs:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified. Reproduce the direct-message cases in Rocket.Chat 6.5.3 with Docker behind an nginx reverse proxy, comparing behavior before and after a page refresh; inspect the missing server and browser logs if available. Done means sent and received messages appear automatically without reloading.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, frontend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100