One hour later... still not finding answer

I installed Nextcloud AIO Latest on my Ubuntu 22.04 VPS Server following instructions here GitHub - nextcloud/all-in-one: Nextcloud AIO stands for Nextcloud All In One and provides easy deployment and maintenance with most features included in this one Nextcloud instance. I’m unable to edit documents and upon further inspection noticed the appstore isn’t connecting. I spent over an hour on this forum and google looking for a solution. With many references to search this forum with this term ‘’ instead of actionable solutions in most cases (my own ignorant observation).

I also installed Nextcloud latest on the same server base following this tutorial and had the same problem of not being able to connect to the Appstore. Bearing in mind there are all kinds of idiots in the world, of which I fall into that category occasionally as most humans do, would someone be so kind as to point me to some actionable solutions to the curl timeout error on Nextcloud AIO Latest?

I create training tutorials to help folks with tech (marketing tools sites, funnels, memberships, email marketing) and would be willing to help out wherever my skillset could be of benefit to this community.

I can’t really help you as I never experienced such issues in my installation.

The only similar experience I had was Collabora connection somewhat broken due to DNS issue between containers running on same Docker host.

Keep in mind containers expect direct internet connection - everything in your network which differs from this could be a reason - proxy server, special firewall rules etc…

I would start troubleshooting by running curl inside of the container (docker exec <container_name> curl and reviewing the output carefully - often you can detect a reason (wrong DNS, missing CA certificates, IPv6 etc…). try running curl with URL shown in the error message. If you don’t get useful error add -v for verbose output… check out other curl options to nail the issue further…

My example below shows successful connect with running on using TLs1.3

This is then likely caused by the docker daemon not being able to connect to an upstream dns-server or something wrongly configured in your home network.

1 Like