Collarora (CODE) and cURL errors

ℹ️ Support 📄 Office
,
1

I recently upgraded my Nextcloud instance to 28.0.1. Since, I don¨t get the green mark anymore in Admin → Overview, but instead warnings about log messages.

Specifically regarding Collabora. I get a few of these every day:

[richdocuments] Error: Failed to fetch the Collabora capabilities endpoint: cURL error 6: Could not resolve host: office.example.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://office.example.com/hosting/capabilities
	from ? by -- at 16 jan. 2024 07:35:08

However, https://office.example.com/hosting/capabilities seems to return an XML page:

{"convert-to":{"available":true,"endpoint":"/cool/convert-to"},"hasMobileSupport":true,"hasProxyPrefix":false,"hasTemplateSaveAs":false,"hasTemplateSource":true,"hasZoteroSupport":true,"productName":"Collabora Online Development Edition","productVersion":"23.05.6.4","productVersionHash":"aff0ccf","serverId":"4ff64844"}

And using Collabora for viewing / editing documents works fine. Does anyone know why these errors occur, and if anything can be done to get rid of them?

2

Can you resolve the hostname from the Nextcloud Server itself? Not knowing your installation method we can’t be more specific than that. If Docker, test from inside container not the underlying host.

1 Like
3

Yes. traceroute works fine, and curl too. I haven´t been able to fins anything that returns an error or doesn´t work.
Anything else I could check?

4

I have the same problem. everything works fine including DNS resolve and function is working as well. but keep getting those error from log

5

I have now moved my Nextcloud server to run in a docker container. My collabora runs as a separate docker container, I am not using the built-in CODE server.
I still get these error, and a lot of them.

curl https://office.example.com/hosting/capabilities

The above curl command returns correct data when I run it from:

Docker host
Nextcloud container
Collabora container

The Nextcloud and Collabora containers run on the same docker host.
Does anyone know how to investigate this further?

6

please consult Collabora integration guide

7

Ok, so I may have discovered something working through the checklist in the guide:

When I ran this I actually got the same error:

So I ran it again. Then I got the expected XML response. So I ran it 20 times more, and got the XML each time. Any idea what could cause that?

8

status.php is expected to return a JSON file like this

{"installed":true,"maintenance":false,"needsDbUpgrade":false,"version":"29.0.5.1","versionstring":"29.0.5","edition":"","productname":"Nextcloud","extendedSupport":false}

if you get similar output it should be OK… if you in fact get some XML output something is wrong… the only problem could be initial failure. This could result from slow DNS response - check if this repeats e.g. if you run the command an hour later - after this time cached DNS result should clear and your test is valid again.

9

Yes of course you are right. I´m sorry.
This is my response:

{"installed":true,"maintenance":false,"needsDbUpgrade":false,"version":"29.0.6.1","versionstring":"29.0.6","edition":"","productname":"Nextcloud","extendedSupport":false}

The same test now, a couple of hours later, was successful from first try.

10

so now once all your checks are susessful I would test again (maybe you need to restart NC after significant changes or run occ richdocuments:activate-config)

11

Restarted Nextcloud (and Collabora) and tested again today. The curl commands get the expected results. In both directions (NC → C & C → NC). But I still get these errors. Got new ones today. Anything else I could check? Anywhere else I should be looking?

12

I actually found some stale/incorrect records in my DNS. I deleted them, hoping that might resolve my issue. I´ll be back in a few days with results.

1 Like
13

I´m sorry to report that that didn´t hold. Got a new curl error today. Any idea how I can proceed in trying to find out what´s wrong?