Webclient is inaccessible with IP address and outside vCenter

[virtualvikram2]

Hi all,

Hope you are having gr8 day.

We have recently upgraded from vSphere 5.0 to 5.5. After upgrade everything is working find except Webclient. It is not accessible through the URL: https://ipaddress:9443/vsphere-client with in the vCenter and outside. We are able to access vCenter through https://localhost:9443/vsphere-client. Are we missing something here. Kindly suggest.

Regards,

Vikram kumar.

[a_p_]

This sounds like a firewall issue, i.e. port 9443 being blocked!? If this is the Windows based vCenter Server, check the Windows firewall and allow port 9443 for incoming traffic.

André

[virtualvikram2]

We are not able to access webclient from the vCenter machine itself and other machine in the same segment. Windows Firewall for these VMs are off.

[abhilashhb]

Try with FQDN.

https://vcenter.example.com:9443/vsphere-client.

Also ping the vCenter IP and check if its reachable from outside. Restart the web client service once.

[virtualvikram2]

Unable to access with FQDN, able to reach vcenter server from outside network and nslookup is resolve the IP. Tried restarting the web client service, but no luck.

[rh5592]

Did you install the web client in a different path? There is a bug in web client if installed in a path other than the default. See KB article VMware KB: Connecting to vSphere Web Client fails with the error: HTTP Status 404

[virtualvikram2]

Hi Rommel,

Thanks alot for you reply,

No, we have not installed the Web Clien in different path.

[virtualvikram2]

Hi,

We have restarted the web client which didn't not help. So, we have logged in through administrator@vsphere.local and then we have restarted the Webclient then we were able to access the webclient with  https://ipaddress:9443/vsphere-client.

We are not sure, if we have to log in first time with administrator@vsphere.local and then it will allow to access webclient with IP address.

[warring]

Have you tried a different browser?

[virtualvikram2]

Yes, we have tried with different browsers at the time of the issue. But, the issue resolved only after we logged in with administrator@vsphere.local and restarted the webclient