Open aasantini opened 4 years ago
also have this issue, upgrade to 3.6 does not resolve it :(
All new users have blank page after update to 3.5
I see "not authorized in web console"
The problem is the 2fa
Login with User and Password in the chat:
-When the data is correct and the login button is pressed, a blank page will be displayed. -That's when they use the following command in the Rocket.Chat virtual machine:
use mongo user rocketchat db.users.updateOne({ "username": "xxx" },{$set: {"services.totp.enabled":true},})
-Replace the "xxx" with the username of the person who needs to be configured
-With this command the blank page should change to the chat home screen.
-Generate an authentication code in "My Account" - "Personal Access Key" -Add
-Next time when a 2fa is requested, that code will be used.
El 2020-09-02 17:15, Renato Tarantelli escribió:
Hello, @geekgonecrazy [1] @rodrigok [2] could you help us with this problem? They would have to prioritize. With this issue the app by browser becomes unusable. We have the same behavior in Chrome, Firefox, and new Edge.
-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [3], or unsubscribe [4].
Links:
[1] https://github.com/geekgonecrazy [2] https://github.com/rodrigok [3] https://github.com/RocketChat/Rocket.Chat/issues/18751#issuecomment-686057335 [4] https://github.com/notifications/unsubscribe-auth/AQ2DEESPZCU5WTTICAJ3GBDSD27ZVANCNFSM4QQVMZSQ
The problem is the 2fa
Login with User and Password in the chat:
-When the data is correct and the login button is pressed, a blank page will be displayed. -That's when they use the following command in the Rocket.Chat virtual machine:
use mongo user rocketchat db.users.updateOne({ "username": "xxx" },{$set: {"services.totp.enabled":true},})
-Replace the "xxx" with the username of the person who needs to be configured
-With this command the blank page should change to the chat home screen.
-Generate an authentication code in "My Account" - "Personal Access Key" -Add
-Next time when a 2fa is requested, that code will be used.
Same problem with 3.10.3 after entering the Mail Authentication code for 2FA activation = white screen tested in Chrome, FireFox and Opera now the browser allways reloads to a white page to get RC back to screnn i had to delete the browser cache
I am on 4.4.1, on a new install of 4.4.0 that was then upgraded. I had disabled 2FA, and I now sometimes get a blank screen when logging in, especially if logging in rapidly, If I hit refresh, it then behaves normally.This is what I see in the logs...
{"level":50,"time":"2022-02-08T09:16:11.608Z","pid":9,"hostname":"a5b2308a5675","name":"","name":"System","msg":"Exception while invoking method userSetUtcOffset 'Error, too many requests. Please slow down. You must wait 35 seconds before trying again. [too-many-requests]'"} {"level":50,"time":"2022-02-08T09:16:16.649Z","pid":9,"hostname":"a5b2308a5675","name":"","name":"System","msg":"Exception while invoking method userSetUtcOffset 'Error, too many requests. Please slow down. You must wait 30 seconds before trying again. [too-many-requests]'"} {"level":50,"time":"2022-02-08T09:19:37.011Z","pid":9,"hostname":"a5b2308a5675","name":"","name":"System","msg":"Exception while invoking method userSetUtcOffset 'Error, too many requests. Please slow down. You must wait 52 seconds before trying again. [too-many-requests]'"}
and I also got this once:
{"level":50,"time":"2022-02-08T09:15:40.005Z","pid":9,"hostname":"a5b2308a5675","name":"","name":"System","msg":"Exception while invoking method getRoomByTypeAndName 'Invalid room [error-invalid-room]'"}
Description:
After installing the latest version 3.5.4 All new users after logging in via web or in the windows client, only a blank screen appears. if they login to the android or iOS apps it works normally. We check user permissions and everything is normal, the same error happens with old accounts that had time without logging in When inspecting the console, no errors appear screenshot: https://prnt.sc/u926kg
Steps to reproduce:
Expected behavior:
Display normal home screen
Actual behavior:
white home screen screenshot: https://prnt.sc/u926kg
Server Setup Information:
Client Setup Information
Additional context
With the rest of the existing users the system works naturally, and we have even replicated the error from the local ip address without leaving through the proxy to verify if it was not an error of the nginx