Inquiry Regarding XCP-NG Web UI Access Issue

Sandeep1996

Dear Community Members,

I hope this message finds you well. I am currently involved in a proof-of-concept deployment of XCP-NG within our organization, and I am encountering an issue with accessing the XCP-NG web UI.

I have successfully deployed XCP-NG on our new hardware linux servers and also set up XOA on a VM hosted within one of the XCP-NG servers. However, despite confirming that port 80 is listening, I am unable to access the XCP-NG web UI. I have attempted to access it both through a web browser and using the curl command directly on the server, but neither method has been successful.

It's noteworthy that I can successfully access the web UI of XOA. I have verified with our Network Engineering team, and they have confirmed that ports 80 and 443 are open from the servers.

As we are currently in the initial stages of our XCP-NG proof of concept, I would greatly appreciate any insights or suggestions regarding potential configuration issues that I might have overlooked. Your expertise and guidance on this matter would be invaluable.

Thank you in advance for your time and assistance.

Best regards,
Sandeep

olivierlambert

Hi,

The integrated UI, called XO Lite, will be only available "by default" in XCP-ng 8.3. If you want to test it in 8.2, you need to install it by yourself.

A zero install process can be also used:

https://lite.xen-orchestra.com/#/?master=<IP_of_your_XCP-ng_master>

Don't forget to visit the host webpage first to accept the self-signed certificate

Sandeep1996

Thank you @olivierlambert

planedrop

What's the reason to login to the XO Lite UI for this proof of concept though? I'm just curious because XOA is a pretty full featured WebUI for managing everything XCP-ng, I use it in prod and have for some time and never once have felt the need to access the host locally.

ajpri1998

@planedrop This is an added control plane.

It could be used for a few reasons:

something happens with your XO, you can still manage VMs and even deploy XOA.
You have a small enough setup that doesn't need XO. Such as just one host.
Easy for beginners. I love XCP-ng, but explaining that the control plane is a VM that isn't automatically installed is quite strange to hear for some people.

planedrop

@ajpri1998 I agree in regards to XOA getting damaged somehow, so that makes sense.

I think my question here to OP was more about why they're concerned with it if they already have XOA. Normally if something happens to XOA though you'd SSH into the XCP-ng host and figure it out from there (which also means XO Lite could be enabled).

Not criticizing at all, just was curious about the use case here in specific since it's being evaluated for enterprise use.