Troubleshooting vSphere Live Site Recovery Plugin "Unknown Error" and SSL Hostname Mismatch

Products

• VMware Live Recovery

Issue/Introduction

This article provides troubleshooting steps for "Unknown error" or "Not accessible" statuses in the vSphere Live Site Recovery plugin caused by SSL hostname verification failures during the HTTPS handshake.

Environment

VMware Live Site Recovery 9.x, VMware Site Recovery Manager 9.x.

Cause

The vSphere Replication or SRM appliance was registered using an IP address instead of its Fully Qualified Domain Name (FQDN). Java HTTP clients strictly enforce hostname verification; if the appliance's SSL certificate Common Name (CN) or Subject Alternative Name (SAN) does not match the registration hostname, a SSLPeerUnverifiedException occurs, preventing the plugin from loading correctly.

Resolution

1. Verify Registration: Check the VAMI or vCenter extension manager to see if the appliance is registered by IP address.
2. Verify Certificates: Ensure the appliance SSL certificate contains the FQDN in its SAN/CN.
3. Correct Registration: Reconfigure the appliances to use the valid FQDN.
4. Restart vSphere UI: SSH to the vCenter Server and restart the UI service:
   1. service-control --stop vsphere-ui
   2. service-control --start vsphere-ui
5. Refresh: Log out and log back into the vSphere Client to confirm plugin health.

Additional Information

 Ensure that DNS forward and reverse lookup records are correctly configured for all FQDNs used in the environment.

Note: For defects and enhancements only, subscribe to the article to be updated on fix status: https://knowledge.broadcom.com/external/article/275360