NSX Upgrade Precheck Fails with "Unable to connect to File"
search cancel

NSX Upgrade Precheck Fails with "Unable to connect to File"

book

Article ID: 413494

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Customer are trying to perform NSX Upgrade Pre-check by uploading the .PUB file to NSX UI
  • Customer are getting below Error
    Error: <Manager_IP> Unable to connect to File /repository/4.2.3.1.0.24####27/UC/localized_eula/EULAContentMessages_<country_code>.properties on source <Manager_FQDN>. Please verify that file exists on source and install-upgrade service is up.
  • Repo_Sync is failing on one or more managers (Steps to verify the same is down below, in resolution) (
    2025-10-03T06:41:38.529Z <Manager_FQDN> NSX 1002442 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] Marking Repo Sync step as failed with errors [[<Manager_IP>] Unable to connect to File /repository/4.2.3.1.0.24####27/UC/localized_eula/EULAContentMessages_<country_code>.properties on source <Manager_FQDN>. Please verify that file exists on source and install-upgrade service is up., [<Manager_IP>] Unable to connect to File /repository/4.2.3.1.0.24####27/UC/localized_eula/EULAContentMessages_<country_code>.properties on source <Manager_FQDN>. Please verify that file exists on source and install-upgrade service is up.]
    2025-10-03T06:41:38.563Z <Manager_FQDN> NSX 1002442 SYSTEM [nsx@6876 comp="nsx-manager" errorCode="MP30040" level="ERROR" subcomp="upgrade-coordinator"] Repository sync is not complete on {0}. Please wait for repository sync to complete, or resolve the errors if repository sync has failed.
  • Certificate Validation Error in the NSX Manager Syslog
    2025-10-03T06:38:42.633Z <Manager_FQDN> NSX 2871320 - [nsx@6876 comp="nsx-manager" subcomp="curl_wrapper" username="uproton" level="INFO"] Calling '/opt/vmware/nsx-common/python/nsx_utils/curl_wrapper', '--silent', '--head', 'https://<Manager_FQDN>:443/repository/4.2.2.1.0.24####84/Manager/vmware-mount/libvixMntapi.so.1.1.0', '--show-error', '--thumbprint', '94:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:10'
    2025-10-03T06:38:42.634Z <Manager_FQDN> NSX 2871320 - [nsx@6876 comp="nsx-manager" subcomp="curl_wrapper" username="uproton" level="INFO"] Trying (with httplib) <Manager_FQDN>:443...
    2025-10-03T06:38:42.636Z <Manager_FQDN> NSX 2871320 - [nsx@6876 comp="nsx-manager" subcomp="curl_wrapper" username="uproton" level="INFO"] Calling 'openssl', 's_client', '-showcerts', '-servername', '<Manager_FQDN>', '-connect', '<Manager_FQDN>:443'
    2025-10-03T06:38:42.489Z <Manager_FQDN> kernel - - - [9137205.246432] getrandom: Device open
    2025-10-03T06:38:42.496Z <Manager_FQDN> kernel - - - [9137205.252254] getrandom: Device close
    2025-10-03T06:38:42.506Z <Manager_FQDN> kernel - - - [9137205.254090] getrandom: Device open
    2025-10-03T06:38:42.657Z <Manager_FQDN> NSX 2871320 - [nsx@6876 comp="nsx-manager" subcomp="curl_wrapper" username="uproton" level="INFO"] certificate verification 94####################################################################a510 from <Manager_a_FQDN>:443 failed: SSL: no alternative certificate subject name matches target host name '<Manager_a_FQDN>'
    2025-10-03T06:38:42.657Z <Manager_FQDN> NSX 2871320 - [nsx@6876 comp="nsx-manager" subcomp="curl_wrapper" username="uproton" level="INFO"] Closing connection 0
    2025-10-03T06:38:42.657Z <Manager_FQDN> NSX 2871320 - [nsx@6876 comp="nsx-manager" subcomp="curl_wrapper" username="uproton" level="INFO"] /opt/vmware/nsx-common/python/nsx_utils/curl_wrapper exit code 51

Environment

VMware NSX
VMware NSX-T Data Center

Cause

The certificate common name (or Subject Alternative Name) applied to the node(s) is incorrect or may not be assigned to the specified FQDN of the Manager node(s).

Resolution

  • Correct the certificate so that the common name matches the FQDN applied to the node or there is a Subject Alternative Name entry with the FQDN.
  • Note: If the repo_sync is still in failed state, even after following the above steps, please refer the following documentation for alternate methods: After replacing Managers or while running Upgrade prechecks, Repo_Sync is Failed
  • Once repo_sync is successful then retry uploading of the .PUB file
    • Reboot of the manager is not required.

Additional Information

Powered by Wolken Software