Backup failures with odd connection refused errors
-
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.txtI'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.
-
From the log you attached, the failure is on
session.login_with_password, and XO tries::1:443and then127.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. -
P poddingue marked this topic as a question
-
@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.13uuid ( RO) : 2b1579d3-d45a-4d67-a423-20ddbbd61e00
name-label ( RW): meriadoc
address ( RO): 192.168.1.12uuid ( RO) : 7641f7a2-5774-4303-939f-afc3b6b4e35e
name-label ( RW): samwise.somezone.net
address ( RO): 192.168.1.10With 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 it's seems more like it's the XCP-NG side.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login