If the outbound traffic of your SDDC environment is configured to go through a proxy, during the deployment of your VMware reverse proxy OVA, you can configure the VMware Proxy Service to use forward proxy. This way, you can provide your environment with an outbound connection without setting up specific firewall rules.

You configure support for forward proxy connections on the Customize template page during the deployment of the reverse proxy appliance OVA. For more details on deploying the reverse proxy appliance, see Deploying the Reverse Proxy Appliance.

When you configure your forward proxy, it is used for connecting to the VMware Cloud Director service proxy server and to other services, such as VMware Cloud services and Docker Registry. When configured, the forward proxy connection is also used for most commands that you run on the appliance console.

VMware Cloud Director service supports proxy connections that use HTTP and HTTPS proxy protocols.

Setting Value
Network Proxy URI

The URI of the proxy to be used for outgoing HTTP or HTTPS connections.

For example: https://user:[email protected]:8443/

User name and password authentication, as well as port number are supported. Whitespace is ignored. Any special characters in the user name and in the password must be URL-encoded.

Network Proxy Skip

A comma-separated list of IP addresses, CIDR blocks, destination hosts, and ports that are not using the proxy connection.

For example: localhost:443,127.0.0.1,example.svc,200.23.0.0/16

Hostnames are considered DNS suffixes. This means that, for example, example.com matches example.com, www.example.com and foo.example.com. Hostnames are translated to IPv4 addresses before being matched against CIDR blocks or IP addresses on the list. Whitespace is ignored.