The application GUI just crashed in Admin acc

Description

Server Setup Information

  • Version of Rocket.Chat Server: 7.7.0
  • Operating System: Ubuntu 22.04.05
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: 22.14.0
  • MongoDB Version: 6.0
  • Proxy: traefik
  • Firewalls involved:

Bug only show in Admin acc, another user work normally

Browser show this error:

Error: Minified React error #130; visit Minified React error #130 – React for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at sv (verifyErrors.js:34:1)
at d (verifyErrors.js:34:1)
at m (verifyErrors.js:34:1)
at M (verifyErrors.js:34:1)
at aj (verifyErrors.js:34:1)
at i (verifyErrors.js:34:1)
at si (verifyErrors.js:34:1)
at so (verifyErrors.js:34:1)
at su (verifyErrors.js:34:1)
at i3 (verifyErrors.js:34:1)
ag @ verifyErrors.js:34Understand this error

I have tried solution this topic: "The application GUI just crashed" - after dismissing banner · Issue #33263 · RocketChat/Rocket.Chat · GitHub

/usr/bin/mongosh --eval 'use rocketchat' --eval 'db.rocketchat_banner.updateMany({active: true },{ $set: { active: false }})'
but not solve this issue

Pls help me to figure out what wrong. Thanks

You are going to have to be more descriptive about your deployment.

There is not enough information to be able to help you.

Show your compose file and give us some history of your deployment - new install, upgrade etc.

I am running RocketChat version 7.7.4 deployed as a docker container. Mongo version is 6.0 as well. I get the same error as the OP in the devtools of rocketchat. We have rocketchat deployed and working since 6 years. This is the first time I have encountered this error.

The following workaround from github issues has not been helpful to me:
> use rocketchat

> db.rocketchat_banner.updateMany({active: true },{ $set: { active: false }})

The only option working for me right now is to remove the admin role for the user. However, this is not ideal. @reetp - I would be happy to share any details that would help troubleshoot this issue. Workarounds are also acceptable.

Thank you.

Mo

Which you have not……

Next, don’t @ people, especially me. I don’t work here. I don’t want my phone pinging all the time. You will get muted/blocked.

Your version will be EOL at the end of Nov. Plan your upgrade.

Make sure you are not using GridFS for file storage - as per the docs.

Check your proxy setup.

Read the docker docs and learn how to read the logs. Almost certainly that’s where the error will be.

My bad - I thought you worked for Rocket.Chat. Would be best not to respond if you do not have anything valuable to contribute.

But looking at your comments in other threads, I shouldn’t expect any better.

I suggest you read the FAQ here.

Abuse of any form will not be tolerated by me or Rocket.Chat.

Abuse

FYI I’ve been here pretty well since Rocket open sourced. I have worked for them in the past, and most of the senior staff are good friends of mine. Hence I have elevated privileges here.

It also means that I am your best chance of a resolution, so annoying me won’t get you any help, least of all from anyone who works at Rocket.Chat

I asked you matter of fact questions to debug your issue because you are the one with the problem, not me.

Some tips on how to debug properly.

Server info required

And also this, and the links therein.

Tips on asking questions

If you can’t be bothered to deal with it professionally then you are on your own. Good luck.