Configuring the content library on vCenter 9.0 using an External Subscription URL requiring proxy throws error: The remote library is not reachable

Products

• VMware vSphere ESXi

Issue/Introduction

• Proxy is configured correctly in VAMI for both HTTP and  HTTPS
• Access to remote subscription URL to be subscribed is enabled only through proxy
• When configuring the subscribed content library with external remote URL needing proxy (say wp-content.broadcom.com) there is an error: The remote library is not reachable

• Messages similar to the following might be seen in /var/log/vmware/content-library/cls.log.

2025-08-18T13:14:55.138Z | DEBUG    | meh4xitd-392-auto-ax-h5:70000146 | proxy-vapi-config--executor-53 | JsonApiProvider                | Sending request of size: 381
2025-08-18T13:14:55.138Z | DEBUG    | meh4xitd-392-auto-ax-h5:70000146 | proxy-vapi-config--executor-53 | HttpClient                     | Value of uri is:http://localhost:/site/api
2025-08-18T13:14:55.138Z | ERROR    | meh4xitd-392-auto-ax-h5:70000146 | tomcat-http-30            | CachedProxyService             | failed to get
2025-08-18T13:14:55.138Z | DEBUG    | meh4xitd-392-auto-ax-h5:70000146 | tomcat-http-30            | ApplianceProxySettings         | Proxy is not enabled / config is null
2025-08-18T13:14:55.139Z | DEBUG    | meh4xitd-392-auto-ax-h5:70000146 | proxy-vapi-config--executor-54 | JsonApiProvider 

Environment

VMware vCenter Server 9.0

Cause

A race condition is happening in the code where the result of the proxy API is being fetched before the callback has been received. This is leading to an exception and content library is not being able to recognize the configured proxy and noProxy details.

Resolution

This is a known issue in content library; fix will be available in 9.0.1 patch.

To work around thi issue use below guide as to download content from remote URL locally and import to local library for tkg images cluster provisioning.

Create a Local Content Library (for Air-Gapped Cluster Provisioning)