RocketChat / RocketChat/Rocket.Chat

First Channel After Login cannot be a group/Private channel

Open
#31,218 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

After upgrading reluctantly from my perfectly stable 3.18.7 to the latest 6.5.0 I noticed that on login I was getting an error:

Room not found
The room does not exist or you may not have permission.

It would appear that First Channel After Login can no longer be a private channel. e.g. companytalk.

This is a private server with no public login but users login first to this private channel.

But private channels now have a URL containing 'group' eg

https://chat.somedomain.com/group/companytalk

Open channel contains 'channel' eg

https://chat.somedomain.com/channel/generalstuff

If we leave First Channel After Login set to companytalk we get the above error. If we change the channel to open/public the /group/ changes to /channel/ and we login correctly as expected.

Also on logout in a browser it should return to:

https://chat.somedomain.com

But it always ends up at this which is the First Channel.

https://chat.somedomain.com/channel/companytalk

Docker
Rocket 6.5.0 and earlier versions

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 login and browser logout flows with a private First Channel After Login, using the Rocket.Chat 6.5.0 Docker setup described in the issue. Trace the route handling for the private /group/ URL and the logout redirect; done means private first channels load after login and logout returns to the server root rather than the channel URL.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication, frontend, web-dev
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.