Have seen a similar issue recently, This could be vCenter proxy issue. when vLCM initiates communication from vCenter to the NSX manager to get its installation bundles, this connection goes to the proxy. You may modify the proxy file on the vCenter and add NSX managers IPs to the exclusion list.
