Site Recovery Plug-in displays "Unknown error" or "Inaccessible" for vSphere Replication and/or VMware Live Site Recovery

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

When accessing the Site Recovery Plug-in from vCenter, the following error is displayed:

• "Site Recovery Manager - UI error: Unknown error. The latest version of Site Recovery UI is not available. Some functionality might be limited"
  
  
  
  
• vSphere Replication and/or VMware Live Site Recovery are showing up as 'Inaccessible' after convergence from 9.0.2 to 9.0.5 version:
  
  

Environment

• VMware Live Site Recovery Manager 8.x

• VMware Live Site Recovery Manager 9.x

• VMware vSphere Replication 8.x

• VMware vSphere Replication 9.x

• VMware Live Recovery 9.x

Cause

• The VMware Live Recovery (VLR) appliance certificate is configured with a short hostname or incorrect FQDN that does not match the actual appliance hostname. As a result, SSL certificate validation fails during internal service communication and plugin registration, causing the Site Recovery Plug-in to become unavailable or inaccessible.

Justification

• /opt/vmware/support/logs/dr-client-plugin/drplugin.log - Explicitly logged a hostname mismatch error: java.io.IOException: HTTPS hostname wrong: should be <VLR FQDN>. This confirms that the plugin expected an FQDN-based identity which the short-name certificate could not provide.

YYYY-MM-DD ##:##:##,209 [srm-reactive-thread-10] WARN  com.vmware.dr.plugin.ls.LookupServiceDiscovery 65####1b-####-####-####-29########24  - Hms LSPP service does not have health endpoint. HMS guid: 82####67-####-####-####-f25######853
YYYY-MM-DD ##:##:##,239 [srm-reactive-thread-10] WARN  com.vmware.dr.plugin.utils.DrUiUtil 53f21b-####-####-####-29########24  - No healthy DR UI found for VC ea####fb-####-####-####-2fd######207, requests size: 1
YYYY-MM-DD ##:##:##,665 [srm-reactive-thread-1] WARN  com.vmware.dr.plugin.utils.ConnectionUtils fb####c2-####-####-####-2b########0a  - Problem occurred while checking connection to https://<VLR FQDN>:5480/configurejava.io.IOException: HTTPS hostname wrong:  should be <VLR FQDN>

• /opt/vmware/support/logs/hms/hms.log - Recorded repeated CertificateValidationException errors. Specifically, checkServerTrusted FAILED for remote server at 127.0.0.1 indicated that the internal service communication was rejected due to SSL trust failures.

YYYY-MM-DD ##:##:##.072 ERROR ping.svr.5259078b-1472-e0b7-9bbf-d44d21406502 [hms-main-scheduled-thread-6] (..net.impl.PersistentConnection) {} [] | Failed to connect to server 127.0.0.1:8123
com.vmware.vim.vmomi.client.exception.InternalException: Error resolving version
Caused by: java.util.concurrent.ExecutionException: com.vmware.vim.vmomi.client.exception.SslException: com.vmware.vim.vmomi.core.exception.CertificateValidationException: [hbrsrv] checkServerTrusted FAILED for remote server at 127.0.0.1
Caused by: com.vmware.vim.vmomi.client.exception.SslException: com.vmware.vim.vmomi.core.exception.CertificateValidationException: [hbrsrv] checkServerTrusted FAILED for remote server at 127.0.0.1
Caused by: com.vmware.vim.vmomi.core.exception.CertificateValidationException: [hbrsrv] checkServerTrusted FAILED for remote server at 127.0.0.1
Caused by: javax.net.ssl.SSLException: [hbrsrv] checkServerTrusted FAILED for remote server at 127.0.0.1

• On vCenter - /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log:

[YYYY-MM-DD:##:##-##:00] [ERROR] -nio-127.0.0.1-5090-exec-955 70211828 151225 200264 com.vmware.vise.mvc.controllers.PluginServiceController   A general error occurred while retrieving plugin (com.vmware.drui.plugin:9.0.5.0.2510039) dynamic extensions info from the plugin server (/plugins/com.vmware.drui.plugin~9.0.5.0.25100392~1563937642/vlr.broadcom.com-443/drplugin/rest/dynamic-items/vm/summary). org.spring
framework.web.client.UnknownHttpStatusCodeException: 526 Invalid SSL Certificate: "-----BEGIN CERTIFICATE-----<EOL>MIIDr....Gp3g==<EOL>-----END CERTIFICATE-----<EOL>"

Resolution

1. Change the VMware Live Recovery Appliance Certificate from short name to FQDN 
   
   
2. Reconfigure the VMware Live Recovery Appliance
   
   
3. Reconfigure the Connection Between Sites

Note : Make sure VC can resolve configured SRM, vSphere replication hostnames.