RocketChat / RocketChat/Rocket.Chat

Endless connection loop during login when using cloud.mongodb.com shared instance (Mongodb V5.0.6)

Open
#24,569 3 comments 0 reactions 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:

For our Rocket.Chat we use a shared M2 instance at https://www.mongodb.com/cloud. Suddenly we can no longer log into Rocket Chat. We only see a flicker of "Waiting for Server.." and "Connecting...".

I was able to reproduce the problem with a fresh new MongoDB instance on cloud.mongodb.com and new Rocket.Chat docker container. Here the same problem happens when finishing the wizard:

Screenshot 2022-02-21 at 22 37 57
Steps to reproduce:
  1. Create a new free Shared M0 Instance on cloud.mongodb.com
  2. Start Rocket.Chat against the new instance
  3. Go through setup wizard
Expected behavior:

Wizard should be able to be completed, login should be possible

Actual behavior:

You get stuck in the last step of the wizard with a endless loop of "Waiting for server..." and "Connecting..."

Server Setup Information:
  • Version of Rocket.Chat Server: 4.4.2 (same with 4.3)
  • Operating System: Ubuntu 20.04.2 LTS
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: 14.18.2 - x64
  • MongoDB Version: 5.0.6
Client Setup Information
  • Chrome (98.0.4758.102) / Safari
  • Operating System: macOS Monteray
Relevant logs:

No logs/errors on server or browser

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

Reproduce the setup wizard login loop using a fresh MongoDB 5.0.6 shared instance and the Rocket.Chat 4.4.2 Docker deployment, then inspect the client and server behavior because the report names no files or tests. Done means the wizard completes and login remains connected without the repeated “Waiting for server...” and “Connecting...” states.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.