Unkindly error message, cant do anything! Several reboots, waiting 10-15 min but nothing is helping.
is there any solution?
Really appreciate your answer.
Have you seen this communities link and is it applicable to your situation-
If you found my answers useful please consider marking them as Correct OR Helpful
"Several reboots, waiting 10-15 min but nothing is helping."
This is not a very scientific strategy, you would be better off spending time finding out why the Web Client is not accessible/functional as opposed to repeatedly doing something you have already tested that does not resolve the issue.
Check and ensure that all services required for a functional vCenter and Web Client are being started and running:
# service-control --status --all
If necessary services (e.g. vsphere-client) are stopped then manually restart them and check that they DO start and stay up:
From the desktop that you are trying to connect to the Web Client check that this connection is possible:
# telnet <vcenter_fqdn> 9443
If both of the above are okay then try a different browser.
If still no joy then start looking at the logs for more specific information about what is wrong here (/var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log and /var/log/vmware/vpxd/vpxd.log)
When you see the error 503, it means that it cannot talk to vCenter service or the service is down.
to check the service status
service-control --status --all gives all service status and if vpxd is showing stopped.. check the vpxd.log in /var/log/vmware/vpxd if appliance or c:\programdata\vcenterserver\logs\vpxd or vmware-vpx (depending on versions)and look for the latest logs which gives you an idea on whats happening with that service.
All VMware services restarted with Services "console".
Then tried to run # service-control --status --all
Cant connect to VIServer with or with PowerCLI and Powershell:
"connect-viserver : not recognized as a cmdlet, function, operable program, or script file."
This was no problem before restart. But now it´s looks like a problem.
Hi all, I have the same problem, vcenter server 6.7 on win server 2012 on esxi 6.5 platform.
service-control --stop vsphere-client
service-control --start vsphere-client
service-control --start vsphere-ui
All works perfectly.