vCloud Director 9 Tenant Portal will not load – Don’t forget to set your Public Addresses !

One issue you may run into deploying vCloud Director 8.20/9.0 is that the Tenant Portal will not load if you browse to it (https://<vcd>/tenant/orgname) with anything other than the Cell IP address. This will occur if you have not set the Public Endpoints (System > Administration  > Public Addresses) for the API Service to the DNS name of your Load Balancer VIP for vCloud Director.

The UI for the tenant portal is built using the VMWare Clarity project and the HTML5 client is making direct API calls to build the responses for the user. When the browser makes the requests to the vCloud API Service it includes a Request Header “Referer:” which is used by the API service when responding to requests.

If the vCloud Director configuration does not have the Public Addresses values set the browser sends a Referer header that is not recognized and you will end up with a blank page being returned. So if you intend to provide different URI endpoints for the vCloud Tenant Portal (eg. You may wish to direct customers to a new URL for using the Tenant Portal to avoid confusion with the Web Portal); make sure that you set the Tenant Portal URIs or it won’t work.

The 2 minute fix:

  1. Logon to the System VDC
  2. Select Administration > Public Addresses
  3. Set the values to the external URI of the deployment and click Apply

Immediately after the settings have been amended the Tenant Portal will begin to function as expected. 

One thought on “vCloud Director 9 Tenant Portal will not load – Don’t forget to set your Public Addresses !

Comments are closed.