RocketChat / RocketChat/Rocket.Chat

Adding guests to channels and teams -> limit reached

Open
#30,299 11 comments 1 reaction 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:

I create a user as admin with the role Guest. I want to add this user to a channel or team with /invite @test.user or via the web gui Add User.

After that Rocket.Chat gives me the following message.

error-max-rooms-per-guest-reached
Steps to reproduce:
  1. Go to a channel (public/private)
  2. Type the command /invite @test.user
  3. Error message appears in the channel
Expected behavior:

That the user is added.

Actual behavior:

Is not added and an error message comes.

Server Setup Information:
  • Version of Rocket.Chat Server: 6.3.3
  • Operating System: Ubuntu 20.04 - Server
  • Deployment Method: snap
  • Number of Running Instances: 1
  • DB Replicaset Oplog: 0
  • NodeJS Version: v14.21.2
  • MongoDB Version: 5.0.15 / wiredTiger (oplog Enabled)
Client Setup Information
  • Desktop App or Browser Version: Both and all Versions
  • Operating System: All
Additional context

Rocket.Chat app, not the server, runs in German in my profile.

Relevant logs:

No logs found that could help.

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 files or tests are named. Start by reproducing the issue through /invite @test.user and the web GUI Add User, then trace the paths using error-max-rooms-per-guest-reached as the search term. Done means a Guest user can be added to a channel or team without that error.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.