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

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

book

Article ID: 388706

calendar_today

Updated On:

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

 

 

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

To resolve the issue, you must exclude the destination vCenter Server Appliance (VCSA) from being routed through the proxy server.

Steps to Exclude the Destination VCSA from Proxy Routing:

  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.