AIO not updating: start.sh script not connecting to ghrc.io

[details=“AIO fail to update: start.sh script fails when it try to connect ghrc.io”]

AIO fail to update: start.sh script fails when it try to connect ghrc.io

#Environment
Next Cloud AIO version v10.11.0
Host Ubuntu 24.04

#Problem
After master container update it fails to access to ghcr.io with this error message:

"Could not reach https://ghcr.io."
"Most likely is something blocking access to it."

Inside the container startup.sh script fails with this curl message error:
curl: (35) TLS connect error: error:00000000:lib(0)::reason(0)
If I try to use curl inside the container with another site, google.com, for example, it works fine. The problem seems to be with ghcr.io.

I was able to test the container by commenting out these lines in the startup.sh script.

if ! curl https://ghcr.io &>/dev/null; then
    print_red "Could not reach https://ghcr.io."
    echo "Most likely is something blocking access to it."
    echo "You should be able to fix this by using https://github.com/nextcloud/all-in-one/tree/main/manual-install"
    exit 1
fi

Test curl inside container

44c5d87003fb:/tmp# curl https://ghcr.io
curl: (35) TLS connect error: error:00000000:lib(0)::reason(0)

Something wrong with curl o its libraries?

1 Like

I had the same error. Got fixed after I disabled Wireguard VPN on the PC.

I initially set up the AIO without a VPN. After I restarted the PC, my VPN automatically turned on, and so AIO docker failed to start due to these errors. It started working again after switching off the VPN and restarting container.

1 Like