RocketChat / RocketChat/Rocket.Chat
Jitsi not working in Enterprise hosted
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 installing Jitsi in Marketplace the configuration is not saved and calls don't work.
Reinstall did not fix the issue: https://github.com/RocketChat/Rocket.Chat/issues/28594
Steps to reproduce:
- Go to Marketplace.
- Search for Jitsi.
- Choose Jitsi.
- Click install.
- Go to settings.
- Find "Conference Call" and click "Open".
- See available Provider.
Expected behavior:
- In the Settings tab of Jitsi in Marketplace should be a settings tab.
- In the Settings -> Conference Call there should be Jitsi available.
Actual behavior:


After reinstall I can't see the settings anymore, even after refressing.

And it actually worked the very first time:

Server Setup Information:
- Version of Rocket.Chat Server: 6.1.2
- Number of Running Instances: 2
- DB Replicaset Oplog:
- NodeJS Version: v14.21.2
- MongoDB Version: 4.4.16 / wiredTiger (oplog Enabled)
- Commit Details HEAD: (7507d14ca)
- Deployment ID: 6439b01c98a60900017f0c89
Client Setup Information
Tried Chrome, Firefox, and Ubuntu Desktop app.
Additional context
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
Start by reproducing the Jitsi Marketplace installation on Rocket.Chat 6.1.2, then inspect the Marketplace settings and Settings → Conference Call behavior described here. Compare the result with issue #28594 and the supplied screenshots and logs. Done means the Jitsi settings tab is retained after installation and Jitsi appears as an available Conference Call provider.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100