Unable to Connect Published URL from Subscribed Content Library of vCenter Server Error: "The Remote Library is Not Reachable"

Products

• VMware vCenter Server

Issue/Introduction

Subscribers to the vCenter Server content library may encounter an error when attempting to connect to the Publisher URL. The error message displayed is:
"The remote library is not reachable".

Environment

 

• VMware vCenter Server 8.x
• VMware vCenter Server 7.x
• VMware vCenter Server 9.x

Cause

The issue occurs when a proxy is enabled on the Source vCenter Server Appliance (VCSA), preventing the connection from reaching the destination vCenter Server.

Resolution

Exclude the destination vCenter Server Appliance (VCSA) from being routed through the proxy server using the following steps below:

vCenter 7.x and 8.x

1. SSH into the vCenter Server Appliance:

   • Open an SSH connection to the vCenter Server Appliance.
   • Log in as the root user.

2. Navigate to the Proxy Configuration Directory:

             cd /etc/sysconfig
   
   
3. Edit the Configuration File
   • Open the proxy configuration file using the vi editor

                   vi proxy

      4. Exclude the Destination VCSA from Proxy Routing:

• • Find the NO_PROXY option within the file.

  • Modify the NO_PROXY entry to include the Fully Qualified Domain Name (FQDN) and IP address of the destination vCenter Server Appliance.

  • Example syntax for the NO_PROXY setting:

    NO_PROXY="localhost, 127.0.0.1, vc.example.com, <ip-address>"

• • Ensure that you use a comma followed by a space to separate each entry.

       5. Save the Changes and Exit:

• • After making the necessary changes, save the file and exit the vi editor.

       6. Restart the vCenter Server Appliance (Optional):

• • To ensure the changes take effect, restart the vCenter Server Appliance, or simply test the connection again after applying the changes.

 

vCenter 9.x 

 

Update /var/lib/vmware-envoy-system-proxy/config.json file with the correct settings. Leave any irrelevant PROXY entries blank. Add comma-separated entries to the NO_PROXY line as needed.

Important: Do NOT update the /etc/sysconfig/proxy file.

 

{
    "http_proxy": {
        "scheme": "<the proxy url schema>",                                    // example: http
        "host": "<the proxy url host>",                                        // example: example.com, 123.123.123.123, subdomian.example.com
        "port": <port if any else null>,
        "username": "<username of the proxy credential if any else null>",
        "password": "<password of the proxy credential if any else null>"
    }, // if exists or null
    "https_proxy": {
        "scheme": "<the proxy url schema>",                                    // example: http, https
        "host": "<the proxy url host>",                                        // example: example.com, 123.123.123.123, subdomian.example.com
        "port": <port if any else null>,
        "username": "<username of the proxy credential if any else null>",
        "password": "<password of the proxy credential if any else null>"
    }, // if exists or null,
    "ftp_proxy": {
        "scheme": "<the proxy url schema>",                                    // example: ftp
        "host": "<the proxy url host>",                                        // example: example.com, 123.123.123.123, subdomian.example.com
        "port": <port if any else null>,
        "username": "<username of the proxy credential if any else null>",
        "password": "<password of the proxy credential if any else null>"
    }, // if exists or null
    "no_proxy": ["<comma separated values if any else leave as is>"]
}

 

If copied, ensure removal of '// example' sections and white space.

Service restart is not needed.

The above must be in valid JSON format