# Collarora (CODE) and cURL errors

**URL:** <https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136>\
**Category:** 📄 Office\
**Tags:** nc28, collabora-online\
**Created:** [January 16, 2024, 11:14am UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136 "2024-01-16T11:14:19Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![dnilgreb](https://help.nextcloud.com/letter_avatar/dnilgreb/32/5_5575768a8748004e209b776fc1b2916d.png) [@dnilgreb](https://help.nextcloud.com/u/dnilgreb)\
**Post date:** [January 16, 2024, 11:14am UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/1 "2024-01-16T11:14:19Z")

</div>

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:

```auto
[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:

```auto
{"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?

---

<div class="post-metadata">

**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/5_5575768a8748004e209b776fc1b2916d.png) [@jtr](https://help.nextcloud.com/u/jtr)\
**Post date:** [January 16, 2024, 6:13pm UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/2 "2024-01-16T18:13:49Z")

</div>

> [@dnilgreb](#):
>
> `Could not resolve host`

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.

---

<div class="post-metadata">

**Author:** ![dnilgreb](https://help.nextcloud.com/letter_avatar/dnilgreb/32/5_5575768a8748004e209b776fc1b2916d.png) [@dnilgreb](https://help.nextcloud.com/u/dnilgreb)\
**Post date:** [January 17, 2024, 2:43pm UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/3 "2024-01-17T14:43:53Z")

</div>

> [@jtr](#):
>
> Can you resolve the hostname from the Nextcloud Server itself?

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?

---

<div class="post-metadata">

**Author:** ![cj2021](https://help.nextcloud.com/user_avatar/help.nextcloud.com/cj2021/32/31484_2.png) [@cj2021](https://help.nextcloud.com/u/cj2021)\
**Post date:** [March 26, 2024, 5:44pm UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/4 "2024-03-26T17:44:42Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![dnilgreb](https://help.nextcloud.com/letter_avatar/dnilgreb/32/5_5575768a8748004e209b776fc1b2916d.png) [@dnilgreb](https://help.nextcloud.com/u/dnilgreb)\
**Post date:** [September 2, 2024, 10:48am UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/5 "2024-09-02T10:48:53Z")

</div>

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.

```auto
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?

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [September 2, 2024, 7:28pm UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/6 "2024-09-02T19:28:24Z")

</div>

please consult [Collabora integration guide](https://help.nextcloud.com/t/collabora-integration-guide/151879)

---

<div class="post-metadata">

**Author:** ![dnilgreb](https://help.nextcloud.com/letter_avatar/dnilgreb/32/5_5575768a8748004e209b776fc1b2916d.png) [@dnilgreb](https://help.nextcloud.com/u/dnilgreb)\
**Post date:** [September 5, 2024, 8:44am UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/7 "2024-09-05T08:44:02Z")

</div>

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

> [@](#):
>
> from Collabora, verify access to the Nextcloud UI (from console run `curl https://cloud.mydomain/status.php`)

When I ran this I actually got the same error:

> [@](#):
>
> curl: (6) Could not resolve host: cloud.mydomain

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?

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [September 5, 2024, 11:09am UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/8 "2024-09-05T11:09:40Z")

</div>

> [@dnilgreb](#):
>
> expected XML response

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.

---

<div class="post-metadata">

**Author:** ![dnilgreb](https://help.nextcloud.com/letter_avatar/dnilgreb/32/5_5575768a8748004e209b776fc1b2916d.png) [@dnilgreb](https://help.nextcloud.com/u/dnilgreb)\
**Post date:** [September 5, 2024, 11:31am UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/9 "2024-09-05T11:31:44Z")

</div>

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

```auto
{"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.

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [September 5, 2024, 3:28pm UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/10 "2024-09-05T15:28:40Z")

</div>

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`)

---

<div class="post-metadata">

**Author:** ![dnilgreb](https://help.nextcloud.com/letter_avatar/dnilgreb/32/5_5575768a8748004e209b776fc1b2916d.png) [@dnilgreb](https://help.nextcloud.com/u/dnilgreb)\
**Post date:** [September 8, 2024, 1:04pm UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/11 "2024-09-08T13:04:14Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![dnilgreb](https://help.nextcloud.com/letter_avatar/dnilgreb/32/5_5575768a8748004e209b776fc1b2916d.png) [@dnilgreb](https://help.nextcloud.com/u/dnilgreb)\
**Post date:** [September 8, 2024, 6:30pm UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/12 "2024-09-08T18:30:16Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![dnilgreb](https://help.nextcloud.com/letter_avatar/dnilgreb/32/5_5575768a8748004e209b776fc1b2916d.png) [@dnilgreb](https://help.nextcloud.com/u/dnilgreb)\
**Post date:** [September 9, 2024, 1:52pm UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/13 "2024-09-09T13:52:41Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [January 16, 2025, 8:55am UTC](https://help.nextcloud.com/t/collarora-code-and-curl-errors/179136/14 "2025-01-16T08:55:42Z")

</div>


