Indeed, @olivierlambert, that was the issue and it works now. So for whoever has the same issue. First go to the local IP address of the host (NOT to the domain name), accept the certificate and then go to /xolite.html and it will work both with the ip address and the domain name in the address field.
Thanx again for clearing things up!

Indeed, @olivierlambert, that was the issue and it works now. So for whoever has the same issue. First go to the local IP address of the host (NOT to the domain name), accept the certificate and then go to /xolite.html and it will work both with the ip address and the domain name in the address field.
Thanx again for clearing things up!

@olivierlambert I am currently on 8.2. I will upgrade and try later. Thank you!
@pdonias The certificates are already accepted. I will check back after I update to 8.2.1 as suggested by @olivierlambert but thank you very much for your suggestion!

High level overview feedback:
So a bit of feedback from me too.

1. The layout looks great!
2. 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!

@olivierlambert Looking forward to it!

@olivierlambert Is this still the standing method of testing XO Lite? It still works but seems to be pretty much at the same stage it was 1 year ago. I was hoping to see some of the new UI from the recent blog posts.