Error "Could not connect to one or more vCenter Server Systems" in vSphere Client due to expired Machine SSL certificate

Products

• VMware vCenter Server

Issue/Introduction

In an Enhanced Linked Mode (ELM) environment consisting of two or more vCenter Servers, a partner node with the FQDN <Not_Visible_vCenter_FQDN> is not visible within the vSphere Client of the remaining vCenter Server systems.

The vSphere Client displays the error: "Could not connect to one or more vCenter Server systems: https://Not_Visible_vCenter_FQDN:443/sdk".

Run the following command on the vCenter Server with FQDN <Not_Visible_vCenter_FQDN>; the "Validity" section indicates that the Machine SSL certificate has expired.

/usr/lib/vmware-vmafd/bin/vecs-cli entry list --store MACHINE_SSL_CERT --text

Environment

VMware vCenter Server 8.0.x

Cause

The Machine SSL certificate has expired on the vCenter Server with the FQDN <Not_Visible_vCenter_FQDN>.

Resolution

If the vSphere Client for vCenter <Not_Visible_vCenter_FQDN> is still accessible, use the Renew action to generate a new certificate. (Refer to Manage vCenter Server Certificates Using the vSphere Client section of Managing vCenter Server Certificates for details.)

Or

Select option:3 Manage certificates to replace Machine SSL certificate in vCert tool. (Refer to vCert - Scripted vCenter expired certificate replacement for details.)

• Use the Menu options - 3. Manage certificates ->  1. Machine SSL certificate ->  1. Replace Machine SSL certificate with a VMCA-signed certificate

 

Additional Information

Could not connect to one or more vCenter Server Systems: https://vCenterFQDN:443/sdk" error in the vSphere Client due to additional SAN entry in certificate