# Setup Collabora Code with docker compose on Azure

**URL:** <https://forum.collaboraonline.com/t/setup-collabora-code-with-docker-compose-on-azure/2965>\
**Category:** User Support\
**Created:** [September 12, 2024, 7:06pm UTC](https://forum.collaboraonline.com/t/setup-collabora-code-with-docker-compose-on-azure/2965 "2024-09-12T19:06:16Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gustavo](https://avatars.discourse-cdn.com/v4/letter/g/a9adbd/32.png) [@Gustavo](https://forum.collaboraonline.com/u/Gustavo)\
**Post date:** [September 12, 2024, 7:06pm UTC](https://forum.collaboraonline.com/t/setup-collabora-code-with-docker-compose-on-azure/2965/1 "2024-09-12T19:06:16Z")

</div>

We are trying to setup a Collabora CODE to deploy on Azure. We are using docker-compose and we are getting an error while connecting to the websocket

docker-compose.yaml:

```yaml
version: '3'
 
services:
  wopi-client:
    image: collabora/code:latest
    container_name: wopi-client
    expose:
      - 9980
    ports:
      - 9980:9980
    environment:
      - username=<username>
      - password=<password>
      - server_name=collabora-code.domain.com
      - domain=wopi\.host-api\.domain
      - DONT_GEN_SSL_CERT=1
      - extra_params=--o:net.frame_ancestors=frontend.domain --o:ssl.termination=true --o:ssl.enable=false --o:logging.level=trace
    restart: always
    volumes:
      - "${SOME_STORAGE_IN_AZURE}/libre-office/ca-chain.cert.pem:/etc/coolwsd/ca-chain.cert.pem"
      - "${SOME_STORAGE_IN_AZURE}/libre-office/key.pem:/etc/coolwsd/key.pem"
      - "${SOME_STORAGE_IN_AZURE}/libre-office/cert.pem:/etc/coolwsd/cert.pem"

```

We get this screen:  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/collaboraonline/original/2X/8/89b6d718c7d6eec147e7345168af7835c0e46eae.png)

And a console error that doesn’t provide any info at all, it just says “can’t connect to wss://”

Can anybody help me with this?

---

<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:** [September 13, 2024, 7:10am UTC](https://forum.collaboraonline.com/t/setup-collabora-code-with-docker-compose-on-azure/2965/2 "2024-09-13T07:10:40Z")

</div>

Hello @Gustavo Welcome to collabora online forums.

I have seen this issue in some forum topics, yes here it is [Failure after CODE update to 23.05.8.4 deb Package](https://forum.collaboraonline.com/t/failure-after-code-update-to-23-05-8-4-deb-package/2368/1)

Try solution mentioned in above topic them let me know if it works or not might be other configuration error on reverse proxy.

ATB,  
Darshan

---

<div class="post-metadata">

**Author:** ![mmeeks](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/mmeeks/32/371_2.png) [@mmeeks](https://forum.collaboraonline.com/u/mmeeks)\
**Post date:** [September 13, 2024, 10:38am UTC](https://forum.collaboraonline.com/t/setup-collabora-code-with-docker-compose-on-azure/2965/3 "2024-09-13T10:38:03Z")

</div>

Also - it might be worth enabling:

```
<hexify_embedded_urls desc="Enable to protect encoded URLs from getting decoded by intermediate hops. Particularly useful on Azure deployments" type="bool" default="false"></hexify_embedded_urls>

```

and testing that - I’m not sure it gets a lot of love; but in the past we’ve seen Azure proxies and ingress points essentially mangling the WOPISRC URLs as they go past which creates a lot of problems 🙂

Would be interested to hear how that goes.

---

<div class="post-metadata">

**Author:** ![Gustavo](https://avatars.discourse-cdn.com/v4/letter/g/a9adbd/32.png) [@Gustavo](https://forum.collaboraonline.com/u/Gustavo)\
**Post date:** [September 13, 2024, 1:18pm UTC](https://forum.collaboraonline.com/t/setup-collabora-code-with-docker-compose-on-azure/2965/4 "2024-09-13T13:18:34Z")

</div>

Hi, thank you so much for replying! We are deploying via Docker compose, how would one uninstall and install again - as suggested in the topic’s accepted answer - in this situation?

---

<div class="post-metadata">

**Author:** ![Gustavo](https://avatars.discourse-cdn.com/v4/letter/g/a9adbd/32.png) [@Gustavo](https://forum.collaboraonline.com/u/Gustavo)\
**Post date:** [September 13, 2024, 1:22pm UTC](https://forum.collaboraonline.com/t/setup-collabora-code-with-docker-compose-on-azure/2965/5 "2024-09-13T13:22:11Z")

</div>

Hi @mmeeks, thanks for the suggestion! I’ll ask the guys that are handling the deployment to add `--o:hexify_embedded_urls=true` to the extra\_params and let you know the results

Edit: It worked! Thank you so much @mmeeks!

---

<div class="post-metadata">

**Author:** ![Gustavo](https://avatars.discourse-cdn.com/v4/letter/g/a9adbd/32.png) [@Gustavo](https://forum.collaboraonline.com/u/Gustavo)\
**Post date:** [September 13, 2024, 3:51pm UTC](https://forum.collaboraonline.com/t/setup-collabora-code-with-docker-compose-on-azure/2965/6 "2024-09-13T15:51:45Z")

</div>

Unrelated question, should I keep ssl disabled and let azure handle https or should I set ssl.enable=true and ssl.termination=false?

---

<div class="post-metadata">

**Author:** ![mmeeks](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/mmeeks/32/371_2.png) [@mmeeks](https://forum.collaboraonline.com/u/mmeeks)\
**Post date:** [September 13, 2024, 6:33pm UTC](https://forum.collaboraonline.com/t/setup-collabora-code-with-docker-compose-on-azure/2965/7 "2024-09-13T18:33:44Z")

</div>

Depends on your use-case; what is that ? ultimately getting someone else to do SSL unwrap and distributing load between multiple containers would be normal for a large setup.