VMware Cloud Director portal fails to load via Load Balancer FQDN while direct Cell access works

Products

• VMware Cloud Director

Issue/Introduction

• Users are unable to access the VMware Cloud Director (VCD) tenant or provider portal when using the configured Load Balancer (LB) FQDN. Symptoms include:
• Browser timeouts or "Site cannot be reached" errors when using the LB URL.
• Direct access to a VCD Cell IP/FQDN may show the login page, but login fails or redirects to the broken LB URL.
• The Load Balancer Virtual IP (VIP) does not respond to ICMP echo requests (ping).

Environment

10.x

Cause

The Load Balancer appliance or virtual machine is in a 'Powered Off' state or has lost network connectivity. Because VCD is configured with Public Addresses, the application logic generates absolute redirects to the LB FQDN. If the LB is offline, the client browser cannot follow these redirects, even if the underlying VCD Cells are functional.

Resolution

 

• Validate Connectivity: * Attempt to ping the Load Balancer VIP from a client machine.

  • If no response, attempt to ping the LB management IP.

• Verify Power State:

  • Log into the vCenter Server managing the management/edge cluster.

  • Locate the Load Balancer VM(s).

  • If the state is Powered Off, right-click the VM and select Power > Power On.

• Verify Service Health:

  • Once the LB is powered on, log into the LB management interface (e.g., Avi Controller or NSX Manager).

  • Ensure the Virtual Service is "Green" or "Up" and that the Pool Members (VCD Cells) are passing health checks.

• Test Access:

  • Clear browser cache or use an Incognito window to test access via the LB FQDN.

 

Additional Information

For more information on configuring Public URLs, see the VMware Cloud Director Documentation.