Collabora cURL error 28 - built in Collabora CODE not working

[nightcobe]

Continuing the discussion from Cannot get Collabora Code Built-in to work:

I have the exact same problem:

@Renaud_B

“Failed to connect to the remote server: cURL error 28: Operation timed out after 45001 milliseconds with 0 bytes received (see libcurl - Error Codes) for https://<MY_SERVER>/apps/richdocumentscode/proxy.php?req=/hosting/discovery”

and the suggested solution is:

@wwe

you must ensure the system can access the built-in CODE instance using ‘https://<MY_SERVER>/apps/richdocumentscode/proxy.php?req=/hosting/discovery’ often this is not the case. you can check using curl from SSH… Depending on your setup hosts entry could be sufficient… if troubleshoot by checking DNS and review which IP it wants to connect and if there is an issue with routing/firewalls etc…

What should I be looking for in the curl response? How do I check which IP it wants to connect to? Could my problem be port forwarding? My server is on a local computer.

There is no error in the curl output for the domain specified above.

Thankfull for any help!

/Martin Book

[wwe]

curl -v provides extended output. check collabora integration guide for more details

[nightcobe]

Thank you! But I have great difficulties understanding that guide because it leaves a lot out and I do not understand how to do many of the things there.

Mainly, I do not understand “client” and “console” in the troubleshooting part. I do get a file, but seems to be HTML instead of an XML file. I do not really know what to look for when it comes to “public hostname” or “right… URL scheme”. This is here:

@wwe

• • the result must be an XML document describing the capabilities of the WOPI client
    (long list of different file types which could be opened)
