Certificate chain of Compute Manager is invalid
search cancel

Certificate chain of Compute Manager is invalid

book

Article ID: 372076

calendar_today

Updated On:

Products

VMware NSX VMware vCenter Server VMware Telco Cloud Platform VMware vSphere ESXi

Issue/Introduction

  • After a vCenter server certificate is replaced (manually or automatically), the connection between NSX and vCenter server breaks, causing the Compute Manager Connection Status to show as Down on the System → Fabric → Compute Managers UI.

  • Attempting to resolve the issue by editing the Compute Manager in the NSX UI and clicking Save fails with the following error:
    Certificate chain of Compute Manager <Compute Manager Host Name> is invalid. Please check Issuer and Subject in the chain. (Error code: 90204)

  • Compute Manager appears to be DOWN in NSX UI.



  • Messages similar to the following can be found in the /var/log/cm-inventory/cm-inventory.log file:

    2024-06-24T19:45:24.327Z ERROR http-nio-127.0.0.1-7443-exec-2 VcPlugin 4732 SYSTEM [nsx@1234 comp="nsx-manager" errorCode="MP40219" level="ERROR" reqId="########-#######-#########" subcomp="cm-inventory" username="admin"] Certificate of Vc example.com is invalid. it might be caused by issuer not being same as subject of next certificate in certificate chain.

    2025-03-12T15:13:37.910Z  NSX 5081 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP40428" level="ERROR" subcomp="manager"] Error connecting EAM com.vmware.vim.vmomi.client.exception.SslException: javax.net.ssl.SSLHandshakeException: PKIX path building failed: java.security.cert.CertPathBuilderException: Unable to find certificate chain. on compute manager ####-####-####-####-####

    2025-03-12T15:13:37.910Z NSX 5081 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP26153" level="ERROR" subcomp="manager"] [HostPinned]: Failed to get EAM status for compute manager ComputeManagerModelMsg/####-####-####-####-####, com.vmware.nsx.management.lcm.vc.soap.exceptions.HostBasedVMException: Error connecting EAM on compute manager ####-####-####-####-####. Error javax.net.ssl.SSLHandshakeException: PKIX path building failed: java.security.cert.CertPathBuilderException: Unable to find certificate chain.

Environment

  • VMware NSX
  • VMware vCenter Server

Cause

  • NSX rejects the vCenter Server certificate when one or more of the following certificate chain issues occur:
    • Incomplete or Out-of-Order Certificate Chain: The installed certificate contains only the leaf certificate, or intermediate/root CA certificates are out of order. NSX strictly requires a complete, correctly ordered chain.
    • Extra or Unrelated Certificates: Duplicate, unrelated, or obsolete certificates included in the chain file cause NSX validation checks to fail.
    • Missing Subject Alternative Name (SAN) Entries: The certificate lacks the vCenter FQDN, short name, or IP address entries in the SAN extension.
    • Incomplete Service Certificate Activation: Replacing the certificate through the vSphere Client UI can leave underlying vCenter services (such as VPXD or Reverse Proxy) using mismatched certificates.

Resolution

The certificate chain must be ordered as follows:

  • Server / Leaf Certificate (vCenter Server)
  • Intermediate Certificate(s)
  • Root Certificate

 

  1. Inspect, Format, and Re-apply the Certificate Chain

    1. Inspect the active certificate chain presented on port 443 by running the following command for the vCenter Server:
      #> openssl s_client -showcerts -connect <VC-Host>:443
      Note: Replace <VC-HOST> with the vCenter Server IP address or FQDN.

    2. Review the output to confirm that the leaf certificate is immediately followed by intermediate CA certificate(s) and terminates at the root CA certificate, with no missing or duplicate certificates.You can use any certificate-checking tool/resource to validate certificate chain.

    3. If the chain is out of order or incomplete, construct a new full-chain PEM file (e.g. fullchain.crt) using a text editor in strict top-down sequence: Leaf/Server→ Intermediate→ Root.

    4. Transfer the corrected certificate chain file to a directory on the vCenter Server (such as /root/certs/) using a secure file transfer utility (SFTP or SCP).

    5. Launch the Certificate Manager utility on the vCenter Server to import the updated chain:
      #>/usr/lib/vmware-vmca/bin/certificate-manager

      Select Option 1 (Replace Machine SSL certificate with custom certificate) and follow the prompts to import the custom certificate chain and private key.
      Refer to Machine SSL certificate renewal using Custom Certificate Authority (CA) in vCenter Server for detailed CLI instructions.

      Note: If using a custom CA-signed certificate, contact your Certificate Authority vendor to re-issue a corrected chain file if any CA certificate is missing.

       

  2. Sync the Compute Manager in NSX

Once the certificate chain is updated on vCenter Server:

    1. Log in to NSX Manager
    2. Navigate to System → Fabric → Compute Managers

    3. Select the affected Compute Manager and click Edit

    4. Click Save without modifying any settings to trigger certificate re-validation

    5. Verify that the Connection Status updates to Up.

 

Resolution for VMware Cloud Foundation (VCF) Environments:

In VCF environments, use SDDC Manager to update vCenter certificates. Refer to the documentation below to update the custom CA-signed machine SSL certificate on vCenter Server, then trigger the NSX sync via  System → Fabric → Compute Managers → Edit → Save

VCF 9: Replace a Certificate with an External CA-Signed Certificate

VCF 5.x and below: Install Third-Party CA-Signed Certificates Using Server Certificate and Certificate Authority Files

 

Workaround:

To temporarily restore connectivity:

  1. Revert the vCenter Machine SSL certificate to the default VMCA-signed certificate.
  2. Log in to NSX Manager, navigate to System → Fabric → Compute Managers, select the Compute Manager, click Edit, and click Save.
  3. Verify that the Connection Status shows Up.

Additional Information

Diagnostic Tools:

Run the CARR script to automatically analyze thumbprint or chain order inconsistencies. See Using Certificate Analyzer, Results and Recovery (CARR) Script to fix certificate related issues in NSX.

vSphere Client UI Limitation:

Replacing certificates via the vSphere Client UI may fail to update all internal service bindings even when the chain is valid. Use Replace a vCenter Machine SSL Certificate with a Custom CA-Signed Certificate via CLI instead of Add Custom Certificates Using the vSphere Client.

 

 Inspecting individual certificates:

  1. Save each certificate block from the chain to a separate PEM file. Inspect its subject, issuer, validity dates, and SHA-256 fingerprint
    openssl x509 -in certificate.pem -noout -subject -issuer -dates -fingerprint -sha256
  2. Confirm that each certificate belongs to the intended certification path and is issued by the expected parent CA.
  3. Identify exact duplicate certificates by comparing their SHA-256 certificate fingerprints. Remove unrelated certificates from the corrected bundle only after confirming the intended chain.


Reusing the same leaf certificate:

Neither the vCenter UI nor the /usr/lib/vmware-vmca/bin/certificate-manager script allows re-applying an identical leaf certificate. To re-apply the same leaf certificate with a corrected chain:

  1. Replace the current Machine SSL certificate with a temporary VMCA-signed certificate.
  2. Replace it again with the original leaf certificate accompanied by the corrected chain.

For further details, see Replacing vSphere Certificates

 

Additional KBs: