How to Fix the vCenter Error: No Healthy Upstream

Error: VMware vCenter No Healthy Upstream

 “No healthy upstream” is a software error that prevents the operation of an application. After installation or upgrading to vCenter Server Appliance (VCSA 7.0 Update3), when accessed to vCenter UI url (https://vcenter:443/ui), you may encounter an error: no healthy upstream. The is because of some unexpected parameters/bugs while deploying vCenter.

You can access vCenter Server Appliance Management Interface at port 5480 and check the services, if all services show as healthy, but you still cannot access web client, you need to change network settings from vCenter Server Appliance Management Interface.

In this article, I will focus on the vCenter no healthy upstream error and offers detailed steps to fix it.

How to Fix No Healthy Upstream Error in vCenter 7

Before making any changes to vCenter appliance, you should backup vCenter or take a snapshot. You can configure IP address setting from DHCP to static with below steps. You can try to fix vCenter no healthy upstream error:

☞ Stop vCenter and restart the service
☞ Upgrade your virtual machine
☞ Change the settings in vCenter
☞ Choose an older hardware compatibility option

🚩 Process to fix the no healthy upstream error in vCenter 7.0:

1. Log in to VMware Server Managment vami portal with 5480 port, go to Networking, and you can see the IP address shows as DHCP even if it was given as static.

2. Click EDIT at top right corner.

3. In the Edit Settings section, change the setting from Obtain IPv4 settings automatically to Enter IPv4 settings manually and click Next.

4. Enter the username and password for SSO credentials.

5. Review the settings and click the checkbox to acknowledge that you have made a backup of your vCenter server and unregistered extensions before continuing with your network configuration.

At the same time, check the Next Steps after network settings are configured successfully.

1. All deployed plug-ins will need to be reregistered.

2. All custom certificates will need to be regenerated.

3. vCenter HA will need to be reconfigured.

4. Hybrid Link with Cloud vCenter server will need to be recreated.

5. Active Directory will need to be rejoined.

6. Click Finish.

Once update is 100% completed, close the window and go back to vCenter Server Appliance Management Interface to test.

If you want to change the same GUI setting using vCenter Server SSH. Open shell and change DHCP=no in the file /etc/systemd/network/10-eth0.network.

🚩 Suggested answers of vCenter no healthy upstream error:

Besides to check the network settings, below you can also check the suggested answers of vCenter no healthy upstream error.

• Check the validity of each certificate in vCenter server
• Upgrade VMware Hardware version and choose the correct OS for vCenter

✍*Note: Take a snapshot from vCenter Server VM before hardware version upgrade, as it’s none reversible task to previous versions.

• Shutdown the vCenter >> right click on the VM >> Compatibility >> Upgrade VM Compatibility.
• Right click on the vCenter and choose Edit settings >> VM Options >> General Options >> Select VMware Photon OS
• Check DNS (you should be able to resolve FQDN names from vCenter)
• Check NTP (Time should be synced and correct between ESXi hosts and vCenter Server)

If all the services which are set to Automatic start are running without any errors or warnings, the error is solved. Now do you know how to fix VCSA no healthy upstream error?

*As we mentioned, you should prepare a complete VCSA backup, Meanwhile, it’s necessary to backup VMware VMs to avoid the data loss due to reversible tasks.

[Pre-Upgrade Essentials] Backup Solutions for vCenter Environments

VCSA is a very convenient official platform for centrally managing ESXi virtual environments and large numbers of VMs on it. However, vCenter does not provide direct virtual machine backup, so the larger your vCenter management environment and the more data you have, the more you need a professional and easy backup solution.

Opting for a professional backup tool offers greater efficiency compared to relying solely on built-in features. Here, I would like to introduce a centralized VMware backup software - AOMEI Cyber Backup.

It automates the backup process of multiple VMware ESXi VMs managed by vCenter Server. By directly adding your vCenter Server account, it can complete agentless backup of all ESXi virtual machines, which greatly saves backup time and simplifies the backup process.

✦ Agentless Backup: create complete and independent image-level backup for VMware ESXi VMs.
✦ Easy VM Backup: batch backup large numbers of VMs managed by vCenter Server, or multiple VMs on a standalone ESXi host.
✦ Multiple Storage: backup to local or network share destinations.
✦ Cloud Archive: make a backup copy on Cloud storage, like Amazon S3.
✦ Automated Execution: create backup schedules to automate backups daily, weekly, or monthly.
✦ Restore Entire VM: restore immediately available VMs from any selected restore points.

AOMEI Cyber Backup supports VMware ESXi 6.0 and later versions. You can click the following button to download the 30-day free trial.

Easy Steps to Batch Backup VMs on vCenter Server

1. Bind Devices: Access to AOMEI Cyber Backup web client, navigate to Source Device > VMware > + Add VMware Device to Add vCenter or Standalone ESXi host. And then click … > Bind Device.

2. Create Backup Task: Navigate to Backup Task > + Create New Task, and select VMware ESXi Backup as the Backup Type.

3. Set Task Name, Device, Target, Schedule, and Cleanup as needed.

• Task Name: you can change the task name or use the default name with an ordinal.
• Device: batch select large numbers of VMs managed by vCenter Server for centralized backup.

• Target: select to back up to a local path, or to a network path.

• Archive: check "Archiving backup versions to Amazon S3" and choose the added Amazon S3.

• Schedule (optional): perform full, differential, or incremental backup, and automate execution according to the frequency you specified.

• Cleanup (optional): automatically delete the old backup copies that exceed the retention period you specified.

4. Run Backup: Click Start Backup and select Add the schedule and start backup now, or Add the schedule only.

✍Created backup tasks will be listed and monitored separately, for progress checking, schedule changing and restoring. It’s easy to make a clone of a virtual machine in the same or another datastore/host, without reinstalling or configuring a new VM by clicking Restore to new location.

FAQs Related to the "vCenter No Healthy Upstream" Error

Q: What factors can trigger the "no healthy upstream" error in vCenter?

A: Possible causes encompass network connectivity problems, service outages, misconfigurations, firewall restrictions, resource constraints, DNS resolution issues, and certificate-related problems.

Q: Can you suggest best practices for avoiding the "no healthy upstream" error?

A: Regularly monitor upstream service health, maintain an updated inventory of network components, implement redundancy where feasible, and have a comprehensive disaster recovery plan in place.

Summary

After upgrading your vCenter appliance, you may notice that vCenter is no longer working properly and display no healthy upstream error messages. This is definitely because of some unexpected parameters while deploying the vCenter. So this article describes the solutions of vCenter no healthy upstream. Besides the answer of networking, I also presented the other solution to fix VCSA no healthy upstream error at the end of the article.