• vCenter Server and clusters fail to connect to the Internet when the system-wide proxy of vCenter Server is set.

Note: In order to check if your vCenter server system is using a proxy, see the following information: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcsa.doc/GUID-7576FBBE-8B67-4D3F-B859-C9688E9442D7.html

You can also check if the vCenter Server Virtual Appliance is using a proxy by accessing it through SSH and running the following command in the shell: cat /etc/sysconfig/proxy | grep -v ^#

Output Example:

• Unable to Log in to Customer Connect using the vSphere Web Client.
• Navigating to vSAN Health > vSAN Build Recommendation Engine Health, you see an error similar to:
  
  Unexpected VMware Update Manager (VUM) baseline creation failure. Please check vSAN and VUM logs for details.
  Internet access is unavailable. Please restore Internet connectivity for VSAN to come up with build recommendations.
   
• In the /var/log/vmware/vsan-health/vmware-vsan-health-service.log file, you see  entries similar to:
  
  2017-08-10T07:22:01.21Z WARNING vsan-health[healthThread-852be566-7d9c-11e7] [VsanCloudHealthUtil::checkNetworkConnection] Internet is not connected.

2017-08-10T12:27:52.311Z ERROR vsan-health[Thread-140923] [VsanCloudHealthDaemon::run] VsanCloudHealthSenderThread exception: <urlopen error [Errno 110] Connection timed out>
Traceback (most recent call last):
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthDaemon.py", line 337, in run
profiler=self.profiler):
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthDaemon.py", line 279, in collectedResults
VsanCloudHealthCollector.updateManifestWithPerCluster(serviceInstance)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthDaemon.py", line 230, in updateManifestWithPerCluster
cls._updateManifest()
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthDaemon.py", line 190, in _updateManifest
manifestVersion = cls._queryManifestVersion()
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthDaemon.py", line 174, in _queryManifestVersion
dataType='manifest_version', objectId=MANIFEST_VERSION_UUID)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthConnector.py", line 209, in getClusterHealth
maxRetries=maxRetries, waitInSec=waitInSec)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthConnector.py", line 247, in getObject
responseBody = self._getPhoneHomeResultsWithRetries(urlParams)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthConnector.py", line 279, in _getPhoneHomeResultsWithRetries
VsanCloudHealthConnectionException: <urlopen error [Errno 110] Connection timed out>

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.