Unable to commission hosts in SDDC Manager/VCF Installer due to "Certificate for host_FQDN doesn't match any of the subject alternative names"
search cancel

Unable to commission hosts in SDDC Manager/VCF Installer due to "Certificate for host_FQDN doesn't match any of the subject alternative names"

book

Article ID: 327187

calendar_today

Updated On:

Products

VMware Cloud Foundation VMware vSphere ESXi

Issue/Introduction

  • Unable to commission new hosts in VCF Installer. The workflow fails with below error
    Failed to connect to <host_FQDN> doesn't match any of the subject alternative names: [list, of, names]
  • The following error is observed on the VCF Installer while commissioning hosts : 


  • Error in /var/log/vmware/vcf/operationsmanager/operationsmanager.log
    ERROR [vcf_om,dd7f90bc5d2c4573,559c] [c.v.e.s.c.c.v.esx.EsxCommandExecutor,http-nio-127.0.0.1-7300-exec-9] Failed to connect to <host_FQDN> com.vmware.vim.vmomi.client.exception.SslException: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <host_FQDN> doesn't match any of the subject alternative names: [list, of, names] Caused by: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <host_FQDN> doesn't match any of the subject alternative names: [list, of, names]

     

  • During creation of the workload domain on the SDDC Manager, the hosts validation fails with the error : 
    Failed to connect to the host. Ensure that the host is reachable, it has a valid certificate with a fully qualified domain name in its Common Name, and credentials are valid.
  • The following is observed on the SDDC Manager : 

Environment

VMware SDDC Manager 5.x

VMware Cloud Foundation 9.x

Cause

  • During ESX provisioning, the installer generates a self-signed certificate before establishing the host identity, resulting in a default Common Name (CN) of localhost.localdomain across all hosts.
  • The VCF Installer/ SDDC Manager encounters SSL/TLS validation errors and subsequent connection failures caused by the hostname mismatch on the FQDN of the hosts and the CN on the certificate on hosts.

Resolution

Re-generate ESX host certificate :
  1. Log in to the ESX Host Client.
  2. Enable SSH on the ESX host.
    1. In the navigation pane, click Manage and click the Services tab.
    2. Select the TSM-SSH service and click Start if not started.
  3. Connect to the ESX host on SSH using root credentials.
  4. Regenerate the self-signed certificate by executing the following command
    /sbin/generate-certificates

    (Optional) : Execute the following command to make the changes persistent across reboots : 

    /sbin/autobackup.sh
  5. Reboot the ESX to apply the changes
    reboot
  6. Verify the correct hostname is listed by executing the following command by connecting to the host using SSH :
    openssl x509 -in /etc/vmware/ssl/rui.crt -noout -text | grep -A1 "Subject"

    Subject Alternative Name should match the ESX host FQDN

    Sample output

    Subject: C = US, ST = California, L = Palo Alto, O = VMware, OU = VMware Engineering, CN = esx.example.com, emailAddress = 
    Subject Public Key Info:
        Public Key Algorithm: rsaEncryption
        X509v3 Subject Alternative Name:
        DNS:esx.example.com

Additional Information