# After updating to 6.10.0 browser screen is stuck on loading screen **URL:** \ **Category:** Community Support\ **Tags:** docker\ **Created:** [July 26, 2024, 7:56pm UTC](https://forums.rocket.chat/t/after-updating-to-6-10-0-browser-screen-is-stuck-on-loading-screen/20304 "2024-07-26T19:56:00Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Roman](https://avatars.discourse-cdn.com/v4/letter/r/ed8c4c/32.png) [@Roman](https://forums.rocket.chat/u/Roman)\ **Post date:** [July 26, 2024, 7:56pm UTC](https://forums.rocket.chat/t/after-updating-to-6-10-0-browser-screen-is-stuck-on-loading-screen/20304/1 "2024-07-26T19:56:00Z")
### Description After the update the screen is just stuck on those three dots moving from big to small in the middle of the screen. Any idea how to fix? I tried clearing cookies/cache but didn’t fix. ### Server Setup Information - Version of Rocket.Chat Server: _6.10.0_ - Operating System: _Linux CentOS 7_ - Deployment Method: _docker compose_ - Number of Running Instances: _1_ - DB Replicaset Oplog: _not sure_ - NodeJS Version: _not sure_ - MongoDB Version: _5.0_ - Proxy: _n/a_ - Firewalls involved: _firewalld_ ### Any additional Information These are my current docker logs: ```auto [root@ELK-Stack rocketchat]# docker logs rocketchat-rocketchat-1 (node:1) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023. Please migrate your code to use AWS SDK for JavaScript (v3). For more information, check the migration guide at https://a.co/7PzMCcy (Use `node --trace-warnings ...` to show where the warning was created) LocalStore: store created at LocalStore: store created at LocalStore: store created at {"level":40,"time":"2024-07-26T19:32:07.096Z","pid":1,"hostname":"eb89009f7138","name":"VoIPAsteriskService","msg":"Voip is not enabled. Cant start the service"} (node:1) [MONGODB DRIVER] Warning: cursor.count is deprecated and will be removed in the next major version, please use `collection.estimatedDocumentCount` or `collection.countDocuments` instead {"level":51,"time":"2024-07-26T19:32:07.202Z","pid":1,"hostname":"eb89009f7138","name":"Migrations","msg":"Not migrating, already at version 304"} [2024-07-26T19:32:07.262Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/BROKER: Moleculer v0.14.31 is starting... [2024-07-26T19:32:07.262Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/BROKER: Namespace: [2024-07-26T19:32:07.263Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/BROKER: Node ID: 53773364-68b1-47a8-b6fd-81376fa17113 [2024-07-26T19:32:07.265Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/REGISTRY: Strategy: RoundRobinStrategy [2024-07-26T19:32:07.265Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/REGISTRY: Discoverer: LocalDiscoverer [2024-07-26T19:32:07.267Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/BROKER: Serializer: EJSONSerializer [2024-07-26T19:32:07.283Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/BROKER: Validator: FastestValidator [2024-07-26T19:32:07.287Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/BROKER: Registered 13 middleware(s). [2024-07-26T19:32:07.289Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/BROKER: Transporter: TcpTransporter {"level":51,"time":"2024-07-26T19:32:07.338Z","pid":1,"hostname":"eb89009f7138","name":"DatabaseWatcher","msg":"Using change streams"} [2024-07-26T19:32:07.360Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/TRANSIT: Connecting to the transporter... [2024-07-26T19:32:07.375Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/TRANSPORTER: TCP server is listening on port 44956 [2024-07-26T19:32:07.376Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/TRANSPORTER: UDP Discovery is disabled. [2024-07-26T19:32:07.377Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/TRANSPORTER: TCP Transporter started. {"level":51,"time":"2024-07-26T19:32:08.734Z","pid":1,"hostname":"eb89009f7138","name":"License","msg":"License installed","version":"3.0","hash":"lxNsHloc"} [2024-07-26T19:32:08.908Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/REGISTRY: '$node' service is registered. [2024-07-26T19:32:08.910Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/REGISTRY: 'matrix' service is registered. [2024-07-26T19:32:08.911Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/$NODE: Service '$node' started. [2024-07-26T19:32:08.911Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/MATRIX: Service 'matrix' started. [2024-07-26T19:32:08.912Z] INFO 53773364-68b1-47a8-b6fd-81376fa17113/BROKER: ✔ ServiceBroker with 2 service(s) started successfully in 1s. ufs: temp directory created at "/tmp/ufs" +-------------------------------------------------+ | SERVER RUNNING | +-------------------------------------------------+ | | | Rocket.Chat Version: 6.10.0 | | NodeJS Version: 14.21.3 - x64 | | MongoDB Version: 5.0.24 | | MongoDB Engine: wiredTiger | | Platform: linux | | Process Port: 3000 | | Site URL: http://10.100.10.36:3000 | | ReplicaSet OpLog: Enabled | | Commit Hash: 623a265851 | | Commit Branch: HEAD | | | +-------------------------------------------------+ [root@ELK-Stack rocketchat]# ``` ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [July 28, 2024, 12:19am UTC](https://forums.rocket.chat/t/after-updating-to-6-10-0-browser-screen-is-stuck-on-loading-screen/20304/2 "2024-07-28T00:19:09Z")
At least one bug open on this. Check github. Also I strongly advise to use 6.10.1 for a security fix. ---
**Author:** ![Roman](https://avatars.discourse-cdn.com/v4/letter/r/ed8c4c/32.png) [@Roman](https://forums.rocket.chat/u/Roman)\ **Post date:** [July 30, 2024, 12:13am UTC](https://forums.rocket.chat/t/after-updating-to-6-10-0-browser-screen-is-stuck-on-loading-screen/20304/3 "2024-07-30T00:13:14Z")
Updated to 6.10.1 but still the same issue. Also getting this in docker logs now for the container: ```auto +-------------------------------------------------+ | SERVER RUNNING | +-------------------------------------------------+ | | | Rocket.Chat Version: 6.10.1 | | NodeJS Version: 14.21.3 - x64 | | MongoDB Version: 5.0.24 | | MongoDB Engine: wiredTiger | | Platform: linux | | Process Port: 3000 | | Site URL: http://10.100.10.36:3000 | | ReplicaSet OpLog: Enabled | | Commit Hash: 636382f57e | | Commit Branch: HEAD | | | +-------------------------------------------------+ {"level":51,"time":"2024-07-29T23:59:08.564Z","pid":1,"hostname":"8bc21ca16b20","name":"License","msg":"License installed","version":"3.0","hash":"MFrZItnI"} {"level":50,"time":"2024-07-29T23:59:16.161Z","pid":1,"hostname":"8bc21ca16b20","name":"System","msg":"Failed to communicate with Rocket.Chat Cloud","url":"https://releases.rocket.chat/v2/server/supportedVersions","err":{"type":"AbortError","message":"The user aborted a request.","stack":"AbortError: The user aborted a request.\n at abort (/app/bundle/programs/server/npm/node_modules/@rocket.chat/server-fetch/node_modules/node-fetch/lib/index.js:1401:16)\n at AbortSignal.abortAndFinalize (/app/bundle/programs/server/npm/node_modules/@rocket.chat/server-fetch/node_modules/node-fetch/lib/index.js:1416:4)\n at AbortSignal.dispatchEvent (/app/bundle/programs/server/npm/node_modules/event-target-shim/dist/event-target-shim.js:818:35)\n at abortSignal (/app/bundle/programs/server/npm/node_modules/abort-controller/dist/abort-controller.js:52:12)\n at AbortController.abort (/app/bundle/programs/server/npm/node_modules/abort-controller/dist/abort-controller.js:91:9)\n at Timeout. (/app/bundle/programs/server/npm/node_modules/@rocket.chat/server-fetch/dist/index.js:37:51)\n at listOnTimeout (internal/timers.js:557:17)\n at processTimers (internal/timers.js:500:7)\n => awaited here:\n at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n at app/cloud/server/functions/supportedVersionsToken/supportedVersionsToken.ts:46:17\n at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40","name":"AbortError"}} {"level":51,"time":"2024-07-30T00:00:34.875Z","pid":1,"hostname":"8bc21ca16b20","name":"License","msg":"License installed","version":"3.0","hash":"33R2HoSs"} ``` ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [July 30, 2024, 7:59am UTC](https://forums.rocket.chat/t/after-updating-to-6-10-0-browser-screen-is-stuck-on-loading-screen/20304/4 "2024-07-30T07:59:46Z")
> [@Roman](#): > > `SERVER RUNNING` Your server is runnung but your configuration is wrong. > [@Roman](#): > > `Site URL: http://10.100.10.36:3000` Http is ONLY for localhost testing. Use a reverse proxy + ssl/https. > [@Roman](#): > > `Failed to communicate with Rocket.Chat Cloud` Likely an issue with firewalling and tied to the previous comment. ---
**Author:** ![Roman](https://avatars.discourse-cdn.com/v4/letter/r/ed8c4c/32.png) [@Roman](https://forums.rocket.chat/u/Roman)\ **Post date:** [July 30, 2024, 7:28pm UTC](https://forums.rocket.chat/t/after-updating-to-6-10-0-browser-screen-is-stuck-on-loading-screen/20304/5 "2024-07-30T19:28:35Z")
> [@reetp](#): > > Use a reverse proxy + ssl/https. Can you explain this more. ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [July 30, 2024, 7:41pm UTC](https://forums.rocket.chat/t/after-updating-to-6-10-0-browser-screen-is-stuck-on-loading-screen/20304/6 "2024-07-30T19:41:22Z")
No, but the documentation can. [https://docs.rocket.chat/v1/docs/deploy-with-docker-docker-compose](https://docs.rocket.chat/v1/docs/deploy-with-docker-docker-compose) ---
**Author:** ![Roman](https://avatars.discourse-cdn.com/v4/letter/r/ed8c4c/32.png) [@Roman](https://forums.rocket.chat/u/Roman)\ **Post date:** [July 31, 2024, 12:05am UTC](https://forums.rocket.chat/t/after-updating-to-6-10-0-browser-screen-is-stuck-on-loading-screen/20304/7 "2024-07-31T00:05:25Z")
For the `Enable HTTPs` section in the above link, I have a question about domain: - `DOMAIN`: _Your domain or subdomain name only. Avoid adding https:// or any trailing slashes. Confirm that this domain resolves to the server IP address._ Can I just input a domain I want (for example: `aquarium.uhtasi.local`) without having to actually own or purchase the domain? How do I “confirm that this domain resolves to the server IP address”? If you know, thanks for the help! ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [July 31, 2024, 6:36am UTC](https://forums.rocket.chat/t/after-updating-to-6-10-0-browser-screen-is-stuck-on-loading-screen/20304/8 "2024-07-31T06:36:07Z")
> [@Roman](#): > > Can I just input a domain I want (for example: `aquarium.uhtasi.local`) without having to actually own or purchase the domain? Yes, but you still need a proxy + ssl certificate to use https. Read about self signed certificates. Note also that if Rocket detects an network it will want to register with a proper internet resolvable domain. They are cheap to buy! There is a specific method to use if you really want it airgapped with no internet connection. Read the docs. [quote]How do I “confirm that this domain resolves to the server IP address”? [/quote] This is a general networking question and the interwebs are full of pages on it. ---
**Author:** ![Roman](https://avatars.discourse-cdn.com/v4/letter/r/ed8c4c/32.png) [@Roman](https://forums.rocket.chat/u/Roman)\ **Post date:** [July 31, 2024, 9:12pm UTC](https://forums.rocket.chat/t/after-updating-to-6-10-0-browser-screen-is-stuck-on-loading-screen/20304/9 "2024-07-31T21:12:14Z")
Since `aquarium.uhtasi.local` is only accessible internally, I believe I shouldn’t have to purchase it. Instead I added it to my `/etc/hosts` file as so: ```auto 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.100.10.36 aquarium.uhtasi.local ``` `ping`-ing the domain shows that it does indeed correspond to the server IP (10.100.10.36): ```auto [root@ELK-Stack rocketchat]# ping aquarium.uhtasi.local PING aquarium.uhtasi.local (10.100.10.36) 56(84) bytes of data. 64 bytes from aquarium.uhtasi.local (10.100.10.36): icmp_seq=1 ttl=64 time=0.075 ms 64 bytes from aquarium.uhtasi.local (10.100.10.36): icmp_seq=2 ttl=64 time=0.072 ms 64 bytes from aquarium.uhtasi.local (10.100.10.36): icmp_seq=3 ttl=64 time=0.130 ms ^C --- aquarium.uhtasi.local ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2004ms rtt min/avg/max/mdev = 0.072/0.092/0.130/0.027 ms [root@ELK-Stack rocketchat]# ``` I updated my `.env` file as so: ```auto ### Rocket.Chat configuration # Rocket.Chat version # see:- https://github.com/RocketChat/Rocket.Chat/releases RELEASE=6.10.1 # MongoDB endpoint (include ?replicaSet= parameter) #MONGO_URL= # MongoDB endpoint to the local database #MONGO_OPLOG_URL= # IP to bind the process to BIND_IP=127.0.0.1 # URL used to access your Rocket.Chat instance ROOT_URL=https://aquarium.uhtasi.local # Port Rocket.Chat runs on (in-container) #PORT= # Port on the host to bind to #HOST_PORT= ### MongoDB configuration # MongoDB version/image tag #MONGODB_VERSION= # See:- https://hub.docker.com/r/bitnami/mongodb ### Traefik config (if enabled) # Traefik version/image tag #TRAEFIK_RELEASE= # Domain for https (change ROOT_URL & BIND_IP accordingly) DOMAIN=aquarium.uhtasi.local # Email for certificate notifications LETSENCRYPT_EMAIL=roman@uhtasi.org ``` Creating the new container shows this in the logs: ```auto +-------------------------------------------------+ | SERVER RUNNING | +-------------------------------------------------+ | | | Rocket.Chat Version: 6.10.1 | | NodeJS Version: 14.21.3 - x64 | | MongoDB Version: 5.0.24 | | MongoDB Engine: wiredTiger | | Platform: linux | | Process Port: 3000 | | Site URL: http://10.100.10.36:3000 | | ReplicaSet OpLog: Enabled | | Commit Hash: 636382f57e | | Commit Branch: HEAD | | | +-------------------------------------------------+ {"level":51,"time":"2024-07-31T19:20:49.907Z","pid":1,"hostname":"0a6c64d8fd87","name":"License","msg":"License installed","version":"3.0","hash":"7Un7R1Co"} ``` Running the `traefik`-related command does return an error however: ```auto [root@ELK-Stack rocketchat]# docker compose -f traefik.yml up -d WARN[0000] Found orphan containers ([rocketchat-rocketchat-1 rocketchat-mongodb-1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. [+] Running 0/1 ⠼ Container rocketchat-traefik-1 Starting 3.4s Error response from daemon: driver failed programming external connectivity on endpoint rocketchat-traefik-1 (9307f7e963a1208f9fc03e1a4630085444c19114da5d313538982517f2769d76): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use [root@ELK-Stack rocketchat]# ``` However I still cannot access Rocket.Chat in the browser. I am trying the following URLs: [http://10.100.10.36:3000/](http://10.100.10.36:3000/) results in: # This site can’t be reached **10.100.10.36** took too long to respond. Try: - Checking the connection - Checking the proxy and the firewall - Running Windows Network Diagnostics ERR\_CONNECTION\_TIMED\_OUT while [https://aquarium.uhtasi.local/](https://aquarium.uhtasi.local/) results in: # This site can’t be reached **aquarium.uhtasi.local** ’s server IP address could not be found. Try: - Checking the connection - Checking the proxy, firewall, and DNS configuration - Running Windows Network Diagnostics ERR\_NAME\_NOT\_RESOLVED Any idea what the fix could be? ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [July 31, 2024, 10:34pm UTC](https://forums.rocket.chat/t/after-updating-to-6-10-0-browser-screen-is-stuck-on-loading-screen/20304/10 "2024-07-31T22:34:29Z")
> [@Roman](#): > > Any idea what the fix could be? Yes, and the answers are already here but you aren’t trying to read and learn. Don’t use http/3000 UNLESS you are testing on your own localhost. Rocket is not a web server. It’s an application that speaks via a websocket. Put the server on a separate machine VM. > Site URL: [https://your.domain.name](https://your.domain.name) Don’t use an IP or 3000. Rocket is not designed for that. Use a reverse proxy. Learn how reverse proxies and self signed certificates work. Don’t use traefik unless you know what you are doing… It’s probably tricky to use a self signed certificate. Use nginx with a self signed SSL certificate and reverse proxy to your IP. All this is documented at docs.rocket - change “letsencrypt” cert to “self signed” or do a general interweb search. ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [August 1, 2024, 12:09pm UTC](https://forums.rocket.chat/t/after-updating-to-6-10-0-browser-screen-is-stuck-on-loading-screen/20304/11 "2024-08-01T12:09:00Z")
Also 6.10.2 might help. > **[Release 6.10.2 · RocketChat/Rocket.Chat](https://github.com/RocketChat/Rocket.Chat/releases/tag/6.10.2)** > > Engine versions > > Node: 14.21.3 > MongoDB: 4.4, 5.0, 6.0 > Apps-Engine: 1.43.1 > > Patch Changes > > > Bump @rocket.chat/meteor version. > > > Bump @rocket.chat/meteor version. > > > (#32935) Fixed an issue that preve...