-
-
Hi @mjtbrady, if you get the login screen, it means it's working. Are you sure you entered the right password for your host? You can check if there's been an error by opening the browser console with F12, then "Console" tab. If there's a
SESSION_AUTHENTICATION_FAILED, it means you entered the wrong password (proper feedback on failed authentication will come soon
). If there's a different error message instead, could you post it here, please? -
wget https://lite.xen-orchestra.com/dist/ -O /opt/xensource/www/xolite.htmlis now fixed
-
@olivierlambert I confirm that the wget now works.
@pdonias I am sure the password was correct. It is a randomly generated one from my password manager. So it was cut and paste. But I just tried it again and is now working.
Thanks all.
-
@mjtbrady Yes, there was an issue on our side but it's fixed, now. Thanks for the feedback and let us know if you have other issues
-
-
XO Lite can be cloned on the local computer or XCP-ng host, to run without internet?
-
Looks good. I like that you have a dark mode in there form day one.
Just to manage my expectations.
Is the code that we are pulling "live" development, meaning that it is likely to change and potentially be broken frequently or is it "snapshots" where everything that has been implemented is supposed to work?
Or something else?
-
- Until it will be available at a version 1.0, it will be loaded from our server. This is easier to rebuild/distribute a new version until we are satisfied with the design/features.
- We rebuild manually, so we won't rebuild when it's broken. Keep in mind this is light version of XO, so you won't have tons of features except basic stuff to bootstrap your infrastructure.
- When we'll reach the production version, we'll package it inside XCP-ng directly, so no internet connection will be needed. We'll see how often we'll update it (and how). In an ideal world, a mechanism that's able to get a more recent version from our server if you can and fallback to the version installed would limit the frequency of package update, but we need to think carefully on how to do this.
-
Hi, @olivierlambert
Looks like lite version is perfect for start but looks like something is missing here?
where are the logs from webserver to troubleshoot this issue?
-
Please force refresh (Ctrl + F5)
edit: it's also possible your pool doesn't have a name
-
@olivierlambert
It's a fresh installation, one host only mgmt network configured during installation.
Looks like only dashboard loading as expected.
Host dashboard not working as well
My config:
I've tried on Firefox(104.0) and Chrome(104.0) my OS Linux
XCP-ng release 8.2.1 (xenenterprise) - no internet access
Storage is NOT configured yet -
If you have no VM and the host doesn't have a pool name, then you have everything loaded
-
@olivierlambert
How to start setup infrastructure (assume it was the main reason to develop lite) if there is nothing available at start? -
Because it's a first alpha release and not a v1.0?
-
@olivierlambert
Got some output from chrome:Audit usage of navigator.userAgent, navigator.appVersion, and navigator.platform A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. Starting in Chrome 101, the amount of information available in the User Agent string will be reduced. To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData. Note that for performance reasons, only the first access to one of the properties is shown. 1 source index.cb584bcd.js:1But got the answer already "first Alpha"
Good practice is to add comment to content f.ex. "Network - Not ready yet" or something similar to prevent stupid questions like mine -
High level overview feedback:
So a bit of feedback from me too.- The layout looks great!
- I believe it has just enough to get one started with using the hypervisor (taking into account the existing labels and the placeholder buttons) or to help you in a pinch.
Current issue found that I assume should work at this time based on other messages is that the console seems to have been implemented but is not working. Chrome inspector console shows: WebSocket connection to 'wss://<my local ip address>/console?uuid=e4cd9c61-d399-a3fa-33f7-5699c920d523&session_id=OpaqueRef%3A927fa4fe-74c2-456a-bfd8-d84e98c3bf42' failed. After that there is a line with "Failed when connecting: Connection closed (code: 1006)".
The interface looks very clean and oriented on functionality. Congratulations and keep up the good work!
-
What version of XCP-ng are you using @bogdantomasciuc ? The console should work on 8.2.1
-
@bogdantomasciuc This is probably due to the browser rejecting self-signed SSL certificates when it tries to connect to the console (the console connections go directly to the slave hosts instead of going through the master). To fix that, go to each of your slave hosts' landing pages with HTTPS (https://<slave host IP>/). The browser should ask you if you want to accept self-signed certificates. Click on Accept. Once you've done that for all your hosts, go back to XO Lite, refresh and the consoles should work.
In the next releases, XO Lite will be able to detect when the self-signed certificates haven't been accepted and give clear instructions on what to do
-
@redy Thanks for the feedback, we've added a "coming soon" message on pages that aren't implemented yet, to avoid confusion.
