Nextcloud collabora docker loading document fails

ℹ️ Support
, , ,
1

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    -31.0.0
  • Operating system and version (e.g., Ubuntu 24.04):
    • Ubuntu 24.04.1
  • Web server and version (e.g, Apache 2.4.25):
    • 2.4.52-1ubuntu4.13
      Reverse proxy and version _(e.g. nginx 1.27.2)
    • using apache:
      I have a domain available, for explanation I call it domain.com
      I A records in the DNS for nextcloud.domain.com and collabora.domain.com
      for both I have virtual hosts set up as explained in the protocol I was following (see
      below)
  • PHP version (e.g, 8.3):
    • 8.1.2-ubuntu2.20
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • right after installation
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no

Summary of the issue you are facing:

I followed the protocol (see above). In administration settings > office I get a green light i.e. connection to the collabora server is established. But when trying to generate a document (Files > + > new document > blank) I get the error ‘Document loading failed Failed to load Nextcloud Office - please try again later’.
docker logs nextcloud-collabora --tail 50 returns

wsd-00001-00031 2025-03-15 16:42:52.380702 +0000 [ websrv_poll ] WRN convert-to: Requesting address is denied: <nextcloud.domain.com IP>| wsd/ClientRequestDispatcher.cpp:452
wsd-00001-00031 2025-03-15 16:42:52.380743 +0000 [ websrv_poll ] WRN #32: Conversion requests not allowed from this address: ::ffff:| wsd/ClientRequestDispatcher.cpp:1818

Steps to replicate it (hint: details matter!):

  1. trying to open a document (see above)

Log entries

docker logs nextcloud-collabora --tail 50 returns

wsd-00001-00031 2025-03-15 16:42:52.380702 +0000 [ websrv_poll ] WRN convert-to: Requesting address is denied: <nextcloud.domain.com IP>| wsd/ClientRequestDispatcher.cpp:452
wsd-00001-00031 2025-03-15 16:42:52.380743 +0000 [ websrv_poll ] WRN #32: Conversion requests not allowed from this address: ::ffff:| wsd/ClientRequestDispatcher.cpp:1818

2

please review collabora integration guide and follow the troubleshooting steps

3

Thanks wwe for the quick reply.

I went through the troubleshooting steps. Acces to nextcloud and collabora could be verified.
I have a problem with installing the richdocuments app.
The commands given in the troubleshooting guide don’t seem to work.
The AI robot gives me these commands:
docker exec -u www-data nextcloud php occ app:install richdocuments returns ‘richdocuments already installed’
docker exec -u www-data nextcloud php occ app:enable richdocuments returns
‘richdocuments already enabled’

I don’t understand what you mean in the troubleshooting guide with this:

  • don’t use internal names or IPs e.g. http://127.0.0.1, http://office:9980, http://192.168.0.7:80
    and with this
    'don’t use plain http:// http://office:9980 , http://cloud:80 , http://cloud

  • this might allow communication from cloud to office and result in a green checkmark within Nextcloud Office settings. But communication from the client will fail.

The protocol from KarlF12 I was following (see link above) uses those settings extensively in the reverse proxy settings.

Do you have a better protocol available for me?

4

reverse proxy is (logically) not part of this integration. using localhost might be ok there depending on the installation variant… but all traffic between Collabora and Nextcloud happens using public FQDN and TLS… this all is explained in detail in the the guide, please take your time to understand how it works.

5

Thanks for the reply, wwe.
I think I gave it a considerable amount of time to understand ‘how it works’.

If you refer to the ‘integration guide’ I couldn’t find a solution there.
I also did a fair amount of research in this forum and found several post from people with the same problem but no real solution.

6

maybe @KarlF12 can give you pointers?

  • better for understanding the underlying technology?

    • @wwe is perfectly capable of explaining and describing the most complicated technology!

  • better for setting up?

    • @KarlF12 described his setup well and it works for him and others with similar setups

you could try alternative setups → How to install & configure Collabora CODE with Docker

but there is no “one setup fits all” method!
rather you should understand what is required Collabora integration guide to make it work and then adapt lessons learned for your configuration…

1 Like
7

Thanks for you input scubamuc. I think I have a pretty good understanding about how the ‘triangle’ works. The problem is to line up the internet environment, the LAN Network environment, the local host environment and the docker network environment in docker-compose.yml, the apache2 reverse proxy settings in nextcloud.conf and collabora.conf.

I duplicated this setup but it doesn’t work! Looking at the results I am getting from forum searches for nextcloud-collabora connectivity issues I am not the only one having this kind of problem.

8

hey @efe, so this is a hunch…

see Nextcloud Snap - Nextcloud Office where the user had an issue with Nextcloud office, loading documents in Nextcloud snap built in CODE…

your log is showing IPv6 addresses too, so maybe the solution @Moto used is an option for you?

that’s correct and we’re sorry to hear there are issues, it seems many users have a full dual stack, thus having IPv4 and IPv6 addresses. usually the latter is priorised if both are available. this causes connectivity to fail.

@wwe could you confirm?

9

That part stuck out to me as well. The log says it’s denying requests from IPv6 ::ffff: which is part of an odd backward compatibility attempt for IPv4. It should be possible to allow the range used by the Docker network in Collabora, although I don’t remember how to do it. I never got too far into Collabora’s inner workings.

