You are here:---VMware vcenter 6.7 | 503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x00007fb6cc081b80] _serverNamespace = /ui action = Allow _port = 5090)

VMware vcenter 6.7 | 503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x00007fb6cc081b80] _serverNamespace = /ui action = Allow _port = 5090)

After playing around for a few days in my lab with vCenter 6.7 I had to reboot my vCenter appliance. After reboot when I was trying connect back to HTML5 web client I received an error:

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x00007fb6cc081b80] _serverNamespace = /ui action = Allow _port = 5090)

Then I tried to connect to a flash web client and worked fine without any error. This maid me to conclude that the issue is only with HTML5 web client. After Googling around I found no related information about this error and then I decided to dig deeper myself.

Since I install vCenter 6.7 on VMware vCenter Server Appliance (VCSA) the first step to look is on VCSA console.

You can connect to Web Console by adding 5480 port to you vCenter URL:  https://VMware vCenter Server Appliance IP address:5480 and user you vCenter administrator credentials to login.

Example: https://192.168.0.200:5480

[separator top=”40″ bottom=”40″ style=””]

Once you successfully  login check Health Status and make sure that everything is good then clink on services

On the page you will see lots of services running and some of them are stopped. Scroll down until you see service called  VMware vSphere Client in my  case is not running as you can see in the screenshot. Select the VMware vSphere Client service and on the top of the page click START.

After you started the service wait for a few minutes until server finish initialise all service and then refresh the HTML5 Web Client page. You should see the home page of HTML5 Web Client coming up.

By |2018-12-29T14:08:18+00:00November 17th, 2018|Categories: vCenter|Tags: , , |1 Comment

One Comment

  1. David March 8, 2019 at 7:00 am - Reply

    Awesome dude. Thanks. Have you managed to work out why the service fails to start?

Leave A Comment