XO Lite: Change URL

mx234

Hello, I am new to XCP-NG, I just did a clean install of XCP-ng 8.3.0 from xcp-ng-8.3.0-20250606.iso

I'm looking for a lightweight approach to managing a few VMs so I wanted to use XO Lite in my browser. I'm currently in a different location than the XCP-NG host (which is behind NAT). So, I setup a Cloudflare tunnel to act as a reverse proxy.

I'm able to load the XO Lite dashboard using https://mynew.public.url , however the browser is trying to load some resources from the host's private IP https://192.168.11.18

I found this comment form last year about setting publicUrl in XOA's config. However I haven't yet figured out exactly how to do this, or what the relationship is between XOA and XO Lite in the current XCP-ng release

I tried adding a new file /etc/xapi.conf/publicurl.conf with:

[http]
publicUrl = 'https://mynew.public.url'

However after rebooting and trying to use XO Lite with my new URL, I'm unable to open a VM console and I see the browser making requests to https://192.168.11.18

Any tips would be appreciated!

ph7

@mx234
I'm running netbird with an exit node and I get access to my LAN.
Everything works great

Kreeblah

I'm curious about this, too, though for a different reason.

I installed a real certificate onto my XCP-ng host, and the login page works fine. But after I log in, I get an error about an unreachable host since it's trying to access resources by IP address (and, since it's a real certificate signed by a trusted CA, doesn't have the IP address as a SAN entry). So, I click the link to open the IP address in a new tab, allow the cert mismatch, and then I'm good to reload the original tab.

Basically, navigating to XO Lite via an FQDN doesn't work without some fiddling unless you run your own CA and can enter the IP addresses on the certs you generate (and trust its certs on your endpoints).

olivierlambert

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).