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
search cancel

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

book

Article ID: 396787

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • Attempting to update  download URL on Proxy configured vCenter by following Authenticated downloads configuration update instructions - VCF fails with one of the below errors:

    The download source https://dl.broadcom.com/#########/vmw-depot-index.xml is invalid or cannot be reached now.
    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-###.log on vCenter Server, download failures similar to below may be observed:

    YYYY-MM-DDThh:mm:ssverbose vmware-vum-server[09641] [Originator@6876 sub=httpDownload] [httpDownloadPosix 686] Set CURLOPT_PROXY as https_proxy: https://proxy.####.###.###.###:8080/
    YYYY-MM-DDThh:mm:ssverbose vmware-vum-server[09641] [Originator@6876 sub=httpDownload] [httpDownloadPosix 699] Set CURLOPT_NOPROXY as no_proxy: localhost, 127.0.0.1, .*.###.###.###.###
    ...
    YYYY-MM-DDThh:mm:ssverbose vmware-vum-server[09641] [Originator@6876 sub=httpDownload] [httpDownloadPosix 188] *   Trying ###.##.##.##:8080...
    YYYY-MM-DDThh:mm:ssverbose vmware-vum-server[09641] [Originator@6876 sub=httpDownload] [httpDownloadPosix 188] * Connected to proxy.###.###.###.### (###.##.##.##) port 8080
    YYYY-MM-DDThh:mm:ssverbose vmware-vum-server[09641] [Originator@6876 sub=httpDownload] [httpDownloadPosix 188] * ALPN: curl offers http/1.1
    YYYY-MM-DDThh:mm:ss verbose vmware-vum-server[09641] [Originator@6876 sub=httpDownload] [httpDownloadPosix 188] * OpenSSL/3.0.14: error:0A00010B:SSL routines::wrong version number
    YYYY-MM-DDThh:mm:ssverbose vmware-vum-server[09641] [Originator@6876 sub=httpDownload] [httpDownloadPosix 188] * Closing connection
    YYYY-MM-DDThh:mm:sserror vmware-vum-server[09641] [Originator@6876 sub=httpDownload] [httpDownloadPosix 763] curl_easy_perform() failed: cURL Error: SSL connect error, OpenSSL/3.0.14:
    error:0A00010B:SSL routines::wrong version number
    YYYY-MM-DDThh:mm:sserror vmware-vum-server[09641] [Originator@6876 sub=httpDownload] [httpDownloadPosix 763] [backtrace begin] product: VMware Update Manager, version: ####, build: build-####, tag: vmware-vum-server, cpu: x86_64, os: linux, buildType: release
    --> backtrace[00] libvmacore.so[0x00531DC5]
    --> backtrace[01] libvmacore.so[0x0042182A]: Vmacore::System::Stacktrace::CaptureFullWork(unsigned int)
    ...
    --> backtrace[05] libvci-vcIntegrity.so[0x00E0B59A]: Sysimage::HttpDownloadFile(std::__c##11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, Integrity::ProxyServer const&, std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>,
    ...
    --> [backtrace end]
    YYYY-MM-DDThh:mm:sserror vmware-vum-server[09641] [Originator@6876 sub=DownloadMgr] [downloadMgr 705] Executing download job {###########} throws error: curl_easy_perform() failed: cURL Error: SSL connect error, OpenSSL/3.0.14: error:0A00010B:SSL routines::wrong version number
    ...
    YYYY-MM-DDThh:mm:ssinfo vmware-vum-server[09641] [Originator@6876 sub=DownloadMgr] [downloadMgr 643] Download job {############} finished, bytes downloaded = 0
    ...
    YYYY-MM-DDThh:mm:ssverbose vmware-vum-server[11195] [Originator@6876 sub=DownloadMgr] [downloadMgr 561] Current download count: 0
    YYYY-MM-DDThh:mm:ss error vmware-vum-server[11195] [Originator@6876 sub=Default] [updateDownloaderImpl 116] File download error: Downloading file: https://dl.broadcom.com/<TOKEN>/####/vmw-depot-index.xml failed, 0 byte downloaded.

  • On the /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server-###.log on vCenter Server, SSL failures similar to below may be observed:

    YYYY-MM-DDThh:mm:ss verbose vmware-vum-server[05583] [Originator@6876 sub=httpDownload] [httpDownloadPosix 182] *  subjectAltName does not match (nil)^M
    YYYY-MM-DDThh:mm:ss verbose vmware-vum-server[05583] [Originator@6876 sub=httpDownload] [httpDownloadPosix 182] * SSL: no alternative certificate subject name matches target host name '(nil)'^M
    YYYY-MM-DDThh:mm:ss verbose vmware-vum-server[05583] [Originator@6876 sub=httpDownload] [httpDownloadPosix 182] * Closing connection 5^M
    YYYY-MM-DDThh:mm:ss 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 8.x

Cause

Proxy configuration on vCenter is incorrect. In this particular scenario, the  HTTPS URL configured on VAMI Proxy Settings was incorrect

Resolution

Check with your local Proxy admin for the correct settings for Proxy in the environment and configure it on the vCenter by following How to configure Proxy Settings for vCenter Server

Additional Information

Powered by Wolken Software