Proxy enable: Failed to deploy OVF Package

With time, and the evolution of vSphere products like VMware Lifecycle Manager; it’s possible that you stopped to use UMDS service (Update Manager Download Service). For just enabling the proxy feature on the vCenter management interface (port 5480)

This change will allow you to be more flexible in your update process and be more confident with the HCL matrix.

Since vSphere 7, your vSphere Lifecycle manager permits you to see updates, check HCL, and see which VMSA is not applied on your vSphere environment… The only condition is to allow your vCenter to reach *.vmware.com, and most of the time security team will allow you to do this only through a proxy

But in the meantime, it’s possible that you faced an issue; No more OVF deployment or OVF upload (in the content library) will work.

On the vSphere Task status, you can read :

Failed to deploy OVF package. ThrowableProxy cause A general system error occurred.

You will observe this type of message in /var/log/vmware/vpxd.log:

Transfer failed: Invalid response code: 403, note that HTTP/s proxy is configured for the transfer.

My recommendation is just to modify the proxy configuration of the vCenter the range of management + the local domain of management.

In /etc/sysconfig/proxy

Where :

• mydomain.local is your domain of management
• 10.10.1.0/24 is your CIDR of management ESXi network

Remark: in case of vCenter file-based backup repository is out of your management domain, you will need to mention it in the NO_PROXY configuration file.