RocketChat / RocketChat/Rocket.Chat

Not able to disconnect when connecting Workspace with RocketChat cloud with "No Internet Access" registration

Open
#19,011 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:

After registering a self hosted service via "No Internet Connection" way on RocketChat cloud, the service itself cannot be properly disconnected again.

When disconnecting, it seems to still use the stored key when clicking on "Reconnecting" because it offers no setup instructions, keys or choosing of connection way. Instead, it shows an error message saying "An error occured".

Steps to reproduce:
  1. Connect your self hosted server with the could via "No Internet Access" by copy pasting the encryption keys
  2. Go to admin page of your self hosted server, click on "Connected Services" and click Disconnected. You will get a success notification
  3. Click on "Click here to Register your Workspace". You will see immediately that you might be connected again but you're getting an error message.
Expected behavior:

When performing step 3, I expect to have again the choice of pasting the key directly from the cloud console or to choose offline registration.

Actual behavior:

It shows immediately the page as if the workspace were connected again.

Server Setup Information:
  • Version of Rocket.Chat Server: 3.6.2
  • Operating System: Ubuntu 18.04.5 LTS
  • Deployment Method: Docker Compose
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: Docker Node JS
  • MongoDB Version: 4.0
Client Setup Information
  • Desktop App or Browser Version: Safari 14
  • Operating System: Mac OS 10.15.6
Additional context

rocketchatbug

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

No source file or test is identified in the issue. Start by reproducing the self-hosted “No Internet Access” registration, disconnection, and re-registration flow described in the steps; done means re-registration again offers key pasting or offline registration instead of reconnecting and showing an error.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.