Failed to communicate with the vCenter Single Sign on server

Deploying a new VMware vCenter Virtual Appliance today, I received the error ” Failed to communicate with the vCenter Single Sign On server https://xxx.xxx.xxx.xxx:7444…. ”

This error has the same resolution as my previous article Failed to connect to VMware Lookup Service

Failed to communicate with the vCenter Single Sign on server

Failed to communicate with the vCenter Single Sign on server

 

Now the issue I have found with both of these problems, is after the first power on, the appliance does an automatic configuration, including assigning a DHCP IP address.  If you then re-configure the appliance and chang the hostname or IP address of the vCenter Virtual Appliance.  The certificate that was created on initial configuration is no longer valid.  To resolve this issue, follow the steps below:

  1. Login into vCenter VA Configuration https://[hostname/IP]:5480
  2. Select the Admin tab
  3. Click Toggle certificate setting, you will see Certificate regeneration enabled change to Yes.
    Failed to connect to VMware lookup service
  4. Re-boot the Virtual Appliance
During the bootup procedure you will see


Hostname or IP has changed. Regenerating self signed certificate.

If this doesn’t resolve your issue, please read this page Need some help getting your vCenter Single Sign On Configured? created by Justin King, which lists articles on how to get SSO up and working

2 Responses to Failed to communicate with the vCenter Single Sign on server

  1. gluuservers10 September 9, 2013 at 11:06 am #

    Very valuable blog.This exception is usually comes when host name and IP address changes.In this blog very useful steps are discuss to resolve this issue.And again you acn enjoy its services.

    idp saml

  2. Gul (@4Gul) February 27, 2014 at 2:02 pm #

    As unhelpful as the original technote in the VMware KB> I followed those steps, rebooted the appliance and still get the error. Moreover, the “Regenerate certificate” radio button is still on “Yes.” What to do next? No idea, haven’t found it addressed in any of the KB articles I’ve come across.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Copyright David Hill

Powered by WordPress. Designed by Woo Themes

Close Bitnami banner
Bitnami