GuzzleHttp Exception ConnectException: cURL error 28: Connection timed out

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
,
1

I am getting the following error in the logs constantly in the app richtextdocuments. It goes away if I select “Use Demo Server” but if I have “Use your own server” selected I get those errors and performance is reduced.

GuzzleHttp\Exception\ConnectException: cURL error 28: Connection timed out after 45002 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nextcloud.xxxxx.cloud/hosting/capabilities

I also see the following in the container log in the AIO interface.

wsd-00007-00012 2023-11-29 11:59:19.703238 -0600 [ remotefontconfig_poll ] WRN #27: Timed out while requesting [GET nextcloud.xxxx.cloud/apps/richdocuments/settings/fonts.json] after 30029ms| net/HttpRequest.hpp:1503
wsd-00007-00012 2023-11-29 11:59:19.703425 -0600 [ remotefontconfig_poll ] ERR Remote config server has response status code: 0 (Unknown)| wsd/COOLWSD.cpp:1306

I am using the Docker AIO install. – I can’t seem to figure out how to get this fixed.

2

Hi, can you follow https://github.com/nextcloud/all-in-one/discussions/1358?

3

Greetings szaimen

In my /etc/hosts file I have 127.0.0.1 localhost

I am unable to adjust the “Allow list for WOPI requests” because when I select “Use my Own Server” " it never connects to allow the advanced settings options.

I entered the container and tried the command curl -vvv https://$NC_DOMAIN:443/hosting/discovery. My results are below. I did redact the IP address and hostname.

me@app-nextcloud-aio:~$ sudo docker exec -it nextcloud-aio-nextcloud bash
de18cd480d6e:/var/www/html# curl -vvv https://$NC_DOMAIN:443/hosting/discovery

  • Trying 140.xxx.xxx.xxx:443…

  • connect to 140.xxx.xxx.xxx port 443 failed: Operation timed out

  • Failed to connect to nextcloud.xxx.cloud port 443 after 133752 ms: Couldn’t connect to server

  • Closing connection
    curl: (28) Failed to connect to nextcloud.xxx.cloud port 443 after 133752 ms: Couldn’t connect to server

Using the portchecker.co website, 443 is open and forwarded to my internal host.

5

I purchased a small vps from OVH and followed this tutorial on setting up another Collabora Server

Installing and Configuring Collabora CODE | Linode Docs

and I was able to get my Nextcloud AIO Docker setup to work with the separate ovh Collabora server and it works beautifully.

I am not very familiar with docker so I am not sure how to troubleshoot the Collabora docker instance. Is it possible to edit the Collabora docker instance?