<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: no healthy upstream - VCenter Server appliance 7 in vCenter™ Server Discussions</title>
    <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2945238#M93917</link>
    <description>&lt;P&gt;Do you mean 'VAMI' web interface, right?&lt;/P&gt;</description>
    <pubDate>Fri, 23 Dec 2022 09:54:04 GMT</pubDate>
    <dc:creator>KlickerLab</dc:creator>
    <dc:date>2022-12-23T09:54:04Z</dc:date>
    <item>
      <title>no healthy upstream - VCenter Server appliance 7</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2869375#M92442</link>
      <description>&lt;P&gt;Recently, we shutdown our ESXi hosts to switch some SD cards that were installed. The rebuild was successful and had no issues launching up the hosts and starting up all VMs. I noticed backups were failing so I started investigating. It all lead me to finding out that there is "no healthy upstream". I started to read up on a few communities and landed with the following information:&amp;nbsp;&lt;/P&gt;&lt;P&gt;VPXD service is not started and after a few attempts I am circling around with no solution. it appears that, in the summary page, status are healthy. If I go to services, most services are healthy while the rest are stopped. One that sticks out is VCenter Service: stopped. Any help would be appreciated.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Sep 2021 19:40:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2869375#M92442</guid>
      <dc:creator>MPS_IT</dc:creator>
      <dc:date>2021-09-29T19:40:09Z</dc:date>
    </item>
    <item>
      <title>Re: no healthy upstream - VCenter Server appliance 7</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2869379#M92443</link>
      <description>&lt;P&gt;This is a complicated issue, if you have support open an SR, there are multiple services that can be causing this in my experiance.&amp;nbsp; The last time for me it was the STS certificates needed to be regenerated&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/76719" target="_blank"&gt;"Signing certificate is not valid" error in VCSA 6.5.x/6.7.x and vCenter Server 7.0.x (vmware.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Sep 2021 19:47:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2869379#M92443</guid>
      <dc:creator>sjesse</dc:creator>
      <dc:date>2021-09-29T19:47:39Z</dc:date>
    </item>
    <item>
      <title>Re: no healthy upstream - VCenter Server appliance 7</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2869403#M92444</link>
      <description>&lt;P&gt;I attempted to open a support ticket, however, it seems like my Vsphere server essentials is not enough to get support. I followed the steps on the link you provided, however the vpxd service is still in a stopped status.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Sep 2021 22:44:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2869403#M92444</guid>
      <dc:creator>MPS_IT</dc:creator>
      <dc:date>2021-09-29T22:44:55Z</dc:date>
    </item>
    <item>
      <title>Re: no healthy upstream - VCenter Server appliance 7</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2869470#M92445</link>
      <description>&lt;P&gt;What do you see in vpxd.log ?&lt;/P&gt;&lt;P&gt;This &lt;A href="https://kb.vmware.com/s/article/2151430" target="_self"&gt;KB&lt;/A&gt; suggests it could be related to vc certificates that need regenerated.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Sep 2021 08:12:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2869470#M92445</guid>
      <dc:creator>vXav</dc:creator>
      <dc:date>2021-09-30T08:12:31Z</dc:date>
    </item>
    <item>
      <title>Re: no healthy upstream - VCenter Server appliance 7</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2904184#M92996</link>
      <description>&lt;P&gt;Spot on, thank you ... The fix was to run&amp;nbsp;&lt;/P&gt;&lt;PRE&gt; /usr/lib/vmware-vmca/bin/certificate-manager&lt;/PRE&gt;&lt;P&gt;and select option 4:&lt;/P&gt;&lt;DIV&gt;&lt;PRE&gt;&lt;SPAN&gt;Regenerate a new VMCA Root Certificate and replace all certificates&lt;/SPAN&gt;&lt;/PRE&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;10 minutes later it was back online!&lt;/SPAN&gt;&lt;/DIV&gt;&lt;H1&gt;&lt;SPAN&gt;&amp;nbsp;&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@89383C2E498027BD88ABC8EABEB8B8DC/emoticons/1f44d.png" alt=":thumbs_up:" title=":thumbs_up:" /&gt; &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@C129253C8FBC9E6A9BF4FF65B79D7FF7/emoticons/1f44f.png" alt=":clapping_hands:" title=":clapping_hands:" /&gt;&lt;/SPAN&gt;&lt;/H1&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 13 Apr 2022 18:01:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2904184#M92996</guid>
      <dc:creator>Kelv1n12</dc:creator>
      <dc:date>2022-04-13T18:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: no healthy upstream - VCenter Server appliance 7</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2910572#M93087</link>
      <description>&lt;P&gt;I have been seeing this a lot (everytime I make a hardware change on my lab esx) and I would just redeploy VCSA over and over again, this seems to have helped, making it easier than a redeploy.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;still a stupid error message to see after adding more drive space to the datastores.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;oh well, thanks again!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2022 10:12:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2910572#M93087</guid>
      <dc:creator>quasimodem</dc:creator>
      <dc:date>2022-05-23T10:12:26Z</dc:date>
    </item>
    <item>
      <title>Re: no healthy upstream - VCenter Server appliance 7</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2923750#M93409</link>
      <description>&lt;P&gt;Hi every one&lt;/P&gt;&lt;P&gt;For this issue you should just Restart&amp;nbsp;VMware vSphere Client Service in WAMI and after that the error gone.&lt;/P&gt;&lt;P&gt;it doesn't need reinstall Vcenter.&lt;/P&gt;</description>
      <pubDate>Sun, 14 Aug 2022 05:13:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2923750#M93409</guid>
      <dc:creator>Nima-hfashami</dc:creator>
      <dc:date>2022-08-14T05:13:26Z</dc:date>
    </item>
    <item>
      <title>Re: no healthy upstream - VCenter Server appliance 7</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2924151#M93425</link>
      <description>&lt;P&gt;That may or may not work, this error just means that a service isn't started, it could either be a temporary thing or another issue to look into. This is the equivalent to logging into windows and getting stuck at loading user profile, or something similar&lt;/P&gt;</description>
      <pubDate>Tue, 16 Aug 2022 15:44:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2924151#M93425</guid>
      <dc:creator>sjesse</dc:creator>
      <dc:date>2022-08-16T15:44:59Z</dc:date>
    </item>
    <item>
      <title>Re: no healthy upstream - VCenter Server appliance 7</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2930365#M93585</link>
      <description>&lt;P&gt;Go to vcenter server host and set the custom DNS Suffixes ---vsphere.local&lt;/P&gt;</description>
      <pubDate>Sat, 24 Sep 2022 10:11:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2930365#M93585</guid>
      <dc:creator>Afrid007</dc:creator>
      <dc:date>2022-09-24T10:11:29Z</dc:date>
    </item>
    <item>
      <title>Re: no healthy upstream - VCenter Server appliance 7</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2945238#M93917</link>
      <description>&lt;P&gt;Do you mean 'VAMI' web interface, right?&lt;/P&gt;</description>
      <pubDate>Fri, 23 Dec 2022 09:54:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/no-healthy-upstream-VCenter-Server-appliance-7/m-p/2945238#M93917</guid>
      <dc:creator>KlickerLab</dc:creator>
      <dc:date>2022-12-23T09:54:04Z</dc:date>
    </item>
  </channel>
</rss>

