HCX - Proxy Exclusion not working when using REGEX patterns

Products

• VMware HCX

Issue/Introduction

• You are running HCX 4.10.
• A proxy server is configured with proxy exclusions using REGEX patterns, such as the * wildcard. Examples include:
  • *.example.com
  • *example.com
  • 192.168.0.*
  • 192.168.0.11
• You may experience issues such as:
  • Migration workflow failures.
  • Unable to deploy HCX appliances due to connection resets during OVF upload.
  • Unable to add vCenter and NSX to HCX due to connectivity issues.
  • Unable to establish site pairing.

Environment

HCX 4.10

Cause

Proxy exclusions using regex patterns are being ignored, and this issue is currently under investigation by the HCX engineering

Resolution

The issue will be fixed in future releases.

Workarounds:

• Use proxy exclusion in one of the following formats:
  • fqdn.example.com
  • 192.168.0.11/32
  • 192.168.0.0/24
• Disable the proxy if it is no longer required. Local HCX no longer requires Internet connectivity.
   

Restarting app-engine and web-engine services is required for the proxy changes to take effect. For more information, see How to restart HCX Manager services.