Unable to deploy OVF using vSphere Client when a HTTPS Proxy is configured with NO_PROXY

Products

• VMware vCenter Server

Issue/Introduction

• When attempting to import an OVF package or deploy an OVF template in the vSphere Client, the operation fails with the following error: 
  
  Failed to deploy OVF package. Cause: A general system error occurred: Transfer failed: Error transferring file to https://example.com/nfc/############################/#######.vmdk: Connection reset, note that HTTP/s proxy is configured for the transfer.
  
  
• Error in /var/log/vmware/vpxd.log:

  error vpxd[1408634] [Originator@6876 sub=Default opID=4####9-01] [VpxLRO] -- ERROR task-#######--  -- SCMSSLAAC3-CN1 -- ResourcePool.ImportVAppLRO: :vim.fault.OvfImportFailed
--> Result:
--> (vim.fault.OvfImportFailed) {
-->    faultCause = (vmodl.fault.SystemError) {
-->       faultCause = (vmodl.MethodFault) null,
-->       faultMessage = (vmodl.LocalizableMessage) [
-->          (vmodl.LocalizableMessage) {
-->             key = "com.vmware.ovfs.ovfs-main.ovfs.transfer_failed",
-->             arg = (vmodl.KeyAnyValue) [
-->                (vmodl.KeyAnyValue) {
-->                   key = "0",
-->                   value = "Error transferring file to https://example.com/nfc/############################/#######.nvram: Connection reset, note that HTTP/s proxy is configured for the transfer"
-->                }
-->             ],
-->             message = "Transfer failed: Error transferring file to https://example.com/nfc/############################/#######.nvram: Connection reset, note that HTTP/s proxy is configured for the transfer."
-->          }
-->       ],
-->       reason = ""
-->       msg = "Transfer failed: Error transferring file to https://example.com/nfc/############################/#######.nvram: Connection reset, note that HTTP/s proxy is configured for the transfer."
-->    },
-->    faultMessage = <unset>
-->    msg = ""
--> }
--> Args:
-->
............

  --> Arg state:
--> "error"
--> Arg result:
-->
--> Arg fault:
--> (vim.fault.OvfImportFailed) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>
-->    msg = ""
--> }

 

Cause

This issue occurs when the /etc/sysconfig/proxy configuration file is missing required bypass entries or if the NO_PROXY variable is not formatted correctly. OVF/OVA deployments utilize the NFC protocol, which must bypass proxy servers to communicate directly with ESXi hosts.

Resolution

1. SSH to the vCenter Server as the root user.
2. Create a backup of the current proxy configuration: cp /etc/sysconfig/proxy /var/core/proxy.bak
3. Edit the file /etc/sysconfig/proxy using a text editor (e.g., vi).
4. Ensure the NO_PROXY line begins with localhost, 127.0.0.1, followed by your environment-specific wildcards and subnets. Note: Wildcard entries must start with a leading period. Example: NO_PROXY="localhost, 127.0.0.1, .domain.com, 10.0.0.0/24"
   
5. Save the file :wq!
6. Restart vCenter services for changes to take effect: service-control --stop --all && service-control --start --all

Additional Information

Important Considerations for VCHA Environments: To avoid configuration reversion, perform proxy configuration changes using the VAMI interface (Port 5480), which triggers the built-in synchronization routines across all cluster nodes. If manual editing via CLI is required, destroy VCHA vCenter High Availability (VCHA) Configuration removal, then apply the proxy settings and then re-create VCHA Configure vCenter HA With the vSphere Client

How to configure Proxy Settings for vCenter Server

Unable to deploy OVF using vSphere Client when a HTTPS Proxy is configured

OVF Deployment Fails with "ThrowableProxy.cause" error