vCenter Sever 8.0U1 or above does not load vCenter Details on the Summary Page of the vSphere UI
search cancel

vCenter Sever 8.0U1 or above does not load vCenter Details on the Summary Page of the vSphere UI

book

Article ID: 335189

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

This is a Workaround For vCenter Server 8.0U1 or above Summary Loading issue in the vSphere UI when the vCenter does not have access to the internet or a configured Proxy.

 


Symptoms:

In vCenter Server 8.0U1 or above, the vCenter Details pane is blank on the Summary tab.

Environment

VMware vCenter Server 8.0U1 or above.

Cause

A vCenter Server which was recently been updated to 8.0U1 or above is loading the vCenter Details pane on the vCenter Summary tab very slowly. While watching the page load in the browser developer tools, we noticed that an 'apigw' call is erroring out after about 6 minutes with an error that says, "Configured repository is not accessible due to network connectivity or incorrect URL."

 

A timeout occurs in the API loading the vCenter Details pane when the vCenter does not have internet access.

Resolution

Pending Resolution


Workaround:

Update Settings from VAMI shows the default repository URL, which the vCenter cannot access.

 

Follow the steps shared below to make the suggested changes.

  • Connected to the vCenter Server Management Interface (VAMI)
  • Click "Update"
  • Click "Settings" to update the configuration
  • In "Update Settings", go to "Repository Settings" > URL > Specified.
  • Provide a custom (dummy) repository URL:
    • Suggested: https://<vCenter_FQDN>
  • Click Save.

Note: If the URL is https://vCenter_FQDN, vCenter summary pane loads more quickly.

 

 

Once this is setting is saved, the vCenter Details pane on the Summary page should load successfully.



 

 

 

 

 

 

 

Additional Information

This Workaround is only applicable when the VC doesn't have internet access and the customer is not willing to use the online repositories to update the VC.

For other scenarios, make sure to grant the proper internet access to vCenter's default URL repositories directly or through a Proxy configuration.