Nextcloud - Collabora Unauthorized WOPI host

Support
1

NethServer Version: 8
Module: NextCloud and Collabora

Hello,

I have installed a fresh nethserver 8 with NextCloud and Collabora from the App repo,

I’ve then configured the SSL certificate using a domain and letsencrypt, but as soon I try to edit a .doc file from NextCloud i got this error:

Unauthorized WOPI host. Try again later, and if the problem persists, report it to the administrator.

It’s possible that is some bug introduced with some new version of Collabora or Nextcloud trough nethserver?

I’m pretty sure it was working this way some months ago,

How I can check if the configuration for the WOPI whitelist on collabora is correct?

Thank you!

2

Maybe helps?

1 Like
3

I can’t reproduce. It’s working here.

Did you set the Collabora server in the NS8 Nextcloud app settings as explained in the documentation?

Did you configure a Letsencrypt cert for both, Nextcloud and Collabora?

I don’t think that the config file is wrong. To show it, you could use the following command:

runagent -m collabora1 podman exec collabora cat /etc/coolwsd/coolwsd.xml
4

Hello @mrmarkuz ,

Yes I have configured both Letsencrypt for Nextcloud and Collabora, and the https is fine for both URL, I have already configured Nextcloud to use the internal Collabora using Nethserver

image
image948×527 13.4 KB

image
image1041×633 16.7 KB
But i’m still seeing the Unauthorized WOPI error, @LayLow not sure if it’s related to the posts that you have shared (my test comes from a fresh nethserver 8 setup)

5

Does it make a difference when you enable “HTTP to HTTPS” in the Collabora app settings and “Verify TLS certificate” in the Nextcloud app settings?

Check if Nextcloud can be reached from Collabora: (adapt the URL to the used FQDN)

runagent -m collabora1 podman exec -ti collabora curl https://nextcloud.domain.tld/apps/dashboard/

It should return {"message":"Current user is not logged in"}

Check if Collabora can be reached from Nextcloud:

runagent -m nextcloud1 podman exec -ti nextcloud-app curl https://collabora.domain.tld

It should return OK

6

Hi @mrmarkuz ,

I’ve enabled the http→https redirection but still no success to edit docs trough nextcloud,

Trying to curl eachother app

[root@cloud ~]# runagent -m collabora2 podman exec -ti collabora curl https://cloud.<redacted>.it/apps/dashboard/
curl: (7) Failed to connect to https://cloud.<redacted>.it port 443 after 1 ms: Could not connect to server

[root@cloud ~]# runagent -m nextcloud1 podman exec -ti nextcloud-app curl https://collabora.<redacted>.it
OK

It seems that collabora can’t reach Nextcloud, but nextcloud can curl collabora and it returns “OK”

Just to clarify, since this is a fresh setup i’ve already tried to unistall and reinstall collabora, that’s why my collabora id is “collabora2”

and If I try to reach the URL https://cloud..it/apps/dashboard/ from my PC it’s working

7

It seems your node FQDN is the same as the Nextcloud FQDN. In that case inside the Collabora container cloud.domain.it is resolved to 127.0.1.1 and therefore Nextcloud can’t be reached.

I recommend to change the node FQDN to something like node.domain.it. Changing the node FQDN is explained in the documentation.
After restarting Collabora, it should be able to reach Nextcloud.

3 Likes
8

That was the issue!

Thank you, as soon i’ve changed the FQDN of the node to something else, it started to work as usual

2 Likes