Updating URL with token in vSphere Lifecycle Manager fails with "The download source https://dl.broadcom.com/<Download Token>/PROD/COMP/VCENTER/... is invalid or cannot be reached now."
Article ID: 402385
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
- Adding url to download patches in Home > Lifecycle Manager > Settings > Patch Setup in vCenter Server
After clicking the New button, entering the url with token (https://dl.broadcom.com/<downloadToken>/PROD/COMP/VCENTER/...) it fails with a message when clicking on save with:
"The download source https://dl.broadcom.com/<Download Token>/PROD/COMP/VCENTER/... is invalid or cannot be reached now."
- On the
/var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server-###.logon vCenter Server, we see entries similar to belowYYYY-MM-DDThh:mm:ss.326-06:00 verbose vmware-vum-server[05583] [Originator@6876 sub=httpDownload] [httpDownloadPosix 182] * subjectAltName does not match (nil)^MYYYY-MM-DDThh:mm:ss.326-06:00 verbose vmware-vum-server[05583] [Originator@6876 sub=httpDownload] [httpDownloadPosix 182] * SSL: no alternative certificate subject name matches target host name '(nil)'^MYYYY-MM-DDThh:mm:ss.326-06:00 verbose vmware-vum-server[05583] [Originator@6876 sub=httpDownload] [httpDownloadPosix 182] * Closing connection 5^MYYYY-MM-DDThh:mm:ss.327-06:00 error vmware-vum-server[05583] [Originator@6876 sub=httpDownload] [httpDownloadPosix 685] curl_easy_perform() failed: cURL Error: SSL peer certificate or SSH remote key was not OK, SSL: no alternative certificate subject name matches target host name '(nil)'^M
Environment
vCenter Server 7.x , 8.x
Cause
Some https proxy servers use port 80 and vCenter proxy maybe incorrectly configured in the vami wrt the https URL
Resolution
Check your local Proxy admin for the correct settings for your Proxy and configure it on the vCenter by following How to configure Proxy Settings for vCenter Server
Additional Information
May need to add no-proxy to deploy OVF
Feedback
Yes
No
Powered by
