Error: "No vCenters Found" when viewing vCenter Server Instances in VCD Provider Portal

Products

• VMware Cloud Director

Issue/Introduction

• The VMware Cloud Director (VCD) provider portal displays no infrastructure resources, vCenters, organizations, or certificates; the GUI shows "No vCenters Found."

• When connecting to VCD using PowerCLI, all expected resources are visible and accessible.
  Using:Connect-CIServer -Server <vcd-fqdn>
Get-Org
Get-ProviderVdc
Get-CIVM

• In browser Developer Tools the following may be observed: 
  
  Request URL: https://<vcd-FQDN>/cloudapi/1.0.0/orgs
  Status: 504
  Time: ~ 50,000ms

Environment

VMware Cloud Director 10.5.1.1

Cause

This issue can occur when the VCD cells are unable to resolve or connect to their own public FQDN (as used by the provider portal) due to internal DNS or load-balancer configuration.

If the cells cannot reach their own address often because hair-pin (U-turn) NAT or SNAT is not enabled, or internal DNS resolves to an unreachable address API calls within the cell hang for 50 seconds, resulting in blank grids and timeouts in the UI.

Resolution

1. Verify FQDN Resolution from Each Cell
   
   Log in to each Cloud Director cell and run:
   
   nslookup <vcd-public-fqdn>
   
   Ensure it resolves to the internal VIP used by the load-balancer (not a public/external IP).
   
   
2. Test HTTPS Connectivity from Each Cell
   
   Run the following from each cell:
   
   curl -k -m 3 https://<vcd-public-fqdn>/api/versions

If the command hangs or fails, the cell cannot loop back to itself through the load-balancer.
   
   
3. Add an entry to /etc/hosts on each cell:
   
   echo "<INTERNAL_VIP_IP> <vcd-public-fqdn>" >> /etc/hosts
   
   Retest with curl to confirm connectivity.
   
   

4. Restart One VCD Cell

   After applying the network fix, restart the VCD services on 1 cell:
   
   systemctl restart vmware-vcd



5. Wait one minute, then refresh the provider portal. Resources should appear as expected.