vSphere Replication Appliance is not able to load in vCenter server Replication Manager tab
Article ID: 387376
Updated On:
Products
Issue/Introduction
The vSphere Replication Manager plugin is failing to load in vCenter Server as it is reporting inaccessible
The /opt/vmware/support/logs/dr-client-plugin/drplugin.log
You may see the log traces below in the vSphere Replication appliance when you encounter this error. The errors are highlighted in below log snippet
/var/log/vmware/dr/drconfig.log
java.lang.Exception: Unable to get VR health status at URL: https://vreplication.vmware.com:5480/configureserver/health/hms?ui=1. at com.vmware.dr.plugin.handlers.dashboard.VrHealthStatusHandler$RequestCallback.fail(VrHealthStatusHandler.java:180) at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:591) at java.base/java.lang.Thread.run(Unknown Source)Caused by: javax.net.ssl.SSLPeerUnverifiedException: Host name 'vreplication.vmware.com' does not match the certificate subject provided by the peer (C=US, ST=California, L=Palo Alto, OU=SRM, O="VMware, Inc.", CN=localhost) at org.apache.http.nio.conn.ssl.SSLIOSessionStrategy.verifySession(SSLIOSessionStrategy.java:217) at org.apache.http.nio.conn.ssl.SSLIOSessionStrategy$1.verify(SSLIOSessionStrategy.java:197) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:372) at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:547) at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:120)
/var/log/vmware/dr/drconfig.log :
javax.net.ssl.SSLException: Certificate for <192.168.0.4> doesn't match common name of the certificate subject: vcsa.ad.test\n\tat org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:185)\n\tat org.apache.http.conn.ssl.StrictHostnameVerifier.verify(StrictHostnameVerifier.java:68)\n\tat org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:153)\n\tat com.vmware.vim.vmomi.client.http.impl.ThumbprintTrustManager$HostnameVerifier.verify(ThumbprintTrustManager.java:534)\n\t... 33 more\n"}
--> Caused by: javax.net.ssl.SSLException: Certificate for <192.x.x.x> doesn't match common name of the certificate subject: vcsa.ad.test
--> Caused by: javax.net.ssl.SSLException: Certificate for <192.x.x.x> doesn't match common name of the certificate subject: vcsa.ad.test
--> Caused by: javax.net.ssl.SSLException: Certificate for <192.x.x.x> doesn't match common name of the certificate subject: vcsa.ad.test
--> Caused by: javax.net.ssl.SSLException: Certificate for <192.x.x.x> doesn't match common name of the certificate subject: vcsa.ad.test
--> 2025-03-28 10:10:56,063 [srm-reactive-thread-12] INFO com.vmware.srm.client.h5config.commands.impl.CheckServiceAccountCommand - The Solution user does not exist.
/var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log
[ERROR] sdk-plugin-deployer-38530 com.vmware.vise.plugin.status.RemotePluginStatusServiceImpl DOWNLOAD_FAILED: Error downloading plugin package com.vmware.drui.plugin:9.0.2.24401761 from https://vreplication.vmware.com:443/drplugin/plugin.json.zip. Reason: URL is unreachable. Make sure that the URL is reachable. com.vmware.vise.plugin.download.PluginDownloadException: org.apache.http.client.HttpResponseException: status code: 503, reason phrase: Service Unavailable at com.vmware.vise.plugin.download.PluginDownloadServiceImpl.download(PluginDownloadServiceImpl.java:195) at com.vmware.vise.plugin.async.task.PluginDownloadTask.run(PluginDownloadTask.java:51)
[ERROR] sdk-plugin-deployer-38530 com.vmware.vise.plugin.extension.VcExtensionManager Downloading plugin package: 'com.vmware.drui.plugin:9.0.2.24401761' registered in vCenter: 'vcenter.vmware.com (e66854ad-2f51-4c91-9dec-3f723b5ec991)' has failed. java.util.concurrent.CompletionException: com.vmware.vise.plugin.download.PluginDownloadException: org.apache.http.client.HttpResponseException: status code: 503, reason phrase: Service Unavailable at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273) at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280) at java.lang.Thread.run(Thread.java:750)Caused by: com.vmware.vise.plugin.download.PluginDownloadException: org.apache.http.client.HttpResponseException: status code: 503, reason phrase: Service Unavailable at com.vmware.vise.plugin.download.PluginDownloadServiceImpl.download(PluginDownloadServiceImpl.java:195)
Environment
VMware Live Site Recovery 8.x
VMware Live Site Recovery 9.x
Cause
This issue will be caused when the CN name in the certificate is not matching FQDN of the vSphere Replication Appliance
Resolution
1. On the VAMI page of the appliance try registering with vCenter server . VAMI page : https://<vSphere Replication FQDN >:5480
2. Change the certificate with the information shown in Organization, Locality, State & Country fields and try registering it with vCenter. Ensure all of information matches correctly
3. In the VAMI page go to the "Certificate" tab and click on "change", ensure the FQDN of the vSphere Replication FQDN is properly mentioned and click "change". Ensure that the IP address and FQDN are verified using the forward and reverse lookup by "nslookup" command
Refer the screenshot below
4. After change, the services of the vSphere Replication Appliance will re-start and you need to refresh the webpage
5. The CN=localhost should be changed to CN=vSphere Replication FQDN in certificate after which the vSphere Replication Appliance can be reconfigured to vCenter Server
6. The services need to be restarted in the vCenter Server so it is advisable to take back-up and snapshot of the vCenter Server
# service-control --stop vsphere-ui && service-control --start vsphere-ui
Additional Information
Here is another article for vSphere Replication Appliance DR plugin failing to load in the vCenter
Site Recovery Plugin not showing up or blank in vSphere Client after deployment
Feedback
