# Collabora + Nextcloud + Docker = Failure **URL:** \ **Category:** ℹ️ Support\ **Tags:** docker, collabora-online\ **Created:** [December 6, 2021, 9:08pm UTC](https://help.nextcloud.com/t/collabora-nextcloud-docker-failure/128696 "2021-12-06T21:08:00Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![flkiwi](https://help.nextcloud.com/letter_avatar/flkiwi/32/5_5575768a8748004e209b776fc1b2916d.png) [@flkiwi](https://help.nextcloud.com/u/flkiwi)\ **Post date:** [December 6, 2021, 9:08pm UTC](https://help.nextcloud.com/t/collabora-nextcloud-docker-failure/128696/1 "2021-12-06T21:08:00Z")
**Environment** Official docker image of Nextcloud, updated to v23.0.0 but failure was happening before update Official docker image of Collabora CODE (latest) Using Portainer to manage containers NPM running in front of the docker containers collabora.mydomain points to Collabora CODE container nextcloud.mydomain points to Nextcloud Both are https with a Let’s Encrypt certificate managed by NPM **Behavior** The most annoying behavior is that this worked flawlessly … and then it didn’t, with no configuration changes whatsoever. Nextcloud works great. It is configured and operating properly. In the Nextcloud settings, under Office, I have specified a separate Collabora server. For all of the following I see a green tick that the server is available. - collabora.mydomain - [https://collabora.mydomain](https://collabora.mydomain) - [https://admin:password@collabora.mydomain](https://admin:password@collabora.mydomain) If I click a document in Nextcloud, I receive the following error: “Document loading failed. Failed to load NextCloud Office - please try again later” Collabora returns “OK” at the root of collabora.mydomain, but if I enter the Collabora admin, I receive the error that “Server has been shut down please reload the page.” In the Collabora CODE logs, there are a couple of interesting entries, that appear to relate to a similar issue. ```auto wsd-00001-00041 2021-12-06 20:42:17.498792 +0000 [websrv_poll] ERR #24 Exception while processing incoming request: [GET /cool/https%3A%2F%2F{NEXTCLOUD.MYDOMAIN}%2Findex.php%2Fapps%2Frichdocuments %2Fwopi%2Ffiles%2F2838_occv53kiq6gp%3Faccess_token% {TOKEN}%26access_token_ttl% {TTL}%26permission%3Dedit/ws?WOPISrc=https%3A%2F%2F{TRUNCATED NEXTCLOUD.MYDOMAIN}...]: Invalid or unknown request.| wsd/COOLWSD.cpp:{NUMERIC STRING}&compat=/ws HTTP/1.1 ``` and ```auto wsd-00001-00041 2021-12-06 20:47:09.652369 +0000 [websrv_poll] WRN convert-to: Requesting address is denied: ::ffff:{SUBNET GATEWAY IP ADDRESS}| wsd/COOLWSD.cpp:2593 ``` (Forgive me if I’ve deleted irrelevant information, but I cannot tell what obfuscated information might contain proprietary data.) This is pretty clearly a Collabora configuration issue, so I’m hesitant to even post the question in the Nextcloud forum. But this is an active, engaged community and I’m hoping someone has solved the same issue, particularly as this integration is clearly an out of the box feature now. **Attempted Troubleshooting** 1. Restarted the docker containers for Nextcloud and Collabora CODE in various orders 2. Removed and pulled the Collabora CODE image 3. Started the Collabora container from the command line with CLI options based on the documentation provided by Nextcloud, Collabora, and the community 4. Tried both http and https access to the Collabora CODE server 5. Updated Nextcloud 6. Per [this thread](https://help.nextcloud.com/t/psa-how-to-get-collabora-working-on-nextcloud-23/128511), I downloaded a working Collabora frontend. The behavior is different but still fails with a brief and very small error of “The server has been disconnected”. All other behavior is the same (including the green tick indicating availability). **Questions** 1. Is the “server shut down” issue related to the above issues 2. How do I start the server if I have followed the configuration docs that do not indicate anything about starting the server One specific question I have is that, if I need to edit a configuration file, where in the Collabora container is the file located? **Additional Information** _ENV variables (Collabora CODE container):_ domain: nextcloud\.mydomain # two slashes not showing here DONT\_GEN\_SSL\_CERT extra\_params: --o:ssl.enable=true LC\_CTYPE: C.UTF-8 password: {password} PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin server\_name: office.mydomain username: {my username} The url **[https://office.mydomain/hosting/discovery](https://office.mydomain/hosting/discovery)** returns the XML namespace file. ---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [December 7, 2021, 9:53am UTC](https://help.nextcloud.com/t/collabora-nextcloud-docker-failure/128696/2 "2021-12-07T09:53:11Z")
At the moment there are lot of changing parts within Collabora integration.. Collabora changed /loolwsd used for ages to /coolwsd which may require change in your [reverse proxy configuration](https://forum.collaboraonline.com/t/upgrade-from-loolwsd-to-coolwsd-broke-nextcloud-use/742/8) (was not the case for me with NC22+traefik).. additionally there seems to be an issue with the [richdocuments app 5.0.0](https://help.nextcloud.com/t/psa-how-to-get-collabora-working-on-nextcloud-23/128511) as you referenced already (didn’t dig deeper if both is related). > [@flkiwi](#): > > The url **[https://office.mydomain/hosting/discovery](https://office.mydomain/hosting/discovery)** returns the XML namespace file. this one is already a good sign - collabora seems to work. My observation is Collabora container is pretty slow on start - if you perform any changes please wait 2-3 minutes before you start testing.. When I upgraded my Collabora container last time I had the feeling I had to visit Nextcloud configuration page and tick “own server” again (maybe to make NC detect loowsd-\>coolwsd change). Check this post - NC22+traefik - but maybe it helps: > [@Docker Compose for Nextcloud + Collabora + Traefik?](https://help.nextcloud.com/t/docker-compose-for-nextcloud-collabora-traefik/127733/2): > > I have such setup running 1,5y and survived 2 major updates and hardware move without issues, the setup is stable. maybe this is the least problematic advanced feature of NC… (works much more stable than talk+coturn). as I don’t use Collabora often first start takes multiple seconds but then it works good on old i3 desktop… The only big problem I experienced was Collabora outage for multiple weeks caused by Collabora until I discovered the solution in Collabora forums (Collabora+SNI). The prob… ---
**Author:** ![punk](https://help.nextcloud.com/letter_avatar/punk/32/5_5575768a8748004e209b776fc1b2916d.png) [@punk](https://help.nextcloud.com/u/punk)\ **Post date:** [March 2, 2022, 1:07pm UTC](https://help.nextcloud.com/t/collabora-nextcloud-docker-failure/128696/3 "2022-03-02T13:07:51Z")
Ok I have a very similar setup (arm64): - NC23 running in docker container from latest image - Collabora running in its own container as well - Docker container with NPM managing domain redirection and SSL - Green tick on connection to server within NC UI I get the return from the XML namespace as well and similar errors in the logs of the collabora container when trying to open a document in NC. Impossible to have a working collabora (except with demo server). What I tried : reading the freakin entire internet for clues, and tried various things. Nothing works yet. I tried NC 22, NC 23, collabora 4.2 or 5, NC installed within docker or from apt, various extra\_params → same results. I may need to look further on the NPM configuration but I don’t know much about NGINX. If anyone has a Docker{NC23+Collabora+NPM) configuration working on arm64, I would appreciate sharing for configuration tips (especially within NPM, which I’m not 100% sure). I also use NPM for reverse proxying other docker containers which are reachable. ---
**Author:** ![bearchen](https://help.nextcloud.com/letter_avatar/bearchen/32/5_5575768a8748004e209b776fc1b2916d.png) [@bearchen](https://help.nextcloud.com/u/bearchen)\ **Post date:** [August 1, 2022, 10:02am UTC](https://help.nextcloud.com/t/collabora-nextcloud-docker-failure/128696/4 "2022-08-01T10:02:46Z")
# **You can refer to the configuration in my article.** # [Use HTTPS with Ubuntu 22.04, apache, Nextcloud and Collabora(Docker)](https://help.nextcloud.com/t/use-https-with-ubuntu-22-04-apache-nextcloud-and-collabora-docker/142880) ---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [December 14, 2024, 2:43pm UTC](https://help.nextcloud.com/t/collabora-nextcloud-docker-failure/128696/5 "2024-12-14T14:43:45Z")