I have a problem with the availability to my collabora docker connection.
I use nextcloud newest version 30.0.2 (same behaviour with other 30.x.x versions) and there Nextcloud office is only available for a short period of time.
For example, I work with nexcloud office without any problems. If I do not use it for a couple of hours and go back, I get an unauthorized WOPI error.
The Collabora online server meanwhile is still up and running and answers wir “OK”.
When I switch to office settings in nextcloud and save the collabora server URL again, Nextcloud office works again for a couple of hours.
Any Idea how I can fix this, not to go to save every time I like to use Nextcloud office after a pause?
as you didn’t provide any useful technical information we have to guess - likely you are hosting on dynamic IP and your public IP changes which brakes the connection… at the end the public IP of the accessing server must exist in “Allow list for WOPI requests”… start with 0.0.0.0/0 to allow every IP and reduce step by step if required.
Sounds quite familiar. After updating to 29 and trying to resolve issues by pushing towards 30, this happens every time the server is restarted. In my case it’s a fixed IP and all routing is done through reverse proxy, but also with a local network through tailscale and fixed server names in DNS, this still comes up. (So in practice, any machine has three routes to be called: over the regular internet, local name and external IP within the tailnet. None of these solved the issue).
Thanks again for the reply and your help. I still did not figured out how to solve the issue.
What I can reproduce is, that when I go to Office settings in nextcloud and press save there, I am able to open office documents again after a couple of seconds. If nextcloud rests for a while, it again fails and will not open office files.
To give some details of my setup:
I am using Proxmox and therefor LXC Containers!
…running nextcloud in an LXC docker container (turnkey). Domainname is proxied via cloudflare and has a public IPv4 and IPv6 from the cloudflare network.
My collabora server is running on a different LXC, also via proxied cloudflare DNS and has also a public IPv4 and IPv6 from the cloudflare network.
As you mentioned that adding the IP address of the server to the allowed WOPI list, I was not succesful so far.
For further context:
I guess you mean the IP address of the collabora server, right?
How should I setup this in my scenario?
My LXC container nextcloud is setup with a public IPv6 with a local (internal IPv4). Due to hav no public IPv4 availabe by my own, I use Cloudflare to get a valid public IPv4 and IPv6, which works fine. I can do nextlcoud updates and download apps, which fails, when I run the nextcloud without Cloudflare and only a public IPv6 setup.
Which IP shoud I use? So far I could not solve the issue with entering the IPv6 of the collabora XC Container with xxxx::1000/64 as shown here:
Suggestion: As saving the collabora server in the nextcloud settings seems to kind of wakeup the connection in between both, is there a way, where I can setup a crontab, to do this on a regular base? Lets say every 15min. mimic the save action in a crontab? My thinking is, that this cloud keep the connection alive?
What are your thoughts?
in general there is no need to “keep the connection” alive. doing so would maybe address symptoms but not the root cause.
you can see the address of the remote system in the logs. Start troubleshooting the problem systematically - review the Collabora integration guide and check which part of the the “communication triangle” is broken once the issue starts. This helps you understand where to apply countermeasures.
I am also thinking about cloudflare proxies.
For now I added a crontab of every 5 minutes with and will lock if this helps:
wget -N /var/www/nextcloud/collabora/index.html https://office.mydomain.xy
Maybe I need to add the cloudflare IPs to the trusted domains in my nextcloud config.php?
For additional information:
My collabora docker runs in my homelab and gets it’s public URL via a cloudflare tunnel. So https://office.mydomain.xy tunnels to my local server.
I see for example, that the domain gets an IPv6 from the cloudflare IP list. But the IPv4 cloudflare provides is 104.21.xx.xx which is not in the list cloudflare shows in there list.
This topic was automatically closed after 89 days. New replies are no longer allowed.