Internet connectivity - Check XOA failed.

[zorro]

The internet check was timing out on the IPv6 address for xen-orchestra.com IPv4 was fine the whole time.

curl -4 -I --max-time 15 https://xen-orchestra.com/ # HTTP/2 200
curl -6 -I --max-time 15 https://xen-orchestra.com/ # couldn't connect

What fixed it was disabling IPv6 at boot, then rebooting so xo-server starts with it already off:

printf '%s\n' 'net.ipv6.conf.all.disable_ipv6=1' 'net.ipv6.conf.default.disable_ipv6=1' | sudo tee /etc/sysctl.d/99-disable-ipv6.conf

After that, xoa check was green, including internet connectivity and no more check for upgrade issues. I'm hoping this fixes my XO Config Cloud Backup. I will report back if not.

17/17 - Internet connectivity: Error: HTTP connection has timed out
at ClientRequest.<anonymous> (/usr/local/lib/node_modules/xoa-cli/node_modules/http-request-plus/index.js:61:25)
at ClientRequest.emit (node:events:519:28)
at ClientRequest.patchedError [as emit] (file:///usr/local/lib/node_modules/xoa-cli/index.mjs:31:17)
at TLSSocket.emitRequestTimeout (node:_http_client:927:9)
at Object.onceWrapper (node:events:633:28)
at TLSSocket.emit (node:events:531:35)
at TLSSocket.patchedError [as emit] (file:///usr/local/lib/node_modules/xoa-cli/index.mjs:31:17)
at Socket._onTimeout (node:net:604:8)
at listOnTimeout (node:internal/timers:585:17)
at process.processTimers (node:internal/timers:521:7) {
url: 'https://xen-orchestra.com/',
originalUrl: 'http://xen-orchestra.com/'
}

XOA Update sometimes failed too but hitting Refresh a couple times got it going.
10/1/2026, 10:03:28 AM: All up to date
10/1/2026, 10:26:26 AM: Start updating...
10/1/2026, 10:26:32 AM: HTTP connection has timed out
10/1/2026, 10:27:14 AM: Start updating...
10/1/2026, 10:27:14 AM: stable channel selected
10/1/2026, 10:27:14 AM: All up to date

[poddingue]

Thanks for posting the fix.

The same thing came up in an older thread, https://xcp-ng.org/forum/topic/9957, where disabling IPv6 also made xoa check go green.

@HamiltonWDS explained a likely reason in https://xcp-ng.org/forum/post/87831: Node tries the addresses with a short timeout and can end up on the IPv6 one.
Your curl -6 test helps a lot here, because it shows IPv6 doesn't connect at all on that network, so it's more than a slow path.

Turning it off in XOA seems reasonable if you don't use IPv6 there; if you do, I'd guess the router side is where it really needs fixing, though I could be wrong (still haven't migrated to IPv6 myself ).

Curious whether it sorts out the Cloud Backup too.

[acebmxer]

@poddingue

I had issue with a remote xo proxy.. showed error in xoa untill i disabled ipv6. But only with one of two remote proxies. This was in a support ticket.

[john.c]

@acebmxer said:

@poddingue

I had issue with a remote proxy.. showed error in xoa untill i disabled ipv6. But only with one of two remote proxies. This was in a support ticket.

Did you test your full stack IP v6 readiness with one of the online testers? The reason being your local LAN maybe ready even at your router level, but if your ISP doesn’t have full stack (or even dual full stack - v4 and v6) then FQDN addresses which are only on IP v6 only may not work). Also v4 and v6 IP address has to also be associated with the FQDN being contacted.

[acebmxer]

@john.c

We currently dont use ipv6 internally. No network changes were made at this location other then moving the proxy to the correct network for nbd connections. With that move some how made the ipv6 issue appear. So it was just easy to disable ipv6 in the proxy. I guess if we ever switch to ipv6 (no plans too) then i guess i will have to look back into it.

[john.c]

@acebmxer said:

@john.c

We currently dont use ipv6 internally. No network changes were made at this location other then moving the proxy to the correct network for nbd connections. With that move some how made the ipv6 issue appear. So it was just easy to disable ipv6 in the proxy. I guess if we ever switch to ipv6 (no plans too) then i guess i will have to look back into it.

If any VMs are accessible online then it’s vital for IPv6 Readiness to be complete. As there are only IPv6 addresses now being available and issued to online users. Also if by proxy your referring to internet access proxy, you can have IPv6 disabled but beware that if any system in the access path to FQDN’s you, access goes IPv6 only you’ll be cut off.

If you mean XO Proxy then it’s even more vital to go IPv6 as you’ll likely, be transporting over an even wider part of the Internet.

Additionally IPv6 offers optional privacy extensions allowing for temporary addresses, amongst other enhancements. One major advantage of IPv6 is that the use of IPSec is built right into the stack itself rather than an add on protocol.