HCX Manager - "Error communicating to VC endpoint Reason: SocketException"

Products

• VMware HCX

Issue/Introduction

• After the HCX Manager (Connector/Cloud) was updated to version 4.10.0, the HCX Manager is unable to connect to vCenters.
• When attempting to reconnect to vCenter, the following error is observed: "Error communicating to VC endpoint Reason: SocketException":

• The SocketException error is observed in /common/logs/appliance-management/appliance-management.log:

2024-08-07 18:28:10.907 UTC [CertificateSyncService_SvcThread-1, Ent: HybridityAdmin, , TxId: ########-####-####-####-############] WARN  c.v.v.hybridity.LookupServiceAdapter- Error response received querying lookup service https://<VC-FQDN-or-IP>/lookupservice/sdk, service type admin:
 {
     "status": "FAILURE",
     "failure": "SocketException",
     "details": "java.net.SocketException: Connection reset\n\tat java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)\n\tat 

Environment

HCX

Cause

Network Configuration: Routing, proxy configuration, or other network settings.

If you are running HCX 4.10.0 and using proxy:
The proxy exclusion list is not working for domain name specified in HCX Appliance-management Interface (: 9443 UI). Refer to HCX - Proxy Exclusion not working when using REGEX patterns.

Resolution

• If you are running HCX 4.10.0 and using a proxy configuration:
  • Upgrade to HCX 4.10.1 or higher.
  • Refer to the article HCX - Proxy Exclusion not working when using REGEX patterns for more details.

 

• If you are running HCX 4.10.1 or higher and using a proxy configuration:
  • Add the vCenter FQDN and IP to the proxy exclusion list.
  • Restart the HCX services.
  • For more information, access Configure a Proxy Server 

• If you are running HCX 4.10.1 or higher and not using a proxy configuration:
  • Test connectivity by running the following commands:
    ping <vCenter IP>
ping <vCenter FQDN>
curl -kiv https://<vCenter-FQDN>