Cannot connect to XO-Lite build XCP-ng 8.3 Latest

PNO3

@olivierlambert
Hi Olivierlambert, what would be the easiest way to do this? Should I just re-install from a newer iSO? It looks like 8.3.0 is the latest available iSO, which is what is currently installed.

gduperrey

@PNO3 There is currently no more up-to-date ISO.

We recommend simply updating from an XO or running a yum update from the command line and rebooting the host.

For more information on updates and how to perform them: https://docs.xcp-ng.org/management/updates/

You can also view informations on the latest updates on our blog: https://xcp-ng.org/blog/tag/update/

olivierlambert

Yes, a more up to date ISO will come at some point (likely for the LTS)

PNO3

@olivierlambert , @gduperrey

Thanks everyone so much for the help. I moved the host computer over to the outside facing network and updated, 52 updated packages. Strangely enough I could still not reach the host PC the first time I tried after updating. Instead of getting the error mentioned before, I hit the login page, then got a blank white page after I logged in. I connected both systems to the outside facing network and re-tried it and then it connected no problem. After this I was able to unplug both systems and put them both back on the air-gapped LAN, and connect no problem. Is there som resource that needs to be downloaded the first time you try to connect? The updates definitely fixed my original problem, I'm just wondering for future reference if the white screen is supposed to happen.

olivierlambert

If your XCP is fully up to date, you should be able to enjoy XO Lite fully offline at the URL/IP of the host, because since few month, if the online version doesn't respond, we'll fallback on the offline one.

Stwarf

Instead of creating a thread about the same thing I figure I'd add to this thread for I'm having the same issue. I do have some additional information that may help. I can login in and use Xo-Lite using this https://lite.xen-orchestra.com/#/?master=192.168.0.5 url but if I use https://192.168.0.5 or https://192.168.0.5/xolite.html I get a HTTP 431 request header fields too large Exceeded the maximum header size on arc browser(Chromium based) and and unable to connect on FireFox. I also want to add that the login page loads when I enter this url https://lite.xen-orchestra.com/#/ but when I enter the correct password it will say An Error Has Occurred. I got it to work using the master link above but I don't understand why when entering the local address doesn't pull it up.

olivierlambert

https://lite.xen-orchestra.com/#/ without any IP in the query string won't work, because XO Lite doesn't know where to connect (to which pool master). That's perfectly normal
If your XCP-ng 8.3 isn't up to date, it's also normal (but will be fixed with a fresh ISO) that it doesn't work correctly. Please make sure your XCP-ng host is up to date, then simply go on the IP address of the host in your browser (without any extra path)
Double check the URL/IP is correct an not conflicting with something else

Stwarf

@olivierlambert thanks for the speedy reply.

That makes sense.
I conducted a yum update command to update the system before I attempted to connect and I got the same results.
I was very thorough in checking everything was typed correctly and I also used different browsers to make sure it wasn't a browser issue and I also disabled my VPN just incase that could have caused any issues. I also checked my router in case I double booked an IP on accident. Since it was a new install, I reinstalled the 8.3 image again and conducted all the updates again and my results were the same as I mentioned in the previous post where the only way to get xo-lite to work was to use https://lite.xen-orchestra.com/#/?master=192.168.0.5 url. It's not the biggest deal to use that URL but I was curious if that's a known issue or maybe a problem with my setup.

olivierlambert

Okay so using the external URL means you are loading the Javascript from our servers and then connecting from your browser to the host successfully (so it means the API of the host is responding).

Still, it's not normal the UI doesn't work after your host is fully up to date have you rebooted after the updates?

Stwarf

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