# Site URL is always http://localhost:3000

**URL:** <https://forums.rocket.chat/t/site-url-is-always-http-localhost-3000/18369>\
**Category:** Community Support\
**Tags:** kubernetes\
**Created:** [November 9, 2023, 4:01pm UTC](https://forums.rocket.chat/t/site-url-is-always-http-localhost-3000/18369 "2023-11-09T16:01:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![oliver1](https://avatars.discourse-cdn.com/v4/letter/o/eb9ed0/32.png) [@oliver1](https://forums.rocket.chat/u/oliver1)\
**Post date:** [November 9, 2023, 4:01pm UTC](https://forums.rocket.chat/t/site-url-is-always-http-localhost-3000/18369/1 "2023-11-09T16:01:58Z")

</div>

### Description

I deployed Rocket.Chat on a Kubernetes cluster using the Helm chart from [helm-charts/rocketchat at master · RocketChat/helm-charts · GitHub](https://github.com/RocketChat/helm-charts/tree/master/rocketchat). The deployment went smoothly, and I can access the site from my browser using the host I specified in the values.yaml. However, the site is stuck at the loading indicator with three dots.

### Server Setup Information

In the Pod it logs:

±---------------------------------------------+  
| SERVER RUNNING |  
±---------------------------------------------+  
| Rocket.Chat Version: 6.4.4 |  
| NodeJS Version: 14.21.3 - x64 |  
| MongoDB Version: 6.0.10 |  
| MongoDB Engine: wiredTiger |  
| Platform: linux |  
| Process Port: 3000 |  
| Site URL: [http://localhost:3000](http://localhost:3000) |  
| ReplicaSet OpLog: Enabled |  
| Commit Hash: d994a6ff33 |  
| Commit Branch: HEAD |  
±---------------------------------------------+

### Any additional Information

Console output when I navigate to the URL I set in the host value (I modified my hosts file to point to the load balancer URL):  
 ![image](https://us1.discourse-cdn.com/flex021/uploads/rocketchat/original/2X/4/4e97e75f7976fc21dd89b1dfb154e1f879c28612.png)

To me, it looks like the Site URL from the values.yaml hosts value is not set within the JavaScript code. However, the environment variable ROOT\_URL is correctly set to the URL in the pod.

---

<div class="post-metadata">

**Author:** ![elix](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/elix/32/4982_2.png) [@elix](https://forums.rocket.chat/u/elix)\
**Post date:** [November 12, 2023, 2:22pm UTC](https://forums.rocket.chat/t/site-url-is-always-http-localhost-3000/18369/2 "2023-11-12T14:22:39Z")

</div>

I encounter the same problem. Any workaround?

---

<div class="post-metadata">

**Author:** ![oliver1](https://avatars.discourse-cdn.com/v4/letter/o/eb9ed0/32.png) [@oliver1](https://forums.rocket.chat/u/oliver1)\
**Post date:** [November 12, 2023, 3:22pm UTC](https://forums.rocket.chat/t/site-url-is-always-http-localhost-3000/18369/3 "2023-11-12T15:22:46Z")

</div>

Not yet, unfortunately.

---

<div class="post-metadata">

**Author:** ![elix](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/elix/32/4982_2.png) [@elix](https://forums.rocket.chat/u/elix)\
**Post date:** [November 13, 2023, 9:46am UTC](https://forums.rocket.chat/t/site-url-is-always-http-localhost-3000/18369/4 "2023-11-13T09:46:51Z")

</div>

I found one. You can install 6.3.10 first, then upgrade to 6.4.5. The problem is the mongoDB init code I guess. Once it init finish, it won’t change between updates.  
In helm value.yaml something like this:  
image:  
repository: registry.rocket.chat/rocketchat/rocket.chat  
tag: 6.3.10  
pullPolicy: IfNotPresent

---

<div class="post-metadata">

**Author:** ![oliver1](https://avatars.discourse-cdn.com/v4/letter/o/eb9ed0/32.png) [@oliver1](https://forums.rocket.chat/u/oliver1)\
**Post date:** [November 13, 2023, 9:48am UTC](https://forums.rocket.chat/t/site-url-is-always-http-localhost-3000/18369/5 "2023-11-13T09:48:18Z")

</div>

After revising the entire `values.yaml` file, removing the previous deployment, and reinstalling it with the updated `values.yaml`, everything now functions correctly. Unfortunately, I am unable to pinpoint the exact issue in my initial attempt. Nevertheless, I’ve identified some aspects that may assist others facing similar problems:

Ensure to:

- Set the host to the correct URL without including the protocol, for example, use “rocketchat.mycompany.local” instead of “https://…”
- Configure the ingress (if applicable) without specifying a host, as the chart will utilize the host specified in the `values.yaml`
- (Even though it may seem trivial, it can happen to the best of us) Make sure to actually use the `values.yaml` in your Helm command.