"Cannot download VIB ''. This might be because of network issues or the specified VIB does NOT exist or does NOT have a proper 'read' privilege set. Please make sure specified VIB exists and is accessible from vCenter Server"
/var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log may see entries similar to below: error vmware-vum-server[24817] [Originator@#### sub=DownloadMgr] [downloadMgr 797] Download failed for url: [https://dl.broadcom.com/###############################/PROD/COMP/ESX_HOST/main/esx/vmw/vib20/esx-base/VMware_bootbank_esx-base_7.0.3-0.125.#########.vib](https://dl.broadcom.com/############################/PROD/COMP/ESX_HOST/main/esx/vmw/vib20/esx-base/VMware_bootbank_esx-base_7.0.3-0.125.########.vib) ####-##-##T##:##:##.###Z info vmware-vum-server[24817] [Originator@#### sub=DownloadMgr] [downloadMgr 640] Download job {###########} finished, bytes downloaded = 0 ####-##-##T##:##:##.###Z verbose vmware-vum-server[11839] [Originator@#### sub=DownloadMgr] [downloadMgr ###] Download job {###########} finished ####-##-##T##:##:##.###Z verbose vmware-vum-server[11839] [Originator@#### sub=DownloadMgr] [downloadMgr ###] Removing download job {###########} in queue ####-##-##T##:##:##.###Z verbose vmware-vum-server[11839] [Originator@#### sub=DownloadMgr] [downloadMgr ###] Current download count: 0 ####-##-##T##:##:##.###Z error vmware-vum-server[11839] [Originator@#### sub=HostUpdateDepotManager] [logImpl 71] Downloading file: [https://dl.broadcom.com/###############################/PROD/COMP/ESX_HOST/main/esx/vmw/vib20/esx-base/VMware_bootbank_esx-base_7.0.3-0.125.#########.vib](https://dl.broadcom.com/############################/PROD/COMP/ESX_HOST/main/esx/vmw/vib20/esx-base/VMware_bootbank_esx-base_7.0.3-0.125.########.vib) failed, 0 byte downloaded.
vCenter Server 7.x
vCenter Server 8.x
Due to stale entries in the VUM DB, successful download of some VIBs fail from the newly configured depot URLs with unique tokens.
To help resolve the issue, please reset the VUM DB and reconfigure the depot configurations and retry the update/patch.
1. Ensure to have valid Snapshots/backups (offline snapshots of all nodes in a enhanced linked environment) of vCenter prior to making any changes.
2. Reset VUM DB by following the below KB steps: Resetting the VMware Update Manager Database
3. Reconfigure new depot URLS with below KB steps: VCF authenticated downloads configuration update instructions