Error: Site Recovery plugin displays "Invalid version" or "URL is unreachable" in vCenter Server.

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• When attempting to reinstall or reconfigure Site Recovery Manager (SRM) or vSphere Replication (VR) appliances, the plugin fails to deploy or render.
• • The vSphere Client Site Recovery UI displays the error: Invalid version: #### (e.g., Invalid version: 9.0.5.0100.2534290).
  • The plugin status under Client Plugins shows: Error downloading plug-in. URL is unreachable. No route to host.
  • The Site Recovery UI does not detect any active VR or SRM instances despite successful appliance configuration.

Environment

• vCenter Server 7.x / 8.x
• vSphere Replication 8.x / 9.x
• Site Recovery Manager 8.x / 9.x

Cause

Stale or duplicate service registrations within the vCenter Server Lookup Service. When multiple versions of the vrUi or h5-dr service endpoints are present, the vSphere Client fails to resolve the correct plugin instance, resulting in version mismatch conflicts or connection failures to decommissioned appliance IPs.

 

 

Resolution

1. Take an offline snapshot of the vCenter Server Appliance.
2. SSH to the vCenter Server Appliance.
3. Export the service registrations to a text file: /usr/lib/vmware-lookupsvc/tools/lstool.py list --url http://localhost:7090/lookupservice/sdk > /tmp/psc_services.txt
4. Identify stale Service IDs by searching for vrUi or h5-dr entries with older versions or incorrect IPs: grep -iC4 h5-dr /tmp/psc_services.txt
5. Unregister the stale Service IDs: /usr/lib/vmware-lookupsvc/tools/lstool.py unregister --url http://localhost:7090/lookupservice/sdk --user "[email protected]" --password '####' --id 'Service_ID_to_Remove'
6. Restart vCenter services to clear the cache: service-control --stop --all && service-control --start --all
7. Log back into the vSphere Client and verify the plugin is detected.

Additional Information

• For assistance with complex Lookup Service cleanup, see Contact Support.