If IPv6 is not used in the setup, maybe the IPv6 stack could be disabled for the Docker network, or the entire host?

1 Like
10

I can’t say for sure but definitely from my observation many or maybe all modern OS prefer IPv6 over IPv4.

Docker by default doesn’t enable IPv6. It must be manually enabled if required

I can confirm CODE works with IPv6 connectivity if everything is setup right. especially router config differs from IPv4

11

I could solve the IPv6 problem by setting the proto type=IPv4 in coolwsd.xml. The situation I am looking at is now:
nextcloud is up and running, in administration settings > office I have a green check mark saying that collabora online server is reachable.
However, when trying to open a document (Files > New > New Document) I give a filename, select the template ‘Blank’ , a new window opens saying loading '<‘document name>’.odt with a spinning wheel. This stops after about 20s with the message ‘Document loading failed. Failed to load nextcloud office - please try again later. Close’
From the graph wwe gives in the integration guide I conclude that the communication between client and collabora (GET command) is not working. Evidence for that is the docker logs nextcloud-collabora output : wsd-00001-00032 2025-03-19 06:37:48.617984 +0000 [ websrv_poll ] WRN convert-to: Requesting address is denied: <public IP for domains nextcloud.domain.eu and collabora.domain.eu| wsd/ClientRequestDispatcher.cpp:452
wsd-00001-00032 2025-03-19 06:37:48.618028 +0000 [ websrv_poll ] WRN #36: Conversion requests not allowed from this address: 192.168.80.1| wsd/ClientRequestDispatcher.cpp:1818
The local address 192.168.80.1 is a local LAN IP but not the one from the system running the docker containers. No idea where that comes from.
I assume that the configuration settings to tweak in order to fix this are in the coolwsd.xml settings. Am I right with that?
What settings do you think have to be modified?

12

Most of the time the client is not a problem, but you can confirm looking at browser dev tools (f12).

Most likely you are missing/wrong aliasgroup setting or wopi_allowlist settings. use search it helps! e.g. Nextcloud Office fails to load - #4 by emburaman

13

Thanks for the input wwe. Since by now I have made so many adjustments to the reverse proxy settings, the php configuration and in coolwsd.xml, I think I start from scratch hoping to apply lessons learned more pointedly.
@KarlF12 your protocol is from 2020 based on Ubuntu 18.04. Do you know about any important changes in the components Ubuntu, nextcloud collabora which could be a trap when following your protocol to the point?

14

It’ll mostly be the same, but there will be a few changes needed. For example a line had to be added to the Docker configurations for redis and MariaDB because of changes outside of Nextcloud. If you flip through the comments on my guide, you should find most or all of the changes needed. I think there were some posts about Collabora as well.

15

Thanks, I started from scratch followed KarlF12’s protocol to the point and am at the point where nextcloud can talk to collabora, but opening a document fails with the collabora log message being: wsd-00001-00032 2025-03-19 10:50:16.101837 +0000 [ websrv_poll ] WRN convert-to: Requesting address is denied: | wsd/ClientRequestDispatcher.cpp:509. I guess the only difference to the previous approach is, that there is no IPv6 Address involved. Again my question: “which settings do I modify to fix this?”

16

this refers to missing HTTPS… is SSL enabled or disabled

17

Thanks for your input, scubamuc. When I make the changes in coolwsd.xml, docker logs nextcloud-collabora --tail 50
returns
wsd-00001-00032 2025-03-19 13:34:14.719278 +0000 [ websrv_poll ] ERR #30: Looks like SSL/TLS traffic on plain http port| wsd/ClientRequestDispatcher.cpp:676

With the following steps I could fix the problem:

  1. Copy coolwsd to the local system docker cp nextcloud-collabora:/etc/coolwsd/coolwsd.xml ~/nextcloud/coolwsd.xml
  2. modify docker-compose.yml by adding
    volumes:
  • ./coolwsd.xml:/etc/coolwsd/coolwsd.xml:ro
    to the collabora service
  1. edit coolwsd.xml
    <server_name>collabora.domain.eu</server_name (collabora.domain.eu being the FQDN of the collabora server)
  2. Modify the reverse proxy settings in 011-collabora.conf (naming according to KarlF12’s protocol) by adding
    ProxyPass /browser https://127.0.0.1:9980/browser retry=0
    ProxyPassReverse /browser https://127.0.0.1:9980/browser
    as suggested here Proxy settings — SDK https://sdk.collaboraonline.com/ documentation
    and by adding
    ProxyPassMatch “/cool/(.*)/ws$” wss://127.0.0.1:9980/cool/$1/ws nocanon
    as suggested by wwe here
    Collabora can't open documents. Nextcloud 29 AIO; Apache Reverse Proxy
    -------Edit-------------
    I put this here in case someone has similar problems.
    Thanks KarlF12 for the protocol on which everything rests.
    Thanks wwe and scubamuc for your input here and in your other posts you pointed me to.
    I spent around 30 hours of focused work getting this up and running. Hopefully, that speaks to the complexity of the task rather than my lack of skill!

Lastly I recommend using KarlF12’s docker approach since with that it’s very easy to go back and start from scratch without having your server messed up. With docker basics chatgpt 4o can help very skilled.