@olivierlambert said in XOA Failing on Check-in:

So it's the case in an IPv6 context I assume, right?

I think it is only the time out setting as the primary cause of the problem with IPv6 as a secondary cause.
I am also in Australia, and just using IPv4 to Ping the address that I am seeing XOA Updater use, takes about on average 320ms.
As from that "Happy eyeballs" link the initial message has, "Node tries to connect to the A address with only 250ms timeout, insufficient for many real-world cases (cellular/satellite links, poorly connected ISPs, far away servers, packet loss, etc). This times out, so node proceed to the last candidate which is supposed to have a longer timeout, however the last candidate is an AAAA address and the host has no IPv6 connectivity so it immediately fails"

So it seems that when timeout occurs for those networks outside of the 250ms range, Node then uses an IPv6 address. And for those using only IPv4 networks, well, the connection never occurs.

The resolution, but looks to not be implemented (by Node.js), would be for Node to have the last address to be IPv4, or at least have the last IPv4 address with the longer timeout.

I can concur that I have had the same issue described above and have a fix for it as well.
XOA did work after deploying. But then after updating to the latest version "5.101.0 - XOA build: 20241004" and rebooted, Updates were no longer possible, along with some other minor things.

I applied the fix from the "Happy eyeballs implementation times out prematurely" link above by editing the "/etc/systemd/system/env" file.
Commands:

sudo nano /etc/systemd/system/env

Added in the NODE_OPTIONS line after the HOME line as shown below:

HOME=/tmp
NODE_OPTIONS='--network-family-autoselection-attempt-timeout=500'

WRITE (CTRL-C) and EXIT (CRTL-X)
Reboot XOA

@olivierlambert said in XOA Failing on Check-in:

So it's the case in an IPv6 context I assume, right?

I think it is only the time out setting as the primary cause of the problem with IPv6 as a secondary cause.
I am also in Australia, and just using IPv4 to Ping the address that I am seeing XOA Updater use, takes about on average 320ms.
As from that "Happy eyeballs" link the initial message has, "Node tries to connect to the A address with only 250ms timeout, insufficient for many real-world cases (cellular/satellite links, poorly connected ISPs, far away servers, packet loss, etc). This times out, so node proceed to the last candidate which is supposed to have a longer timeout, however the last candidate is an AAAA address and the host has no IPv6 connectivity so it immediately fails"

So it seems that when timeout occurs for those networks outside of the 250ms range, Node then uses an IPv6 address. And for those using only IPv4 networks, well, the connection never occurs.

The resolution, but looks to not be implemented (by Node.js), would be for Node to have the last address to be IPv4, or at least have the last IPv4 address with the longer timeout.

I can concur that I have had the same issue described above and have a fix for it as well.
XOA did work after deploying. But then after updating to the latest version "5.101.0 - XOA build: 20241004" and rebooted, Updates were no longer possible, along with some other minor things.

I applied the fix from the "Happy eyeballs implementation times out prematurely" link above by editing the "/etc/systemd/system/env" file.
Commands:

sudo nano /etc/systemd/system/env

Added in the NODE_OPTIONS line after the HOME line as shown below:

HOME=/tmp
NODE_OPTIONS='--network-family-autoselection-attempt-timeout=500'

WRITE (CTRL-C) and EXIT (CRTL-X)
Reboot XOA

I know this has been some time for this thread, but raising it due to having the same issue and finding via a web search.
I encountered the same problems when attempting to deploy from the Website and XO-Lite. I also had a failure when trying to download the deploy.sh. The cause of the problems appears to be due to outdated OpenSSL version (OpenSSL/1.0.2k-fips) when using curl.

I am using the latest XCP-ng version of 8.3
I did perform an update after the installation.

Running the command:

curl https://xoa.io/deploy > deploy.sh

Results in:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (35) OpenSSL/1.0.2k-fips: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure

Running:

curl --version

Results in:

curl 8.6.0 (x86_64-koji-linux-gnu) libcurl/8.6.0 OpenSSL/1.0.2k-fips zlib/1.2.7 OpenLDAP/2.4.44
Release-Date: 2024-01-31
Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp
Features: AsynchDNS GSS-API HSTS HTTPS-proxy IPv6 Kerberos Largefile libz NTLM SPNEGO SSL threadsafe UnixSockets

I was not successful in updating OpenSSL or Certificates (I did not add any respositories).

However, downloading the deploy.sh script by wget was successful and I was able to then deploy XOA.