Backup failures with odd connection refused errors

CLiF

Hello! I'm having a problem with my backups that started last week. I ran into some problems with one of my three nodes and ended up essential rebuilding it. Since that time when the backups run they fail immediately with errors like "connect ECONNREFUSED 127.0.0.1:443"

Here is an example:
2026-08-05T07_00_00.001Z - backup NG.txt

I've used netcat to check that the ports are open and tried to make sure services are all running. From what I can tell they are. The only other thing that is a bit off is that I can't migrate VMs in the pool. Copying a VM works just fine though.

I am running on XCP-NG 8.3 and Xen Orchestra commit 03d2a. Currently running XO as a docker but was running originally using the script. Could use some guidance with what other things to check.

poddingue

From the log you attached, the failure is on session.login_with_password, and XO tries ::1:443 and then 127.0.0.1:443.
So it is XO trying to reach a host, not your remote, and whatever address it holds for that host is resolving to loopback.
You rebuilt one of the three nodes and you moved XO into Docker, so my guess is the host came back into the pool with a hostname instead of an IP, and that name does not resolve inside the container the way it did for the script install.
It would fit the rest too: migration goes host to host over the management address, copying does not, which is why one works and the other doesn't.

Could you paste the output of xe host-list params=uuid,name-label,address? I am guessing here, and @Team-XAPI-Network will know much better than me whether resetting that address is the right move.

CLiF

@poddingue Here is the ouput of the command:

$ xe host-list params=uuid,name-label,address
uuid ( RO) : 8b0ac09d-a723-4a18-85ae-86660746d8aa
name-label ( RW): frodo
address ( RO): 192.168.1.13

uuid ( RO) : 2b1579d3-d45a-4d67-a423-20ddbbd61e00
name-label ( RW): meriadoc
address ( RO): 192.168.1.12

uuid ( RO) : 7641f7a2-5774-4303-939f-afc3b6b4e35e
name-label ( RW): samwise.somezone.net
address ( RO): 192.168.1.10

With moving it to the Docker container, I only did that after I was already experiencing the same issue with a system that used the script to setup XO. I had hoped it was something on the XO side but is it maybe more on the XCP-NG side?

CLiF

Hello @poddingue and @Team-XAPI-Network is there anything else to check?

poddingue

Your xe host-list output kills my guess.
All three addresses are real LAN IPs with nothing on loopback, so the loopback is probably coming from the XO side rather than from XAPI.
I did test one thing: given a name that resolves to both families, Node reports connect ECONNREFUSED ::1:443 and connect ECONNREFUSED 127.0.0.1:443 together, which is what your log shows, while the literal 127.0.0.1 only ever names one address.
That suggests something is handing XO a name rather than an IP, and localhost is the obvious candidate, so it's worth checking what you have registered for that pool under Settings then Servers, which is where the address comes from in the first place: https://docs.xen-orchestra.com/xo5/manage_infrastructure#add-a-host .

The migration failure I'd keep separate for now, and could you paste the exact error XO gives when one fails? I don't know whether the two are the same problem and I'd rather have the text than keep making wild guesses.