# Kubernetes installation not updating server\_name?

**URL:** <https://forum.collaboraonline.com/t/kubernetes-installation-not-updating-server-name/3384>\
**Category:** Installation & Configuration\
**Created:** [February 6, 2025, 10:00am UTC](https://forum.collaboraonline.com/t/kubernetes-installation-not-updating-server-name/3384 "2025-02-06T10:00:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![marinho](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@marinho](https://forum.collaboraonline.com/u/marinho)\
**Post date:** [February 6, 2025, 10:00am UTC](https://forum.collaboraonline.com/t/kubernetes-installation-not-updating-server-name/3384/1 "2025-02-06T10:00:37Z")

</div>

Hi all,

I currently have a server with Collabora Online working, which I installed by using “apt install coolwsd”, nginx and let’s encrypt.

I also have an instance of NextCloud which points to that Collabora working all fine as expected.

Now, I decided to setup a new Collabora server, this time using Kubernetes, and then I followed [this tutorial](https://www.collaboraonline.com/blog/how-to-easily-deploy-collabora-online-on-your-kubernetes-setup/) for it.

I chose to use nginx, installed it, and all tests seem the installation worked fine, except that, when I update my NextCloud to point to that new server instead, it shows this error below:

> Your browser has been unable to connect to the Collabora server: [http://no2.mydomain.com](http://no2.mydomain.com)  
> This URL is determined on the Collabora server either from the configured URL or the server\_name parameter in coolwsd.xml.

My values.yaml has this content below:

```auto

collabora:
  server_name: no2.mydomain.com
  password: admin
  username: admin

autoscaling:
  enabled: true
  minReplicas: 1
  maxReplicas: 3

```

I logged into the pod to see how /etc/coolwsd/coolwsd.xml looks like, and it has no value in the server\_name tag, as you can see below:

```auto
<server_name desc="External hostname:port of the server running coolwsd. If empty, it's derived from the request (please set it if this doesn't work). May be specified when behind a reverse-proxy or when the hostname is not reachable directly." type="string" default=""></server_name>

```

I also tried with aliasgroups and/or ssl.enable=true:

```auto
collabora:
  server_name: no2.mydomain.com
  aliasgroups:
    - host: "http://no2.mydomain.com:443"
  extra_params: --o:ssl.enable=true
  password: admin
  username: admin

```

But got the same result ☹

Does anyonw know what can be wrong?

Thanks

---

<div class="post-metadata">

**Author:** ![Loubens](https://avatars.discourse-cdn.com/v4/letter/l/9fc29f/32.png) [@Loubens](https://forum.collaboraonline.com/u/Loubens)\
**Post date:** [February 7, 2025, 10:34am UTC](https://forum.collaboraonline.com/t/kubernetes-installation-not-updating-server-name/3384/2 "2025-02-07T10:34:42Z")

</div>

Hi, for my part I created configmaps rather than the values.yaml file, so I updated my coolwsd.xml and I send it to the pods via the configmap.

---

<div class="post-metadata">

**Author:** ![marinho](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@marinho](https://forum.collaboraonline.com/u/marinho)\
**Post date:** [February 9, 2025, 8:28am UTC](https://forum.collaboraonline.com/t/kubernetes-installation-not-updating-server-name/3384/3 "2025-02-09T08:28:55Z")

</div>

hummm, I see. Did you follow any tutorial or guidance on how to install Collabora on Kubernetes using ConfigMap? I used this [here, that’s based on a Helm chart](https://github.com/CollaboraOnline/online/tree/master/kubernetes/helm), and as I’m neither too good on Collabora nor on K8s, I guess I wouldn’t know how to setup from scratch without a tutorial or the like.

---

<div class="post-metadata">

**Author:** ![Loubens](https://avatars.discourse-cdn.com/v4/letter/l/9fc29f/32.png) [@Loubens](https://forum.collaboraonline.com/u/Loubens)\
**Post date:** [February 10, 2025, 7:55am UTC](https://forum.collaboraonline.com/t/kubernetes-installation-not-updating-server-name/3384/4 "2025-02-10T07:55:17Z")

</div>

I’m sorry, but I didn’t follow a tutorial, I had the idea to add the configmap because I had problems testing with the values.yaml.  
I create the configmap from a file that I extracted from a pod, here is the command I use to create the configmap:  
kubectl create configmap coolwsd --from-file=coolwsd.xml --dry-run=client -o yaml | kubectl apply -f -

Then you have to attach the volume in your POD deployment:

```auto
volumes:
  - name: "coolwsd"
    configMap:
        name: "coolwsd"

```

And mount it also for PODS:

```auto
volumeMounts:
  - name: "coolwsd"
    mountPath: "/etc/coolwsd/coolwsd.xml"
    subPath: "coolwsd.xml"

```

Don’t forget to modify the lines:  
server name with the dns name that you give to your server  
frame\_ancestors with the servers authorized to connect to your CODE

---

<div class="post-metadata">

**Author:** ![darshan](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/darshan/32/2230_2.png) [@darshan](https://forum.collaboraonline.com/u/darshan)\
**Post date:** [March 13, 2025, 5:52am UTC](https://forum.collaboraonline.com/t/kubernetes-installation-not-updating-server-name/3384/5 "2025-03-13T05:52:47Z")

</div>

Closed on March 13, 2025, 5:52am UTC


