UCS vm of Nextcloud works fine, but not OnlyOffice despite combo bundle

[JustDave]

The UCS Uninvention vm of nc works straight out of the box with just minimal config.

The download I used was:

https://appcenter.software-univention.de/univention-apps/current/nextcloud-onlyoffice/Univention-App-nextcloud-onlyoffice-ESX.ova

It was very easy to deploy in vCenter.

I gave it a real internet outside fqdn, internal ip, dns, gateway, and nc works right away, even with a ldap external storage. I am able to install LetsEncrypt in the UCS and that works with nc with a real certificate.

However, I have no idea how to get it to work with the included pre-installed OO. It does come already enabled from nc Apps, but still doesn’t work even if a disable and reenable it. Clicking on a .docx just let’s you download it.

Nc does work with the OO demo server, but not when I disable the demo, regardless of what syntax I populate the server settings with, including grabbing the secret out from the OO welcome.

I am able to see the fdqn and its internet ip in the trusted_domains.

I am able to use UCS to update from nc24 to nc29, and OO too. I check to see if it works in-between each update, yet still no.

I am thinking this UCS vm of nc/OO may require some fiddling from the console, and perhaps I would get better results with the UCS vm of Nextcloud standalone, and new install OO from there.

[Mornsgrans]

Did you install OnlyOffice from Univention App-Center?

Is the OnlyOffice docker container running? - Login to console and type “docker ps” - two docker containers should run: Nextcloud and OnlyOffice.

[JustDave]

That was one of the first things I did to verify that I have deployed the correct image from UCS, and the oo welcome page shows that.

The UCS image is a rather large 2.7G download because it combos both nc and oo pre-installed.

[Mornsgrans]

The App-Center shows, that Nextcloud and OnlyOffice need to be upgraded.

Because the is a version dependency between the Nextcloud OnlyOffice app and the Univention OnlyOffice (Docker-App), you should take care, to keep the latest release of both Apps and if you update the Nextcloud OnlyOffice App, you also need to upgrade the Univention OnlyOffice (Docker-)App, as far it an update is available.

(same with Collabora and Collabora CODE on UCS)

[JustDave]

In my experience, vm’s generally work out of the box as the image was prepared.

I have already mentioned that upgrading either or both of them still does not get oo to work.

[Mornsgrans]

If I google for the error message in the 3rd schreenshot, I get a hit to this thread in the Univention forum:

NextCloud / onlyoffice-doc server broken

Please note: The mentioned thread concerne to UCS 4.4, but your version seens to be 5.2 or higher.

So it might be better to ask in the univention forum for help.

[JustDave]

I pass the healthcheck too, so I have no idea what else can be wrong.

I am sure it’s a config or json I have to edit.

I poked into the docker container of oo and I saw a private ip in the dbHost, which I never typed in. Should I change this to my internal local ip? or fdqn external ip?

[Mornsgrans]

The docker IP should be known by UCS to forward the request to open the document. My Collabora instance had an 172.x.x.x IP on my UCS and it worked. But I turned off my UCS last week and replaced it by the Hansson-IT Nextcloud instance.

Did you check the Univention-logs in /var/log/univention as well as /var/log/ and /var/log/nginx/* resp /var/log/apache2/ ?

Sorry, but I cannot help more, than until now.

[JustDave]

When I changed that 172.17.42.1 to localhost, the healthcheck no longer worked by responding with a 502 bad gateway. I have a feeling this is some internal ip defined by oo during it’s setup, generated or otherwise.

I have seen that dbHost is localhost from other local.json shared by other users.

[Mornsgrans]

You should not change the IP address.