If the certificate on ESXi can't be verified by vCenter, it would fail to add ESXi to vCenter with such error message at task bar.
A general system error occurred: Failed to verify certificate on <ESXi-FQDN-or-IP>. When ESXi Certificate Mode is set to custom it is mandatory to install valid certificate on ESXi host before adding the host to VC
This article is applicable when custom CA certificate isn't required on ESXi.
Certificate chain broken.
Resolution A
To perform it on ESXi Host Client, see Place an ESXi Host in Maintenance Mode in the VMware Host Client
To perform it on vSphere Client, see Place a Host in Maintenance Mode
To perform it by Command Line, see Place a Host in Maintenance Mode using esxcli command
mv /etc/vmware/ssl/rui.crt /etc/vmware/ssl/rui.crt.bakmv /etc/vmware/ssl/rui.key /etc/vmware/ssl/rui.key.bak
/sbin/generate-certificates
services.sh restart
ESXi Host Client >> "Host" >> "Manage" >> "Security & users" >> "Certificates" to verify the change.We need to check the certificate mode being used. This can be verified by checking the value of vpxd.certmgmt.mode on the vCenter server. There are three available modes: VMCA mode, thumbprint mode and custom CA mode. If the ESXi hosts are using one certificate type while the vpxd.certmgmt.mode on the vCenter is set to another, the hosts will fail to connect to vCenter and trigger the error mentioned above.
To know where exactly you can find this setting, please follow the below tech-doc:
Change the Certificate Mode
Following the above doc, check the value of value of vpxd.certmgmt.mode . Depending on the type of certificates your ESXis are using , change the value of vpxd.certmgmt.mode on the vCenter accordingly if it has the wrong value.
If you need to revert to the previous SSL certificate, follow the steps below:
mv rui.crt.bak rui.crtmv rui.key.bak rui.key
services.sh restart
ESXi Host Client >> "Host" >> "Manage" >> "Security & users" >> "Certificates" to verify the change.