Difference between revisions of "VMware vSphere VCSA no healthy upstream"
Jump to navigation
Jump to search
(Created page with "I've run into the "no healthy upstream" error a few time with newer VMware vSphere installs (now VCSA Appliance) and I feel like I should clearly explain the cause. It's DNS....") |
|||
| Line 1: | Line 1: | ||
| − | I've run into the "no healthy upstream" error a few | + | I've run into the "no healthy upstream" error a few times with newer VMware vSphere installs (now VCSA Appliance) and I feel like I should clearly explain the cause. |
It's DNS. The VCSA Appliance can't start some service due to DNS resolution failure. | It's DNS. The VCSA Appliance can't start some service due to DNS resolution failure. | ||
Fix your DNS settings, reboot the VM, wait about 10 minutes and you're good to go. | Fix your DNS settings, reboot the VM, wait about 10 minutes and you're good to go. | ||
Latest revision as of 08:08, 12 November 2022
I've run into the "no healthy upstream" error a few times with newer VMware vSphere installs (now VCSA Appliance) and I feel like I should clearly explain the cause.
It's DNS. The VCSA Appliance can't start some service due to DNS resolution failure.
Fix your DNS settings, reboot the VM, wait about 10 minutes and you're good to go.