Plug-in registration successful but icons do not appear in web client

Description

Registration shows as successful, but the plug-in icons are not visible from the vSphere Web Client.

Corrective action
  • Log out of the vSphere Web Client and log in again. Closing and re-opening your browser may be required.
  • Clear your browser cache.
  • From vCenter, restart the vSphere Web Client Service from the Services menu within Windows Administrative Tools or reboot vCenter.
  • Ensure that you have all required default administrative privileges associated with the vCenter Administrator role.
  • Check that the plug-in ZIP file successfully downloaded to vCenter:
    1. Open vsphere_client_virgo.log in the vCenter. vCenter log files for versions 6.5 and 6.7 are in the following locations:
      • Flash installations: /var/log/vmware/vsphere-client/log/vsphere_client_virgo.log
      • HTML5 installations: /var/log/vmware/vsphere-ui/log/vsphere_client_virgo.log
    2. If a failure message indicates that the ZIP download failed, download the ZIP again.
    Note: You might need to correct an unreachable or bad URL. Update the plug-in registration or unregister and register the plug-in again with a corrected URL. Failure to download the ZIP can also occur if you specified an HTTP URL without changing the allowHTTP setting.
  • Verify networking ports. Ensure the management node is reachable from vCenter bidirectionally on the required ports.
  • Check the vCenter’s MOB extension record (https://<vcenterIP>/mob/?moid=ExtensionManager&doPath=extensionList%5b%22com%2esolidfire%22%5d%2eserver) that contains the download location URL for the plug-in ZIP:
    1. Paste the URL into a browser.
    2. Verify that the plug-in ZIP can be downloaded.
      • If the plug-in ZIP can be downloaded, proceed to the next step.
      • If the plug-in ZIP cannot be downloaded, check for networking issues between vCenter Server and the management node.
    3. If the plug-in cannot be downloaded, compare the serverThumbprint in the MOB record with the certificate SHA-1 for the ZIP URL that is displayed in the browser:
      1. If the registration record in the MOB has an incorrect or stale URL or SHA-1, unregister the plug-in and register the plug-in again.
      2. If the problem persists and the ZIP is unreachable, inspect the ZIP URL to determine if there is an issue with the management node address used. In some cases, it might be necessary to customize a URL using the registration utility for the plug-in so that the ZIP file can be downloaded.