vCenter “No Healthy Upstream”: Causes, Diagnosis, and Recovery
Quick answer: In vCenter, No Healthy Upstream means the vSphere Client front end cannot route the request to a healthy backend service. Broadcom describes it as an alternate HTTP 503 symptom, not a diagnosis. Common causes include stopped services, expired certificates, disk-space or memory pressure, session exhaustion, a changed /etc/hosts file, and Lookup Service problems. … Explore: vCenter “No Healthy Upstream”: Causes, Diagnosis, and Recovery