RocketChat / RocketChat/Rocket.Chat
Rocketchat not loading in browser
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Rocketchat is not loading in browser, remains on 3 white dots
Steps to reproduce:
- Put in server URL
Expected behavior:
Rocketchat should load login screen
Actual behavior:
Stays on white background with 3 white dots
Server Setup Information:
- Version of Rocket.Chat Server: 6.5.0
- Operating System: Ubuntu 18.04
- Deployment Method: Snap
- Number of Running Instances: 1
- DB Replicaset Oplog:
- NodeJS Version:
- MongoDB Version:
Client Setup Information
- Desktop App or Browser Version: Firefox 115.5/Chrome/Brave
- Operating System: Debian 12
Additional context
I've changed the SITE URL to the correct value https://chat.xxxx.xxxx
Seems to constantly reset to http:/localhost:3000
I am using Apache reverse proxy
When i set to https://chat.xxxx.xxxx, still encounter the problem.
Works on Android rocketchat app (chat only, admin gets 3 dots)
Tried clearing cache and performing various suggestions found about this bug, nothing worked.
Relevant logs:
Firefox debug output
Uncaught ReferenceError: meteor_runtime_config is not defined
https://chat.xxxx.xxxx/1519e0159bfa893f84a8840a684f71abb3b48133.js?meteor_js_resource=true:1
https://chat.xxxx.xxxx1519e0159bfa893f84a8840a684f71abb3b48133.js?meteor_js_resource=true:1
https://chat.xxxx.xxxx/1519e0159bfa893f84a8840a684f71abb3b48133.js?meteor_js_resource=true:1
Brave debug output
Uncaught ReferenceError: meteor_runtime_config is not defined
at client_environment.js:1:1
at client_environment.js:78:1
at url_common.js:80:1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The browser console points to client_environment.js and url_common.js in the served JavaScript resource; start there and inspect how runtime configuration is supplied. Reproduce through the Apache reverse proxy with the stated SITE URL, then verify that the login screen loads without the meteor_runtime_config error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, javascript
- Domain
- frontend, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100