vCenter Server Reports "No healthy upstream" for VMware Live Site Recovery After Certificate Replacement
search cancel

vCenter Server Reports "No healthy upstream" for VMware Live Site Recovery After Certificate Replacement

book

Article ID: 441962

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

After replacing expired certificates on VMware Live Site Recovery (VLSR) appliances with new self-signed certificates and successfully reconnecting the site pair, the vCenter Server displays a "no healthy upstream" error when attempting to access the Site Recovery plugin. The VLSR Appliance Management Interface shows the services are healthy and the site pair is connected.

Environment

VMware Live Site Recovery (VLSR) 9.0.2
VMware vCenter Server

Cause

While the VLSR appliances were successfully paired using the newly generated self-signed certificates, the local registration between each VLSR appliance and its respective vCenter Server was not updated. The vCenter Server reverse proxy continues to attempt authentication using the old, expired certificate thumbprint. Reconnecting the site pair alone does not update this local vCenter registration, resulting in the "no healthy upstream" error.

Resolution

To resolve this issue, the VLSR appliances must be reconfigured with their local vCenter Servers to update the certificate thumbprints, and then the site pair must be re-established.

  1. Log in to the VLSR Appliance Management Interface (VAMI) on the first site (https://<VLSR_FQDN>:5480).

  2. Run the reconfiguration wizard to re-register the VLSR appliance with its local vCenter Server. Accept the new certificate thumbprint when prompted.

  3. Repeat steps 1 and 2 for the VLSR appliance on the second (peer) site.

  4. Once both appliances have been successfully reconfigured with their respective vCenter Servers, log in to the vSphere Client.

  5. Navigate to the Site Recovery plugin and run the VLSR site pairing process again to fully re-establish the connection between the two sites.

Additional Information

It may be necessary to log out of the vSphere Client, clear your browser cache, and log back in after reconfiguring the appliances to ensure the UI reflects the updated certificate state.

Powered by Wolken Software