vsphere - service Unavailable

[AntoineWAHL]

I have no way to access anymore our VMware console https://192.168.2.4/vsphere-client/

It reports the following error :

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x7f23f805da60] _serverNamespace = /vsphere-client _isRedirect = false _port = 9090)

Unfortunately, windows websphere client also doesn't work anymore and we really need to start a windows virtual machine located on it.

I just get an access to local text console.

Maybe there is a command line / CLI access to start the windows virtual machine from this local console ?

Is there any way to solve this ?

How could I proceed ?

Thanks a lot for your support,

Best regard, Antoine

[vijayrana968 · Accepted solution]

If you get acces to ESXCLI on host, you can Power ON the VM using below steps.

opower on a virtual machine from the command line:

1. List the inventory ID of the virtual machine with the command:
   
   vim-cmd vmsvc/getallvms |grep <vm name>
   Note: The first column of the output shows the vmid.
   
   
2. Check the power state of the virtual machine with the command:
   
   vim-cmd vmsvc/power.getstate <vmid>
   
3. Power-on the virtual machine with the command:
   
   vim-cmd vmsvc/power.on <vmid>

For your main issue of Web client error, make sure all services are running on vCenter (Specially vSphere Web Client). Start if any service is stopped, if possible reboot.

"503 service unavailable" error when connecting to vSphere Web Client (2121043) | VMware KB

[AntoineWAHL]

Well... sounds great !... CLI just worked fine to restart our Windows server.

Thanks a lot, so much !!!

About "503 service unavailable" error when connecting to vSphere Web Client,

I tried resolving this issue, verifying that connectivity exists from the machine trying to access the vSphere Web Client to vCenter Server with telnet by running this command:

telnet vcenter_fqdn 9443

Unfortunately, it doesn't work... telnet command reports an error, it cannot open any connection on port 9443

TELNET command fails from any computer.

To get access to text main console, we need to be in front of the ESX server.

I guess something might be wrong in our vCenter but I have no idea about the way to solve this.

Thanks a lot again for your help,

Best regards, Antoine

[AntoineWAHL]

Of course, I used the following :

telnet 192.168.2.4 9443

[vijayrana968]

What is the results of telnet command. It will return 'telnet not recognized' if telnet isn't enable on client machine, if it returns blank with curson blinking it means port is open.

Also are you able to FQDN of vCenter server via PING or NSLOOKUP ?

[AntoineWAHL]

Well, TELNET client is already enabled and works.

PING 192.168.2.3 just works fine also, but you've got it about FQDN... this is the trouble I have to check for !

NSLOOKUP 192.168.2.3 reports an error : Non-existent domain

I try TELNET througt a remote network... maybe this is the reason... I will try from a local host ASAP

[AntoineWAHL]

vSphere is on 192.168.2.4... not 2.3... PING and NSLOOKUP report the same results... I will chech for FQDN soon

[vijayrana968]

What if you access https://192.168.2.4:9443/vsphere-client/

[AntoineWAHL]

If I try to access https://192.168.2.4:9443/vsphere-client/​ it reports a Can't display error page :

[AntoineWAHL]

Now, I just noticed https://192.168.2.4/vsphere-client actually reports a certificate error :

It says Unallowed Certificate : (unapproved authority)

When I display Certificate I get this :

I just tried installing the Certificate... unfortunately, error remains exactly the same trying to access https://192.168.2.4/vsphere-client

[vijayrana968]

Yes, this is certificate error, you need to dig up logs more. Please see step 4 and 5 in "503 service unavailable" error when connecting to vSphere Web Client (2121043) | VMware KB