Rocket.chat: Cannot visit specific room before logging in, no error message.

[timbeiko]

Description:

When trying to go directly to a room, without having logged in to Rocket.Chat, participants get a loading screen forever rather than a redirect/popup to login.

Ideally, users clicking the link should be able to see that they are in the right room (i.e. see past conversation, perhaps with the typing box greyed out) and have the option to log in.

Steps to reproduce:

1. Without being logged into Rocket.Chat / on a new browser, go to: https://chat.hyperledger.org/channel/besu
2. The window only shows grey loading dots, like these:
   
3. To fix this issue, we have realized you can go to https://chat.hyperledger.org/home, and then to https://chat.hyperledger.org/channel/besu, and that will work, but this is cumbersome.

Expected behavior:

1. Go to https://chat.hyperledger.org/channel/besu
2. See the chat room, have the opportunity to log in if not logged in.

Actual behavior:

1. Go to https://chat.hyperledger.org/channel/besu
2. Loading screen stays stuck:
   

Server Setup Information:

• This is happening to everyone on our team who tries too visit https://chat.hyperledger.org/channel/besu

Additional context

N/A

Relevant logs:

N/A

[ryjones]

This server is running:

Hash | abf67ce98521b115c4c85d2ff86394098c92bbf3
-- | --
Tue Apr 30 16:58:11 2019 -0300
HEAD
1.0.2

[ryjones]

This is not fixed in 3.0.0

[Sing-Li]

@engelgabriel fast track candidate

[geekgonecrazy]

@ggazzo this seems like would be super easy to add specifically on the room to redirect?

[ggazzo]

sorry I cant reproduce on any other server (open/localhost/unstable), could you update to 3.2/3.3 or test over open.rocket.chat? thanks

[timbeiko]

@ryjones can you confirm the version of rocket chat that HLF is running?

[ryjones]

@timbeiko we have an upgrade scheduled for next Sunday (US time): https://lists.hyperledger.org/g/tsc/message/3002

we are running

Version | 1.0.2

[timbeiko]

@ryjones will we upgrade to v.>3.3?

[ryjones]

We are upgrading to 3.2.2, which has the fix. I was able to visit this chat server, where it works, and check the version, which is {"version":"3.2.0","success":true}.

[ryjones]

@timbeiko this looks fixed. We’re running 3.3.0 and these links work.