That's why XO proxies are great and the go-to solution Alternatively, you can deploy an XO inside the target network and manage your hosts from there (but you won't have the unique central console with one XO+proxies for the entire infrastructure)

@acebmxer Hello, the XO team is currently working on a solution. We will keep you inform as soon as it is on release.

I will create a new thread from your message

@AtaxyaNetwork It is Debian 12. I found the problem and will post again if there's more issue. The VM stopped using its static IP, not sure how that happened, but I re-added it to /etc/network/interfaces and it's working again.

Hi @Andrew. This PR should fix your issue https://github.com/vatesfr/xen-orchestra/pull/8854

@DustinB That pic was taken from the host tab. But yes I removed from the settings tab and host 2 still shows under pool 1 and all looks ok. Thank you.

@pierrebrunet fixed now, thanks.

@Danp THANKS! That did the trick. I was able to clean up after doing that. Thanks so much!

@olivierlambert Yes sir, it is and I'm glad I confirmed this for myself. Thanks also for helping me understand how the VM Suspend process works. Hopefully this post helps other newbies with the same understanding in the future.

@Razor_648 While I was writing my previous message, I have been reminded that there are also issues with LVHDoISCSI SR and CBT, you should disable CBT on your backup job and on all VDI on the SR. It might help with the issue.

@dinhngtu Thank you so much. If you want me I'll be at the pub.

@andriy.sultanov After running that command I didn't have anything returned.

@ph7 worked, ty.

@lsouai-vates Duly noted. If amd when you do get a moment, could you have a look at https://xcp-ng.org/forum/post/94297 and offer up any guidance on how I can stop the debug log entries and also the double timestamp entries in the audit.log file? Thank you.

@kagbasi-ngc You are welcome.

@olivierlambert, yes, thank you. I will open that ticket.

@AtaxyaNetwork It will/it does

@olivierlambert Thanks!

removed the failed server connection. Restarted xo-server service. Added new host again. Seems fine now. In hind sight, I could have very well recycled a DHCP ip here as well, if that is a known issue...

Sounds a like a bug to me, we can maybe check what's displayed in there and take a look at xe level to see what's the problem Ping @lsouai-vates