Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Urgent Fix: Messages are not showing on channel page and unable to login #14701

Closed
Tayyaba03 opened this issue May 31, 2019 · 9 comments · Fixed by #14717
Closed

Urgent Fix: Messages are not showing on channel page and unable to login #14701

Tayyaba03 opened this issue May 31, 2019 · 9 comments · Fixed by #14717
Assignees

Comments

@Tayyaba03
Copy link

Description:

When a user is logged out and opens a channel page, a white blank screen appears showing nothing, no messages and no option for the user to log in/sign in. As you can see in the attached screenshot list of public channels are also unavailable.

Steps to reproduce:

  1. Go to directory page as a logged out user
  2. Click on any channel
  3. A blank white screen appears without any messages or option to login

Expected behavior:

As a logged out user channel page should show messages and at the bottom, a button appears which asks the user to log in or sign up.

Actual behavior:

When a user is logged out and opens a channel page, a white blank screen appears showing nothing, no messages and no option for the user to log in/sign in.

Screen Shot 2019-05-31 at 5 11 40 PM

Server Setup Information:

  • Version of Rocket.Chat Server: "1.1.1"
  • Operating System: linux
  • Number of Running Instances: 1
  • NodeJS Version: v8.11.4
  • MongoDB Version: 3.4.19

Additional context

Giving 400 error in the console
/api/v1/groups.members?roomName=mods
however, we don't have any room with the name "mods"
Unable to revert to the previous version because while doing it gives the error that we have migrated your database to the latest version

Relevant logs:

Can't share logs as I'm unable to login back :(

Please solve it as soon as you guys can.

Thank you

@tassoevan
Copy link
Contributor

Does your browser console log any errors?

@Tayyaba03
Copy link
Author

@tassoevan the one I mentined in
Additional context
Giving 400 error in the console
/api/v1/groups.members?roomName=mods

and the followings:

Couldn't load members ice.js:1 Failed to log to loggly because of this exception: TypeError: Converting circular structure to JSON --> starting at object with constructor 'Window' --- property 'parent' closes the circle

Failed log data: {args: Arguments(2), stack: undefined, url: "https://urlofoursite", ua: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) Ap…L, like Gecko) Chrome/74.0.3729.169 Safari/537.36", v: "1655.008-2.056", …} args: Arguments(2) 0: "CatchAll. Exception: $ice.$root.browser.getDevice is not a function" 1: Window {postMessage: ƒ, blur: ƒ, focus: ƒ, close: ƒ, parent: Window, …}

@fais3000
Copy link

fais3000 commented May 31, 2019

@tassoevan This is happening when Anonymous read is on. Last working on 1.0.3

@Tayyaba03
Copy link
Author

@tassoevan any update on this one?

@sampaiodiego
Copy link
Member

are you guys able to test #14717 ?
I can provide a Docker image if that makes it easy for testing. thx

@fais3000
Copy link

@sampaiodiego Tested in 1.1.2. Still broken, same behavior as prior version.

@sampaiodiego
Copy link
Member

@fais3000 in wihch browser are you having the issue? can you please describe detailed what you are doing and what are you seeing? thanks

@fais3000
Copy link

@sampaiodiego Chrome and Firefox. When users visits a public channel when anonymous read is on. e.g https://chat.talkwithstranger.com/channel/chatroom The page fails to load and is still with the loading spinner.

  • Same happens if this url is used in an iframe
  • Same happens on a mobile browser (safari)

We had to disable anonymous read for now. It used to work on 1.0.3 and prior versions with same setup.

Here is a screenshot one user shared
image

@sampaiodiego
Copy link
Member

@fais3000 I just tested on either 1.0.3 and 0.74.3 and both versions didn't work when trying to access the room URL directly (i.e.: http://localhost:3000/channel/general)..

but they both work if you go first to home page (i.e.: http://localhost:3000/home) and then open the channel you want via UI.

I'll create an issue so we can fix this for the next version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants