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.