Assuming all of the vRA services are running as expected and deploy.sh has finished successfully, noted at the end of
/var/log/deploy.log, vRA will only respond via an FQDN.
|Short Name||Fully Qualified Domain Name|
Additionally you may review
/var/log/deploy.log to confirm the FQDN
This is due to vRA’s use of SNI to route the request to the appropriate internal virtual server. With vRA’s multi tenancy ability this becomes a requirement. When Enabling Multi-Tenancy CNAME DNS Records are created for each tenant and all pointed at the vRA node/cluster lb. Having SNI setup in the vRA appliance allows it to respond to the request for each tenant by examining the fqdn the client browser requested. So, with out a FQDN being leveraged in the client browser the vRA appliance is un able to determine which internal virtual server the request should be routed too.