Connection timeout with Collabora Office

ℹ️ Support
, , , , , ,
1

Error:

Failed to connect to the remote server: cURL error 28: Connection timed out after 5002 milliseconds (see libcurl - Error Codes) for https://nc.example.com/custom_apps/richdocumentscode/proxy.php?req=/hosting/discovery.

When downloading odt, docx, excel… files. infinite download. I realized that I need to install collabora office from the app store (My docker collabora container is running).
I think the built-in CODE for small tasks will be enough for me.
At first I was getting timeout errors due to collabora, but they were fixed by increasing the timeout in the nextcloud container configuration. But now I am getting the same error above
I am behind NAT (Any access from local network to my external ip will fail). Normal connection speed is ~20 Mbps

/etc/hosts:

127.0.0.1 localhost
127.0.1.1 servername

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
# Added by Docker Desktop
# To allow the same kube context to work on the host and the container:
127.0.0.1	kubernetes.docker.internal
# End of section

$ curl -vvvv https://$NC_DOMAIN:443/hosting/discovery (from nextcloud container)

* Host nc.example.com:443 was resolved.
* IPv6: (none)
* IPv4: 91.xxx.xxx.37
*   Trying 91.xxx.xxx37:443...
* connect to 91.xxx.xxx.37 port 443 from 172.20.0.8 port 53080 failed: Operation timed out
* Failed to connect to nc.example.com port 443 after 136063 ms: Could not connect to server
* closing connection #0
curl: (28) Failed to connect to nc.example.com port 443 after 136063 ms: Could not connect to server

$ curl -vvvv https://$NC_DOMAIN:443/standalone-signaling/api/v1/welcome (from nextcloud container)

* Host nc.example.com:443 was resolved.
* IPv6: (none)
* IPv4: 91.xxx.xxx.37
*   Trying 91.xxx.xxx.37:443...
* connect to 91.xxx.xxx.37 port 443 from 172.20.0.8 port 58006 failed: Operation timed out
* Failed to connect to nc.example.com port 443 after 136231 ms: Could not connect to server
* closing connection #0
curl: (28) Failed to connect to nc.example.com port 443 after 136231 ms: Could not connect to server

Снимок экрана от 2024-09-16 08-10-06
Снимок экрана от 2024-09-16 08-10-061130×255 26.6 KB

I’m inexperienced in networking, so please point out what’s wrong, I’d be very grateful!
Ubuntu server 24.04 LTS, Nextcloud AIO 29.0.6.

2

Looks like this is your issue. Most likely your router or networking infrastructure does not allow the container to connect to its domain via the external ip-address.

You can fix this by following GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

1 Like
3

That helped, I configured dnsmasq.
But now I got a new errors

Could not find urlsrc for application/vnd.openxmlformats-officedocument.wordprocessingml.document in WOPI discovery response
and
Didn't find urlsrc for mimetype application/vnd.openxmlformats-officedocument.wordprocessingml.document in this WOPI discovery response: <html><body> <h1>Socket proxy error</h1> <p>Error: no_glibc</p> </body></html

installed everything according to the instructions
I checked Callabora Office when installing, the container started successfully on port 9980.
Some say to downgrade the richdocuments version, others say to wait…
Apparently there is something with “no_glibc”, I’m not familiar with php, I don’t understand what this could mean

6

no_glibc and the URL ../custom_apps/richdocumentscode/proxy.php?req=/hosting/discovery makes me think you mix up installation methods. similar to Built-in CODE error: Didn't find urlsrc for mimetype application AiO doesn’t use built-in CODE (and the respective app in not required) it runs separate CODE container and the CODE URL configured in Nextcloud Office settings should be https://cloud.mydomain.tld/hosting/discovery which in turn must be accessible from the cloud and client as described in Collabora integration guide…

1 Like
7

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.