Unable to view dashboard via plugin when logging to vCenter 8.0
search cancel

Unable to view dashboard via plugin when logging to vCenter 8.0

book

Article ID: 321626

calendar_today

Updated On: 04-29-2025

Products

VMware HCX VMware Cloud on AWS

Issue/Introduction

This document is created as a reference for the HCX vSphere Web Client plug-in post vCenter 8.0 upgrade.

Symptoms:
HCX plugin will not load in vCenter UI post 8.0 upgrade.



Impression:

  • User will get HCX option under vCenter plugin section but the HCX logo will remain hidden.
  • Upon clicking HCX button under plugin, the content will remain empty.



Cause

This may happen in two possible scenarios:

Case 1:
HCX plugin is now supported as a remote plugin from vCenter 8.0.0 onwards and if user is unable to resolve secondary hostname used for vCenter plugin isolation that is "vcenter-plugins.xxxx.com"  in that case the HCX plugin UI does not load from the browser.
Note: Starting from vCenter 8.0.0, vSphere Client Local plugins are deprecated. Refer to 87880.

Case 2:
We have also identified that the "index.html" page for HCX plugin could be opened in a new browser tab but it could not be loaded in the plugin "Iframe" hosted in the vSphere UI page.
In this case, the vSphere UI content is loaded from "https://vcenter.xxxx.com/" whereas the HCX "index.html" page is loaded from "https://vcenter-plugins.xxxx.com/", which prevents the browser from displaying the HCX plugin "Iframe" content inside the vSphere UI.

Resolution

This issue is fixed in HCX 4.6.1 release.

Workaround:
For case 2 only: User can open a Service Request with VMware Global Support Services and include the required information to work on remediation if running HCX 4.5.0.
Alternatively, users are also recommended to view HCX dashboard using HCX hybridity Standalone(443) UI for all versions and continue with the operations.

Additional Information

Impact/Risks:
  • Due to absence of HCX vSphere Web Client plugin, HCX hybridity UI will not be accessible from vCenter. However, it will NOT impact HCX hybridity Standalone(443) UI.
  • This behavior will be seen for all HCX versions registered with vCenter 8.0.0.
  • No impact in any HCX workflows and functionality.