@pdonias confirmed... [image: 1780065202934-screenshot-2026-05-29-103255.png]

I'm not positive, but this may be available RSN in xo-lite.

Hi @olivierlambert and @pilow Thank you for your answers, it helps a lot, Regards, Olivier

It's not meant to be used like that. If you are behind a NAT, the right approach is to have your XOA behind the NAT and inside the same network than the hosts. That's because hosts will always use and return their internal IPs to connect to some resources (stats, consoles etc.). XOA deals with that easily as being the "main control point" for all hosts behind your NAT (or a XO proxy if you prefer).

@ph7 Thank you!

Hi, Somewhere between Q1 and Q2 next year, hard to be more precise

@lsouai-vates Great! Thanks for addressing this

@Greg_E Ah, ok..yeah...guess I did Yep, agree. Really needs more functions...like networking (and elsewhere) ha

I have not had time to work on this, and my lab changed significantly, had to spend a bunch of money to move it to a new rack and that rack has been disconnected for months so no real work in XCP or vSphere and learning to migrate VMs from vSphere to XCP which was one of my big intentions. But a recent post confirms that this "oddity" of trying to create a UEFI VM from XO-lite is still present. I'd bet money that this gets fixed before or when the full release is provided. https://xcp-ng.org/forum/topic/11227/boot-new-vm-to-iso-in-xo-lite Workaround is to either click the button provided to download XOA, or install Linux and XO from sources in BIOS mode. Then you have the full XO to work with to bring everything else up the way you want it. I see it as a minor annoyance right now, not really a bug or problem.

Thanks for engaging! In this thread I would say: Storage I need it to get ISO files uploaded without going native (CLI). Or in other words, the basic stuff you would expect of a web-interface to be able to launch working VM's.

@olivierlambert said in Limiting access to xo-lite to a specific IP address or ssubnet: About iptables, there's /etc/sysconfig/iptables but I'm not sure it's the right place to put manual modification, that's why I pinged the @Team-OS-Platform-Release In a way that's the right place, but one needs to be careful with modifications there.

@olivierlambert can you close this thread?

No. I'm saying that all VMs (HVM) are using RFB consoles, readable with VNC protocol (used by XO or a VNC client). There's no text console since it's like a screen in HVM. If you are stuck on "Loading in progress", it's not a console issue, it's a VM issue. You can use a LiveCD to check what's going on.

@olivierlambert I did reboot the system. The fact that I can access everything fine with the using the external url but not when I try to use the local IP address of the machine is strange. I'm at work currently but I'm going to do a deeper dive when I get home and search through everything in my home network. I just don't know what else to check.

Oh I see. Thanks for explanation

@Danp Yes I. have .. no change

@DustinB Hi Dustin, It's amazing what one can miss when setting something up, and I surely did miss that part. I now see much more in the way of management items. My project for the weekend will be XO/XOCE from source for my home rack. Thanks so much for seeing what I didn't. Take care, Eric

@Greg_E Having backup XO's has always been our policy here. @business we have our min XOA on a (now dedicated Intel server doing the backups, because of the EPYC networking issues) and then a XO (from sources) on the main pool if XOA tanks or during reboots. @home I hace one XO on each host. Has saved me time and time again.