Nextcloud not saving Collabora url

[rinkfaraway]

Nextcloud version: Nextcloud AIO v9.4.1
Operating system and version: 6.10.2-arch1-1 (64-bit)
Collabora version: 24.04.6.1

The issue you are facing:
Upon my host’s nightly restart, Nextcloud forgets the appropriate collabora url. Docker-compose down does not do the same thing.
Here’s what it’s supposed to look like (and works when I do it manually):

Here’s what it looks like after a host restart:

based on guides like: Nextcloud won't save the Collabora online wopi_url setting I tried a few config env variables in collabora without success.

    environment:
      - wopi_url=https://collabora.wallaby-gopher.ts.net
      - server_name=https://collabora.wallaby-gopher.ts.net
      - COLLABORA_DOMAIN=https://collabora.wallaby-gopher.ts.net

There’s not really any errors beyond “Can’t connect to the wrong server”, which isn’t particularly helpful. Any ideas?

[szaimen]

Hi, you probably need this: GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

[rinkfaraway]

Hi, I’m not sure anything is pertinent on that page. While there are a few mentions of Collabora/WOPI, none of them apply to saving them inside the administrator settings or docker-compose. Could you please specify on what you saw that was helpful?

[wwe]

I think there is some AiO internal logic which is supposed to run CODE on the same URL as NC.

@szaimen the user runs strange setup with tailscale VPN and runs separated CODE (as the one from AiO didn’t work) New AiO installation behind caddy and tailscale, Collabora not connecting? - #11 by rinkfaraway what is the right way to run AiO with with external CODE?

[ImHotiDog]

Does editing of docs and files work in collabora, does it disconnect after restart or does it never connect fully? Like are you able to edit files.
Could you try to disable cert verification from what i have heard tailscale grants own certs for its env.
The stuff below is just something to keep in mind:

Could you try doing this change:

      - wopi_url=https://LINKTOYOURNEXTCLOUDINSTANCE #Which domains are allowed to connect.
      - server_name=https://collabora.wallaby-gopher.ts.net # To specify collaboras server name
      - COLLABORA_DOMAIN=https://collabora.wallaby-gopher.ts.net # To specify where collabora will be hosted

Also i see im 3 days late so you might already have fixed the problem or moved on.
Goodluck!

[rinkfaraway]

@ImHotiDog

Also i see im 3 days late so you might already have fixed the problem or moved on.
Goodluck!

Yup, still working on it 3 days later haha. Thanks for helping!

@ImHotiDog

Does editing of docs and files work in collabora, does it disconnect after restart or does it never connect fully? Like are you able to edit files.
Could you try to disable cert verification from what i have heard tailscale grants own certs for its env.

Yes, I can open and edit documents when I manually change the url to the correct one every day after the restart. It saves the incorrect url so it never connects properly until I change it again.
Could you try doing this change:

@ImHotiDog

      - wopi_url=https://LINKTOYOURNEXTCLOUDINSTANCE #Which domains are allowed to connect.
      - server_name=https://collabora.wallaby-gopher.ts.net # To specify collaboras server name
      - COLLABORA_DOMAIN=https://collabora.wallaby-gopher.ts.net # To specify where collabora will be hosted

I’d only ever tried running one of those environmental variables at once.
With all three for some reason it just points to https when it connects, but now files DON’T open like they were when I was manually inputting the url.

and after a restart we’re back to nextcloud instead of collabora again

Commenting - server_name=https://collabora.wallaby-gopher.ts.net lets the documents open again, but again, upon restart back to nextcloud.

I’m able to open documents with and without disabling certificates when server_name isn’t used.

I notice in the nextcloud log it says collabora is still the public WOPI even though we set it to nextcloud.

Checking configuration

🛈 Configured WOPI URL: https://nextcloud.wallaby-gopher.ts.net

🛈 Configured public WOPI URL: https://collabora.wallaby-gopher.ts.net

🛈 Configured callback URL: 

Failed to fetch discovery endpoint from https://nextcloud.wallaby-gopher.ts.net

cURL error 28: Operation timed out after 5002 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nextcloud.wallaby-gopher.ts.net/hosting/discovery

[szaimen]

@szaimen

probably need this: GitHub - nextcloud/all-in-one: The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

This is the correct advice. Disabling collabora in the AIO interface should allow you to keep your domain and the app installed.

[rinkfaraway]

Hello, I removed those previously discussed variables and added - NEXTCLOUD_KEEP_DISABLED_APPS=true to nextcloud’s env, but upon restart we still have the wrong url. I added the variables back in again (less the server_name) and behavior was the same. In the admin logs I’m getting a lot of repeat errors:

[no app in context] Fatal: Could not boot files_trackdownloads: Call to undefined method OC\Server::getEventDispatcher()
	GET /apps/logreader/api/log?offset=50&query=
	from 100.122.199.7 by admin at Aug 15, 2024, 4:01:55 PM

Saying that it allowed me to keep the old app installed got me thinking though

I thought this bugger would be minding its own buisness as long as I wasn’t using the CODE, wrong! I disabled it and now the right url is saved without any extra vars necessary. Thanks everyone!