Installation script fails on Ubuntu 24.04 during Nextcloud download

[Dieguim25]

Steps To Reproduce

1 Provision a new Ubuntu 24.04.3 LTS server.

2 Log in and switch to the root user:

sudo su

4 Download the installation script:

wget https://raw.githubusercontent.com/nextcloud/vm/refs/heads/main/nextcloud_install_production.sh

5 Make the script executable:

chmod +x nextcloud_install_production.sh

6 Run the script:

./nextcloud_install_production.sh

7 Follow the initial prompts. The script fails when it tries to download the Nextcloud zip file.

Expected Result

The script should successfully download the Nextcloud archive and complete the installation process.

Actual Result

The script fails with the following error message:

curl didn't produce a 200 status, is github.com reachable? Please report this to https://github.com/nextcloud/vm/issues.

Notably, this exact same installation process was working perfectly about 15 days ago on a similar setup, which suggests a recent regression might have been introduced.

Screenshots, Videos, or Pastebins

log SSH.txt

https://paste.sh/cWRES1MC#dc7SDGlGHCX9LxnSC4J7k2XT

Additional Context

Please note that the attached log file does not contain the final curl error, as the logging appears to have stopped just before the failure occurred. However, it contains the full process up to that point.

Build Version

31.0.8

Environment

By using the scripts

Environment Details

• Operating System: Ubuntu 24.04.3 LTS
• Kernel: 6.8.0-79-generic x86_64
• CPU Cores: 2
• RAM: 5.8 GB
• Virtualization/Cloud Provider: VirtualBox

[ffc91]

I'm in Uruguay, and I'm having the same issue I tracked it down to this part in the scripts.

At some point the scripts checks for connection using this: curl -vLI github.com -w '%{http_code}\n'

I manually ran it and this is the result:

• Host github.com:80 was resolved.
• IPv6: (none)
• IPv4: 4.228.31.150
• Trying 4.228.31.150:80...

It gets stuck there waiting for a response

I don't know why, but when the scripts checks for connectivity, it does so, using port 80 to the github domain, and it seems that, that endpoint is no longer available.

[Dieguim25]

Not even updating one that I had installed when it worked will work anymore. 😥

[muchachagrande]

If I do curl -vLI https://github.com -w '%{http_code}\n' I get a response. The problem is that curl is trying to connect to http by default and github.com only will answer with https.

[muchachagrande]

Here is a workaround:

To make curl default to https you have to create ~/.curlrc and add --proto-default https.

[ffc91]

I tried @muchachagrande’s suggestion, but when running sudo bash /var/scripts/menu.sh it doesn’t use the ~/.curlrc configuration.

What I ended up doing instead was creating a small wrapper script that forces curl to always use HTTPS by default:

sudo tee /usr/local/bin/curl >/dev/null <<'EOF'
#!/usr/bin/env bash
exec /usr/bin/curl --proto-default https "$@"
EOF

sudo chmod 0755 /usr/local/bin/curl

This works because anything placed in /usr/local/bin takes precedence in the $PATH, so my wrapper is called before the system’s /usr/bin/curl.

The chmod 0755 part :

• 7 gives read, write, and execute permissions to the owner (root).
• The two 5s give read and execute permissions to the group and others.

That makes the wrapper executable for everyone, just like the original curl binary, so scripts such as menu.sh will transparently call it without issues.

With this in place, the connectivity check in the installer succeeds because it no longer tries plain HTTP on port 80, but goes directly over HTTPS.

I tested it in my own installation and it solved the issue. However I'm not responsible for the useof this fix in any other system, other than mine.

[muchachagrande]

@ffc91, I've created .curlrc at root home (/root) because I run update_nextcloud from root account. If one creates curlrc in another home as /home/ncadmin and then updates from root account, curl wont use it.
If you've created .curlrc in the non root users home and the updated with sudo, the home will change to /root.

[Dieguim25]

With the command suggested by @ffc91 it really works. Thank you very much 🤩

[RobertRoberts2020]

Same problem, unable to install nextcloud.

[RobertRoberts2020]

Why was this closed, the problem is still ongoing I'm experiencing it right now.

[muchachagrande]

There is a workaround on this thread but the issue was not solved yet.

[Dieguim25]

Try what friend ffc91 suggested above, it worked well for me:
sudo tee /usr/local/bin/curl >/dev/null <<'EOF' #!/usr/bin/env bash exec /usr/bin/curl --proto-default https "$@" EOF
sudo chmod 0755 /usr/local/bin/curl

[RobertRoberts2020]

I mean, yeah, but just because someone managed to find a fix that works on their end by changing something doesnt mean the problem is really " fixed" that's the reason the script exists :(

…

On Fri, Oct 3, 2025 at 4:25 PM Diego Zeppe ***@***.***> wrote: *Dieguim25* left a comment (nextcloud/vm#2763) <#2763 (comment)> Try what friend ffc91 suggested above, it worked well for me: sudo tee /usr/local/bin/curl >/dev/null <<'EOF' #!/usr/bin/env bash exec /usr/bin/curl --proto-default https "$@" EOF sudo chmod 0755 /usr/local/bin/curl — Reply to this email directly, view it on GitHub <#2763 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJJHCCQ5NRGYEVHDTQSFCUL3V3ERLAVCNFSM6AAAAACFURUV4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNRWHE2DENJZHA> . You are receiving this because you commented.Message ID: ***@***.***>

[RobertRoberts2020]

Also the commands didnt really work for me, maybe something needs to be changed but I dont know, I'm not using to diagnosing these problems because the script has to work without doing any other work.

…

On Fri, Oct 3, 2025 at 4:25 PM Diego Zeppe ***@***.***> wrote: *Dieguim25* left a comment (nextcloud/vm#2763) <#2763 (comment)> Try what friend ffc91 suggested above, it worked well for me: sudo tee /usr/local/bin/curl >/dev/null <<'EOF' #!/usr/bin/env bash exec /usr/bin/curl --proto-default https "$@" EOF sudo chmod 0755 /usr/local/bin/curl — Reply to this email directly, view it on GitHub <#2763 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJJHCCQ5NRGYEVHDTQSFCUL3V3ERLAVCNFSM6AAAAACFURUV4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNRWHE2DENJZHA> . You are receiving this because you commented.Message ID: ***@***.***>