Failed to get release information

[girish]

@ghaisasadvait Is this Ubuntu 16/18/20 ?

[ghaisasadvait]

@girish said in Failed to get release information:

curl https://my.cloudron.io

all curl commands related to cloudron.io give certificate error like above

[ghaisasadvait]

@girish its ubuntu server 18.

[girish]

@ghaisasadvait How did you manage to download the cloudron-setup script in the first place? Maybe you can try sudo update-ca-certificates to see if that helps. Also, can you confirm that you can access cloudron.io and api.cloudron.io from other devices of your house? (so we can localize this to a VM issue).

[ghaisasadvait]

@girish said in Failed to get release information:

sudo update-ca-certificates

sudo update-ca-certificates

This worked!..pretty odd since i updated and upgraded all the packages beforehand

[luckym]

I am getting the same error message on a fresh Hetzner VPS Ubuntu 22.04.3 install.

=> Updating apt and installing script dependencies
=> Validating setup token
=> Checking version
Failed to get release information

When I look at the logs I get the following output:

root@ubuntu-2gb-nbg1-1:~# cat /var/log/cloudron-setup.log
Running cloudron-setup with args : --
Hit:1 https://mirror.hetzner.com/ubuntu/packages jammy InRelease
Hit:2 https://mirror.hetzner.com/ubuntu/packages jammy-updates InRelease
Hit:3 https://mirror.hetzner.com/ubuntu/packages jammy-backports InRelease
Hit:4 https://mirror.hetzner.com/ubuntu/security jammy-security InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
curl is already the newest version (7.81.0-1ubuntu1.15).
python3 is already the newest version (3.10.6-1~22.04).
software-properties-common is already the newest version (0.99.22.9).
ubuntu-standard is already the newest version (1.481.1).
0 upgraded, 0 newly installed, 0 to remove and 36 not upgraded.

Anybody has any ideas what the problem might be? Not sure if it makes a difference but the server only has an IPv6 address.

[girish]

@luckym can you check curl https://api.cloudron.io/api/v1/releases on the server ? If that doesn't work, does host api.cloudron.io work ?

Can you also tell us a bit about your server/network setup?

[luckym]

@girish

The setup is basically this, the cheapest Hetzner VPS with a fresh Ubuntu 22.04.3 install. Didn't do anything special, just ssh'd in and ran the three install commands from Cloudrons homepage.

I tried running both of the commands, the first one fails, the second one works:

root@ubuntu-2gb-nbg1-1:~# curl https://api.cloudron.io/api/v1/releases
curl: (7) Couldn't connect to server
root@ubuntu-2gb-nbg1-1:~# host api.cloudron.io
api.cloudron.io has address 165.227.67.76

[girish]

@luckym thanks. the DNS resolution is correct. It seems it is not able to make outbound request for some reason. I just checked from multiple servers and api.cloudron.io seems fine. Are you able to curl other sites? Say curl https://www.cloudron.io ?

Another idea: start afresh with ubuntu 22.04. then, run the curl command first. then, run cloudron-setup script. This will give us a better idea if it is some installation issue or some VM issue.

[luckym]

Thanks girish. I tried to curl other sites and that worked fine as well. Also from my local computer curling api.cloudron.io works fine. I then deleted the server and set up a fresh server and tried the curl command first as you suggested. Same issue.

After that I deleted the server again and set up a new server that also has a IPv4 address instead of IPv6 only. This time the curl command to api.cloudron.io worked and the setup script is currently running just fine ¯_(ツ)_/¯ .

[jdaviescoates]

@luckym said in Failed to get release information:

IPv6 only

sounds like that was the issue then

[girish]

Ah right. Cloudron currently does not support IPv6 only servers. It needs an IPv4. But this is great to know that Hetzner has IPv6 only servers. I will see how far away we are from supporting this.

[eddowding]

Ah .. ssdnodes can also be ip6 only. ip4 adds a fair chunk of money these days.