Collabora: Unexpected server error

Support apps
, ,
1

What app is this about, and its version: Nextcloud 25.04.9.1~ynh2
What YunoHost version are you running: 12.1.39
What type of hardware are you using: VPS bought online

Describe your issue

Suddenly I cannot open documents from my nextcloud instance anymore. This started with the last few weeks (I am not sure). I used to wotk without any issues.

My setup is like this: I have a your-storageshare NextCloud instanse at Hetzner and a separate VPS with YunoHost in which I have installed a Collabora server. Until recently, the NextCloud instanse connected to the Collabora server without issues. Now it does not. After the problem occurred, I have tried to solve it by trying to add the domain of the nextcloud instance to wopi allow request. I am not sure I did this correct, but there is no visible difference in usage.
I am accessing the NextCloud instance through three different subdomains (nx.mydomain.dk x 3) plus hetzners own (nx00000.your-storageshare.de).

Share relevant logs or error messages

I cannot get a log but I have an image of the error message. How can I upload it?

2

Check nextcloud logs in the admin area

3

Did you try in the wopi allow request add the IP of your server Collabora ?

4

How did you do that?

5

I don’t see where I can find that?

6

Administration > Logs at the bottom left.

7

I have not, and now that I want to try, I get this error messags:

Could not establish connection to the Collabora Online server.

Failed to connect to the remote server: Server error: `GET https://cb.gnubahn.dk/hosting/discovery` resulted in a `502 Bad Gateway` response: 502 Bad Gateway body { width: 35em; margin: 0 a (truncated…)

And where you can usually enter the allow list, it now says:

Firefox can’t open this page

8

Your collabora server seems to be down. Check its service in yunohost webadmin > tools > services > coolwsd.

9

Via ssh I opened /etc/coolwsd/coolwsd.xmland entered this

<net>
  <wopi>
    <host allow="cloud.domain.tld"/>
  </wopi>
</net>

I also ran

coolconfig set net.wopi.host "cloud.domain.tld"
10

I fail to see it. Can it be somewhere else?

11

Your are right: hastebin

12

I started it up again and now ot seems to be running. But it still does not open a document.

13

Now I have, but it didn’t change behaviour.

14

Ok, try this :

  • clear the “allow list for WOPI request” in nextcloud
  • remove these lines in /etc/coolwsd/coolwsd.xml:

and change this whole block

            <host desc="Regex pattern of hostname to allow or deny." allow="true">__NEXTCLOUD_DOMAIN__</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="true">10\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="true">172\.1[6789]\.[0-9]{1,3}\.[0-9]{1,3}</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="true">172\.2[0-9]\.[0-9]{1,3}\.[0-9]{1,3}</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="true">172\.3[01]\.[0-9]{1,3}\.[0-9]{1,3}</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="true">192\.168\.[0-9]{1,3}\.[0-9]{1,3}</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="false">192\.168\.1\.1</host>

to this

            <alias_groups mode="groups">
                <group>
                        <host id="0" desc="Regex pattern of hostname to allow or deny." allow="true">cloud.domain.tld</host>
                </group>

                <group> # <-- only if needed
                        <host id="1" desc="Regex pattern of hostname to allow or deny." allow="true">other.cloud.domain.tld</host> 
                </group>

               
                <group>
                    <host desc="Regex pattern of hostname to allow or deny." allow="true">10\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}</host>
                    <host desc="Regex pattern of hostname to allow or deny." allow="true">172\.1[6789]\.[0-9]{1,3}\.[0-9]{1,3}</host>
                    <host desc="Regex pattern of hostname to allow or deny." allow="true">172\.2[0-9]\.[0-9]{1,3}\.[0-9]{1,3}</host>
                    <host desc="Regex pattern of hostname to allow or deny." allow="true">172\.3[01]\.[0-9]{1,3}\.[0-9]{1,3}</host>
                    <host desc="Regex pattern of hostname to allow or deny." allow="true">192\.168\.[0-9]{1,3}\.[0-9]{1,3}</host>
                    <host desc="Regex pattern of hostname to allow or deny." allow="false">192\.168\.1\.1</host>
                </group>
        </alias_groups>

Then run sudo systemctl restart coolwsd

15

I am quite confused about the wopi thing.

I am asked in nextcloud to write the allow list for wopi requests. But is this not a collabora server thing? And should I not enter this data in the collabora server config file?

Also, Besides the URL that Hetzner gives me, I use three different subdomains (sub.domain.tld) to acces my nextcloud instanse. Should I enter all of these in the server settings or should I just enter the original Hetzner URL?

16

The nextcloud server(s) is/are the WOPI hosts.

17

I believe I have done all that, but I still get a “Document loading failed“, when I try to open a document…

18

Can you share the logs from nextcloud and from coolwsd service ?

19

In the allow list for wopi requests, should I enter the url (e.g. nx12345.your-storageshare.de) og the ip address (IPv4 or IPv6) of my collabora server?

20

Here is the log from the running Coolwsd service: hastebin

After being started, it stops soon. Here is the log for that: hastebin

I still can’t figure out where to find the logs in Nextcloud