# Integration collabora online nextcloud 33.0.3

**URL:** <https://help.nextcloud.com/t/integration-collabora-online-nextcloud-33-0-3/244570>\
**Category:** ℹ️ Support\
**Tags:** docker, wopi, office, collabora-built-in, traefik\
**Created:** [May 18, 2026, 12:17pm UTC](https://help.nextcloud.com/t/integration-collabora-online-nextcloud-33-0-3/244570 "2026-05-18T12:17:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ernolf](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ernolf/32/77874_2.png) [@ernolf](https://help.nextcloud.com/u/ernolf)\
**Post date:** [May 18, 2026, 12:57pm UTC](https://help.nextcloud.com/t/integration-collabora-online-nextcloud-33-0-3/244570/2 "2026-05-18T12:57:30Z")

</div>

Hi @Jeremy_Vies,

> [@Jeremy\_Vies](#):
>
> docker official image

Before diving into the technical details, one thing worth clarifying: the image you’re using is not the official Nextcloud Docker image. The repository at [GitHub - nextcloud/docker: A community maintained docker micro-image for deploying Nextcloud on container platforms · GitHub](https://github.com/nextcloud/docker) carries this warning right at the top of its README:

> ⚠⚠⚠ This image is maintained by community volunteers and designed for expert use. For quick and easy deployment that supports the full set of Nextcloud Hub features, use the Nextcloud All-in-One docker container maintained by Nextcloud GmbH.

The officially supported Docker deployment is **Nextcloud AIO** (All-in-One), maintained by Nextcloud GmbH. With AIO, Nextcloud Office works out of the box — the Collabora integration, WOPI configuration, and internal networking are all handled automatically.

* * *

**What’s actually failing in your setup:**

Looking at your logs, the root cause is these two lines:

```auto
192.168.81.254 - "GET /index.php/apps/richdocuments/wopi/files/... HTTP/1.1" 500

```

`192.168.81.254` is your CODE server (COOLWSD) trying to fetch the document from Nextcloud via the WOPI protocol — and getting HTTP 500 back. Everything else follows from that:

- The `400` on `proxy.php` (WebSocket) is a consequence — Collabora can’t open a document it was never able to load
- The `404`s for SVG files are cosmetic and irrelevant

The most likely cause in a community Docker setup is that `wopi_allowlist` in `config.php` does not include the IP range of your CODE container (`192.168.81.x`). Since Nextcloud 22, WOPI requests from IPs not in the allowlist are rejected. Getting this right in a custom Docker + Traefik setup requires manual network configuration that AIO handles automatically.

To confirm the exact error you would need the `nextcloud.log` entries at the same timestamp — but honestly, if you’re not already deeply familiar with Nextcloud’s Docker networking requirements, switching to AIO will save you a lot of this kind of troubleshooting.

If you want to stay with the community image, the proper approach is to run Collabora CODE as a **separate container** with a correct reverse proxy configuration — not as the integrated `richdocumentscode` app. This HowTo covers exactly that setup, including network configuration and the domain-based allowlist approach: [Collabora CODE for Nextcloud with Docker](https://help.nextcloud.com/t/collabora-code-for-nextcloud-with-docker/216725)

* * *

h.t.h.

* * *

ernolf

---

_[View the full topic](https://help.nextcloud.com/t/integration-collabora-online-nextcloud-33-0-3/244570)._