fix: initial stuck client if root_url is wrong

[debdutdeb]

closes #30990
closes #30931
closes #31169

Proposed changes (including videos or screenshots)

Issue(s)

Steps to test or reproduce

Further comments

[changeset-bot]

⚠️ No Changeset found

Latest commit: a55c36f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

Merging #30913 (a55c36f) into develop (a271587) will decrease coverage by 8.90%.
The diff coverage is 75.00%.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #30913      +/-   ##
===========================================
- Coverage    57.77%   48.88%   -8.90%     
===========================================
  Files          885     3272    +2387     
  Lines        20228    80283   +60055     
  Branches      3766    16318   +12552     
===========================================
+ Hits         11687    39246   +27559     
- Misses        7848    36422   +28574     
- Partials       693     4615    +3922     

Flag	Coverage Δ
e2e	51.35% <ø> (+8.98%)	⬆️
e2e-api	40.72% <75.00%> (?)
unit	77.33% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[geekgonecrazy]

This is extremely disruptive to brand new deployments.

Our 1-click installation images are all affected by this. Because you can't access them with your browser at localhost but Rocket.Chat by default has localhost on root_url and site url

So they'll access at the public ip and it's broken. Very bad first impression

[HassbergKliniken]

Hello,

I still have the 3 dots after the update.

It's a clean environment. I tested a lot with the ROOT_URL variable and also tested in MongoDB with the SITE_URL for examble:

mongosh
use rocketchat
db.rocketchat_settings.update({"_id" : "Site_Url"},{$set:{value:"<http://chat2:3000>"}})

I can rotate it however I want, the 3 dots remain.

Another idea what I can test?