Hi, what version of HCX have you deployed? 

4.6.0 and 4.6.3

both see the same issue

Are you using a complex password? Have you tried with something simpler?

Are there any firewalls which may be blocking port 9443 between you and the deployed VM?

Are the network/gateway, NTP and DNS configs correct during the deployment process?

I have tried with complex password and with simple password

this is on my home lab -- local lan -- so no firewall or anything in between

yes the configurations are right, I have double checked

Have you tried an alternate browser/incognito mode? Are you putting in https://<HCX IP>:9443

There was a bug to do with NTP/DNS space/comma separation which stopped some services coming up, but that PR was fixed in 4.6

Also ssh in and check the date is correct.

I checked web.log and found below error repeating

Line 66634: ERROR in ch.qos.logback.classic.pattern.SyslogStartConverter@612fc6eb - Could not determine local host name java.net.UnknownHostException: home-hcx-01.home.local: home-hcx-01.home.local: Temporary failure in name resolution

I found that in /etc/resolv.conf the nameserver entry was missing

I added the name server and restarted web and app engine service and then the port 9443 came up

but I then rebooted my appliance to verify if it retains the setting and it did not

DNS setting is lost now -- post reboot and now the port 9443 is not responding again

I have assigned static IP to this setting and then rebooted the server but then too /etc/resolv.conf does not retain the nameserver setting

any suggestion how can /etc/resolv.conf retain the nameserver on reboot?

Nameserver information is in /etc/systemd/resolved.conf

If it is not correct then there might be an error during the ova deployment process.

dns entry is correct there

there should be some way to fix this?

During deployment I was keeping this field blank because of which it was giving the issue

if this field is important then they should put an asterisk next to it

Thanks Chris for your help!

Thanks for updating, and great to hear that the issue is resolved.

Did you try leaving this field blank with 4.6.3? I believe the log you attached was for 4.6.0

If you see the same error with 4.6.3, please let me know and I will raise this internally.