• review the content of the XML document reflect the right public hostname
• verify the content of the document reflect the right - https:// - URL scheme
• from Nextcloud, verify access to Collabora (from console run curl https://office.mydomain/hosting/discovery)
• from Collabora, verify access to the Nextcloud UI (from console run curl https://cloud.mydomain/status.php)

Then it goes on to tell me to install the richdocuments app. I thought that was done in installation when I checked the box to include Nextcloud office.

The tip about curl -v was really helpful. It seems port 443 is used and since it is already open I think I do not have a port forwarding problem.

I am learning but I am not as well versed in all the lingo and what it means as the rest of you.

Thanks for any help!

[nightcobe]

I found the part about the built in Nextcloud Office, CODE, and get the following output:

From the first url described in the collabora integration guide under “Nextcloud Office aka…” I got:

    "convert-to":{"available":true},
    "hasMobileSupport":true,
    "hasProxyPrefix":false,
    "hasTemplateSaveAs":false,
    "hasTemplateSource":true

From the second one I got the long list of file types that are mentioned above.

To me it seems all is correct regarding those two URLs

@wwe

• https://mydomain.tld/apps/richdocumentscode/proxy.php?req=/hosting/capabilities
• https://mydomain-tld/apps/richdocumentscode/proxy.php?req=/hosting/discovery

I do not understand how to do the things that are said that one should do with Apache.

How do I do this:

@wwe

Running collabora-built-in behind a reverseproxy highly depends on reverse proxy X_FORWARDED* http headers - make sure your proxy adds them!

And where do I put this?

Apache reverse proxy config for build-in CODE

• Collabora - Built in Code - Reverse Proxy / “ssl.enable” and “ssl.termination” - #5 by DerP4si

I am not on Docker but rather on a normal installation of Nextcloud.

I had no problems with Collabora/Nextcloud Office last time I installed nextcloud in a similar way. Now it is acting up and I do not understand why.

Thanks for any help!

Cordially,
Martin Book

[saettel.beifuss0]

Hey @nightcobe just a small heads up, before you drive yourself nuts, like I did

I used Collabora since at least Nextcloud 28 without any issues.
Since version 30.0.3, I have the same strange issues.
See my other forum post

I also tried to check with the great writeup of @wwe to hunt down the issue.
But no luck.

I also use CODE and these two links

@wwe

• https://mydomain.tld/apps/richdocumentscode/proxy.php?req=/hosting/capabilities
• https://mydomain-tld/apps/richdocumentscode/proxy.php?req=/hosting/discovery

worked perfectly fine, but I still get the curl connection timeouts.

I did not have the knowledge or the time to further troubleshoot this, but just so you are aware that this might be a bug and not a config error on your side.

[nightcobe]

Hi, @saettel.beifuss0 !

Thanks for the heads up! I sometimes get a pass on the server and I see this:

Next time I click “Use the built-in CODE…” it generally gives me the red error below:

Did you try to update the Apache reverse proxy config?

I see now that there is a possibility to update to 30.0.4, I am now on 30.0.2 having this issue.

Thanks!

Cordially,
Martin Book

[saettel.beifuss0]

I always get a pass on that page.

I get the curl error 28 in the logs (and it also crashed the apache fpm completely).

I am using NGINX as reverse proxy. The problem also exists on 30.0.4 for me.

[nightcobe]

Ok. Wondering if my error 28 could be something else, then?

Have you tried the suggestions in the Collabora integration guide for built-in Collabora with NginX?

More worried about my local disk not being read by Nextcloud at the moment. Will wait and see if anyone (@wwe ?) knows if this Collabora thing is a bug or if I should do something else.

[tj200]

Hi, I had a similar probleme with version 30.0.2. In my case, i’ve had a wrong firewall config. I didn’t allow the nextcloud server so open connection to other to my dns server. I over see (to late at the evening) the log entries in my firewall. after add a the new rule, it works.

[nightcobe]

This sounds great! What was the new rule you set?

[tj200]

All “server” are in the same network segement (vlan)

Default: No server is allow to communicate elsewhere. Everything will be droped

I use unifi network equipment. thats very simple to setup rules

Here my rule
allow nextcloud_server_ip (xx.xx.x1.3) to dns_server_ip(xx.xx.x1.1), revers_proxy_server_ip (xx.xx.x1.2), collabora_server_ip(xx.xx.x1.4)/nextcloud_server_ip (xx.xx.x1.3) connect

Hint: the ip address above are only for easy reading

[nightcobe]

Thank you for your feedback, @tj200 ! However, I do not understand where you enter these rules. I think you are doing it on the router, but I do not get under what setting you are able to add those rules. Under what heading do you find these rules?

[nightcobe]

Does this at all help? I updated and in the logs I got this:

Error - Index:
Call to a member function xpath() on false in file ‘/var/www/nextcloud-folder/apps/richdocuments/lib/WOPI/Parser.php’ Line 41.

The line is this, I think:

$result = $discoveryParsed->xpath(sprintf(‘/wopi-discovery/net-zone/app[@name='%s']/action’, $mimetype));

Is something the matter, there?

Thanks!

Cordially,
Martin Book

[saettel.beifuss0]

@nightcobe

Have you tried the suggestions in the Collabora integration guide for built-in Collabora with NginX?

Jup. Remember, it used to work for over a year.

@tj200

Default: No server is allow to communicate elsewhere. Everything will be droped

I use unifi network equipment. thats very simple to setup rules

Not trying to be a dork, but this makes no sense.
If your server are in the same VLAN and subnet, traffic will not even touch your firewall.

1.1 and 1.3 will directly communicate with each other. Even if you wanted to block that with the firewall you could not, since it never touches your firewall. You would have to block that on the switch level.

Maybe Unifi controller firewall rules do some strange shenanigans (I love my Unifi APs, but the Firewall and Switch port management is ridiculous) but in a normal setup you could not block that traffic.

@nightcobe

I do not understand where you enter these rules.

You don’t. See above

[nightcobe]

Any thoughts about my index error?

[nightcobe]

UPDATE:

Everything regarding Nextcloud Office (CODE) seems to have solved itself. I access documents, spreadsheets, etc. everytime I try now.

However, if there are any new ideas about what could have been the problem I think it would be great to address it, maybe come with suggestions here.

Thanks you, all who tried to help!

Cordially,
Martin Book

[nightcobe]

UPDATE2:

Unfortunately I was too quick in my hopes that all was good! It works quite a lot of the time but quite often just keeps spinning and does not open the documents.

A solution to this problem would be great!

/Martin Book

[saettel.beifuss0]

I haven’t found out what exactly is causing the errors, but it was always with xlsx files and when some kind of ODF / XML conversion was involved. Maybe that helps you find at least reproducing the error.

[nightcobe]

Thanks!

However, for me it is really always when I try the status of my Nextcloud CODE. On second attempt it generally gives me a green light.

But when I try to open documents or spreadsheets I can normally open them. Sometimes it loads and loads and then fails.

I start to feel like it is just a bug and has nothing to do with my setup.

[saettel.beifuss0]

@nightcobe

However, for me it is really always when I try the status of my Nextcloud CODE. On second attempt it generally gives me a green light.

Ahh you are talking about admin settings page. I had the same behavior there.