This Caddy forum post seems to support my observations as it suggests that the Caddy error arises from an upstream server terminating a connection.

Rather, the error is flagged when Collabora exits and returns control to Nextcloud and

I noticed that saving a document within Collabora doesn't give rise to the error.

There isn't any evidence of a problem in the Nextcloud and Collabora logs at around the time the issue is flagged by Caddy.

There has not been any outwardly visible impact (such as file corruption) arising from the error in the weeks I've been trialling Nextcloud-Collabora integration.

It should suffice for far larger numbers when talking about webinars or small (1-5 participants) meetings. This setup is estimated to work for at least about 150 concurrent users. I'm tempted to ignore the error for several reasons: 32 GB free disk (for caching, data will not be stored) 4 Cores i7/Xeon. Fixed: Add Collabora Offices program directory to LDLIBRARYPATH in AppImage on ARM64, in order to find the right libxml2.so. Collabora Online - Built-in CODE Server (ARM64) 6.4.14. So, I'm happy to deal with it in this discussion area (though I'd still like to bring it to the attention of as it is Caddy flagging the error). Download Collabora Online - Built-in CODE Server (ARM64) 6.4.202. I was going to suggest that you repost this in the Caddy discussion area, but the more I looked into this, the more I felt the Caddy error was due to the behaviour of Collabora within the Nextcloud environment. I hadn't noticed this error before, but it does appear in my Caddy log as well. $COLLABORA_DOMAIN is set to to expand.Thanks for pointing this out. My docker-compose.yaml has gone through several iterations in an attempt to get this working, but my current attempt is below: version: '3' I can also access the admin page at /loleaflet/dist/admin/admin.html When I point my browser at I see the OK message.

I have the following subdomains all pointing at my server:Ĭ Īs I mentioned, the Nginx and Nextcloud setups are great.

There are multiple bits that I might have got wrong so I'll dump as much info as I can here. My issue is that I cannot get my Collabora CODE instance to link to Nextcloud. So far I have Nginx and Nextcloud working really nicely with persistent volumes so that my configs survive kill & rm. I am trying to get a docker-compose.yaml together to run Nextcloud and Collabora CODE via Nginx Proxy Manager.

Collabora code requirements