VMware Cloud Community
Turny
Contributor
Contributor

Cannot login using Web Vsphere client

Newbie here---

Using VMware ESXi ver 5.5.0 Build 1331820

I need to edit some VMs.   I can log in using vSphere Client 5.5 but the VMs are ver10 or higher.

The VMhost was rebooted today and where the vSphere web client was also rebooted. 

When I click on vSphere Web Client I get this in my browser:

https://localhost:9443/vsphere-client/#

If I change to https://x.x.x.x:9443/vsphere-client/#    the ip of the HOST I get nothing.

Thanks for your help.

0 Kudos
9 Replies
DavoudTeimouri
Virtuoso
Virtuoso

I guess, you have no vCenter and you need to install vCenter and its components to have vSphere Web Client.

So you should install vCenter.

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
0 Kudos
SavkoorSuhas
Expert
Expert

When you say login to vsphere client, are you referring to logging into host using this client or logging into vcenter managing this host using the client?

Also, for web client, you enter https://vcenterIP or FQDN:9443

If vCenter is not installed then it will not work.

If you are unaware if vcenter exists in the machine, then you can do a simple check by going to control panel add or remove programs and verify you see vCenter components like sso inventory service web client and vcenter

If these are not there then you will have to download vCenter iso and install all the components in the order sso>web client>inventory service> vCenter

Suhas

If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points.

Don't Backup. Go Forward!
Rubrik

0 Kudos
Karthikvraj
Contributor
Contributor

You cannot use thick client(C# client) to edit VM's which has hardware version 10. Please note that VMware is going away from C# client.

Btw, did you try using webclient as soon as it was rebooted? If yes, it needs some time to initialize.

Also, is your SSO server embedded or external? If it is external, trying using the SSO server ip with :9443.

Please post the screen-shot of the error you are experiencing.

Thanks,

Karthik Varadaraja

0 Kudos
Turny
Contributor
Contributor

VMware VCenter appears to be loaded.

vCenter Orchestrator, Single Sign-On;

VMware Client:  Integration Plug-in, infrastructure Client 2.5

VMware VCenter:  Inventory Service, Server, Server -Java Components, Server -tc Server

VMware vSphere:  Client 5.5, Update Manager, update Manager Client 5.5, Web Client

The Inventory service is running.

When I log into vSphere Web Client (so I am closer) using https://localhost:9443/vsphere-client/..........

I get this error:

Could not connect to one or more vCenter Server systems:

https://FQDN:443/sdk

But I am logged into the web client with no inventory.

Thanks!

0 Kudos
Turny
Contributor
Contributor

Logging into the host using Client not using vcenter.   I can use root and password.

so I used the local host or ip of the vcenter pc,  using the DC Admin credentials I can log in, but there is no information it is all blank.

Vcenter is installed.  There is a vCenter SSO and vCenter Inventory and web client and vcenter.

0 Kudos
Turny
Contributor
Contributor

SSO server is I believe is external, it is not a VM.   It is a Server 2008 R2 on a Raid 10.

I can log into the SSO server using the Administrator credentials, but when I do that I see nothing in the inventory.   I don't see any existence of my host machine.

There is an error at the top that says:

Could not connect to one or more vCenter Server systems:  https://FQDN:443/sdk

Thanks!

0 Kudos
Turny
Contributor
Contributor

Will anyone help me?  Thanks, Troy@@ !

0 Kudos
Dee006
Hot Shot
Hot Shot

Turny,Can you verify that your NTP service or time is running fine?Please share your vpxd.log and verify your AD identity source.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=205891...

0 Kudos
Karthikvraj
Contributor
Contributor

Since you mentioned, you were able to logon using vSphere thick client - I believe your vCenter is all fine.

Some questions/steps -

1. I believe you have configured everything using FQDN. Do a nslookup of the IP/FQDN(of vCenter Server) from SSO server and make sure you get a reply correctly.

2. Ensure there is no firewall between vCenter and SSO.

3. If the nslookup is not working, ensure all FQDN entries are recorded in DNS.

4. If you want a short-cut, manually keyin the entries of vCenter in SSO server's host file and SSO server's in vCenter.

Thanks,

Karthik Varadaraja

0 Kudos