VMware NSX
This happens because of an expired SSL certificate on the target ESXi host where the NSX VIB installation is failing. During the NSX upgrade, the process attempts to establish a secure connection (SSL handshake) with the ESXi host to deploy or update NSX components (VIBs). If the ESXi host's SSL certificate has already passed its expiration date, the SSL handshake fails. This SSLHandshakeException prevents the successful retrieval of existing VIB components and the installation of new NSX software on the host, leading to the upgrade failure.
Workaround
Log in to the vSphere Client (HTML5 client):
Use an administrator account.
Navigate to: Hosts and Clusters → your_datacenter → your_cluster → impacted_host.
Renew the Certificate:
Right-click the affected host.
Select Certificates → Renew Certificate.
Confirm the action. Renewal typically completes within a few moments.
Note: Self-signed certificates issued by vCenter VMCA or renewed through this method are generally valid for 5 years.
Verify the New Certificate:
Run the following command on the host to confirm that a new certificate has been issued and check the expiration date:
openssl x509 -in /etc/vmware/ssl/rui.crt -text -noout | grep -A 2 "Validity"
Restart Management Agents:
Restart the management agents to ensure the host begins using the newly generated certificate:
services.sh restart
Resume NSX Upgrade:
Retry the NSX upgrade process. After successful renewal, the NSX VIB installation status for the host should show as Successful in the NSX UI.
Additional Note
If the certificate does not renew after selecting Renew Certificate and no error is displayed in the task, follow the Resolution guidance in this KB to validate the value for vpxd.certmgmt:
ESXi host’s certificate cannot renew or refresh when vpxd.certmgmt.mode is not "vmca" or "custom"
Prerequisites before refreshing/renewing the ESXi SSL certificates from vCenter server vSphere UI:
"ESXi Host Certificate Status" alert for any host in vCenter Server