RocketChat / RocketChat/Rocket.Chat

app or browser client constantly refreshes when trying to send the message: `netstat | grep 80`

Open
#29,288 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description:

When I am trying to send the command to a chatroom: netstat | grep 80 (either enclosed in backticks or not) rocket refuses to send the message, it stops responding and it constantly refreshes even if I switch to another room. This happens until I perform 'View->Reload Ignoring Cache'. However the message is never sent.

Steps to reproduce:
  1. Go to a chat (either from electron client or directly via the browser)
  2. send the following on a chatroom: netstat | grep 80
Expected behavior:

The message to be sent to the room.

Actual behavior:

The browser or electron-client constantly refreshes without sending the message and in the ui I constatly see Connecting.... and Waiting for server connection switching back and forth.

In the devtools console I constantly see the following 5 requests being sent again and again without ever stopping.

  • wss://rocket.eurodyn.com/sockjs/173/zjoolzj1/websocket
  • https://rocket.eurodyn.com/sockjs/info?cb=a17iphuvg3 (200 OK)
  • https://rocket.eurodyn.com/api/v1/users.presence?ids[]=wiNSsSKmacTSqJj9o&ids[]=...... (200 OK)
  • wss://rocket.eurodyn.com/sockjs/227/9xvg6104/websocket (101 Switching Protocols)
  • https://rocket.eurodyn.com/api/v1/me (200 OK)
Server Setup Information:
  • Version of Rocket.Chat Server: 5.0
  • Operating System: Centos
  • Deployment Method:
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version:
Client Setup Information
  • Desktop App or Browser Version: both chrome and app client
  • Operating System: Tested both on Ubuntu 22.04 and Windows
Additional context
Relevant logs:

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

The report names no source files, tests, or entry points. Start by reproducing the failure with netstat | grep 80 in both the browser and Electron client while observing the listed SockJS, WebSocket, and API requests. Done means the message sends normally without repeated refreshes or connection cycling.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, typescript
Domain
api, backend, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.