Error: "Failed to Start" after updating Public Addresses or Ciphers in VCD
search cancel

Error: "Failed to Start" after updating Public Addresses or Ciphers in VCD

book

Article ID: 325173

calendar_today

Updated On:

Products

VMware Cloud Director VMware Telco Cloud Platform

Issue/Introduction

  • Navigating to the VCD provider UI prompts for login normally but fails with the error
    • Failed to Start: An error occurred during the initialization. Accessing the application through an unsupported public URL or poor connectivity might cause this error.
  • Issue occurs after modifying or populating Public Addresses and Cipher settings.
  • Standard URL checks succeed, but application initialization fails.

Environment

  • VCD: 10.x
  • TCP: 3, 4.x, 4.0.1, 5.x, 5.0, 5.0.1, 5.0.2

Cause

  • An uncaught typo or case-sensitivity mismatch in public address settings causes the configured address string to misalign with the webapp.allowed.origins property list or the actual client request origin.
  • VCD uses a Cross-Origin Resource Sharing (CORS) filter to maintain and validate all allowed endpoints.
  • Because CORS origin validation logic is strictly case-sensitive, for example https://vcd1.vcloud.local vs https://VCD1.vcloud.local, any casing discrepancy or missing entry in the allowed origins list triggers a security block that prevents application initialization.

Resolution

  1. Take a full database and appliance backup of the VCD environment before making configuration changes.
  2. Examine and validate all relevant configuration property values:
    • restapi.baseHttpUri
    • restapi.baseUri
    • ui.baseHttpUri
    • ui.baseUri
    • consoleproxy.external.address
    • webapp.allowed.origins

For VCD 10.2.x and earlier:

  1. Query current property values directly via this database query:
    • select name,value from config where name in ('restapi.baseHttpUri','restapi.baseUri','ui.baseHttpUri','ui.baseUri','consoleproxy.external.address','webapp.allowed.origins');
  2. View individual property values using the cell management tool:
    • /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n ui.baseUri -l
  3. Update incorrect property values using the cell management tool, ensuring entry casing matches client request origins exactly:
    • /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n ui.baseUri -v "https://####################"

 

For VCD 10.3 and later:

  1. Query current CORS settings via API Explorer by browsing to:
    • https://####################/api-explorer/provider/#/cors
  2. Click Try it out, then click Execute.
  3. Update CORS settings via API Explorer by browsing to:
    • https://####################/api-explorer/provider/#/cors
  4. Click Try it out
  5. Paste the updated values into the allowedOrigins field ensuring casing matches client request origins exactly
  6. Click Execute.

Contact Broadcom Support for further assistance.

Additional Information

Configure CORS for VMware Cloud Director

Powered by Wolken Software