Failed to deploy OVF package. Cause: A general system error occurred: Transfer failed: Invalid response code: 407

Products

• VMware vSphere ESXi
• VMware vCenter Server 8.0

Issue/Introduction

Issues deploying VM templates and OVA/OVF files.

Consistent failures deploying virtual machine templates, regardless of template or OVA source.

When deploying an OVA through vCenter, it fails with the errors:

Failed to deploy OVF template. Cause: A general system error occurred: Transfer failed: Invalid response code: 407, note that HTTP/s proxy is configured for the transfer.

Failed to deploy OVF package from content library to resource pool.
Cause: A general system error occurred: Transfer failed: Invalid response code: 407, note that HTTP/s proxy is configured for the transfer.

 

Checking /var/log/vmware/vpxd/vpxd.log in the vCenter VM shows the following error:

ResourcePool.ImportVAppLRO::vim.fault.OvfImportFailed msg = "Transfer failed: Invalid response code: 407, note that HTTP/s proxy is configured for the transfer."

 

The /var/log/content-library/cls.log in the vCenter VM may also show the same 407 error:

ImportSessionActivity          | OVF import session <session id> failed with server error.com.vmware.vapi.std.errors.ServiceUnavailable: ServiceUnavailable (com.vmware.vapi.std.errors.service_unavailable) => {
    messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = com.vmware.ovfs.ovfs-main.ovfs.transfer_failed,
    defaultMessage = Transfer failed: Invalid response code: 407, note that HTTP/s proxy is configured for the transfer.,
    args = [Invalid response code: 407, note that HTTP/s proxy is configured for the transfer],
    params = <null>,
    localized = <null>
}],
    data = <null>,
    errorType = SERVICE_UNAVAILABLE

ImportSessionActivity          | Completing import lease ManagedObjectReference: type = HttpNfcLease, value = session[<session id>, serverGuid = <server id>(exception: (vim.fault.OvfImportFailed) {
   faultCause = (vmodl.fault.SystemError) {
      faultCause = null,
      faultMessage = (vmodl.LocalizableMessage) [
         (vmodl.LocalizableMessage) {
            dynamicType = null,
            dynamicProperty = null,
            key = com.vmware.ovfs.ovfs-main.ovfs.transfer_failed,
            arg = (vmodl.KeyAnyValue) [
               (vmodl.KeyAnyValue) {
                  dynamicType = null,
                  dynamicProperty = null,
                  key = 0,
                  value = Invalid response code: 407, note that HTTP/s proxy is configured for the transfer
               }
            ],
            message = Transfer failed: Invalid response code: 407, note that HTTP/s proxy is configured for the transfer

Environment

VMware vCenter Server 8.x

Proxy configured on the vCenter

Cause

Error 407 indicates Proxy Authentication Required indicating Proxy communication is causing the deployment failure between vCenter and the ESXi host.

Resolution

To resolve the issue you will need to investigate and resolve the underlying trust/proxy configuration issue between vCenter Server and the ESXi host.

This includes updating the proxy configuration settings for the vCenter VM.

• Wildcards may be necessary for proper NO_PROXY configuration.
  • The vCenter Server Appliance Management Interface (VAMI) does not support wildcards.
  • Add wildcards to the /etc/sysconfig/proxy file directly on the vCenter VM and restart vCenter services or the vCenter VM afterwards.

    • NO_PROXY=".*.my.domain"

 

To work around this issue by bypassing the vCenter and proxy communication to the ESXI host:

1. Disconnect the problematic ESXi host from the vCenter inventory (to disable lockdown mode if required).
2. Log into the ESXi Host Client directly (using the host's IP address).
3. Deploy the OVA to the disconnected host using Create/Register VM.
4. Once the OVA deployment is complete, re-connect the ESXi host back to vCenter Server.

Additional Information

Proxy behavior is rewritten and improved in vCenter 9.x.