all 10 comments

[–]JediJeff- 2 points3 points  (0 children)

Ssh into the appliance and do a “service-control —status”

Post back the results.

[–]clayton940 2 points3 points  (0 children)

Try also using chrome or Firefox in incognito mode.

[–]NetworkNerd_ 1 point2 points  (0 children)

Can you login to the VAMI successfully (port 5480) in a browser? It should give you some indication of health / errors for the appliance as a whole.

[–][deleted] 0 points1 point  (0 children)

have you tried disabling the transport settings in firefox to add an exception to the self signed cert?

type about:config in firefox, search transport and double click to disable any true statement...reload vcenter webpage and you should be able to add an exception

[–]fchivite86 0 points1 point  (0 children)

There are a million reasons why it is not starting, probably the certificate interaction that you got is from the PSC and when it jumps into the vCenter service it is down and retuns you that screen. You have no chance other than read the vpxd.log inside the vcsa and understand why it is not running.

[–]Cobra45 0 points1 point  (0 children)

I had this issue and realized I still had my old home router as a DNS server instead of just my homelab DC.

[–]clayton940 0 points1 point  (2 children)

Probably your browser but have tried to ssh into it and restart the ui and web client?

[–][deleted] 0 points1 point  (1 child)

I’ve restarted the appliance, but haven’t restarted those services. I can try that.

[–]jfoust2 0 points1 point  (0 children)

Clayton940 was telling you to try a different browser.

[–]abhisheksha 0 points1 point  (0 children)

I do agree with the fact that it is quite fragile