Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"Failed to Start: An error occurred during the initialization" error when trying to access vCloud Director after updating public addresses (79183)

Last Updated: 7/5/2023Categories: TroubleshootingTotal Views: 16970Language:
English

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Symptoms

You noticed the issue after filling out or modifying your Public Addresses settings.

When trying to access your vCloud Director instance at the <IP address>/provider/ or <FQDN>/provider/ it prompts you to login normally, but it then presents you with the following 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."

You have already verified that "Failed Start: An error occurred during initialization" error while accessing the vCloud Director H5 provider and tenant UI (75305) did not resolve the problem and that your ip addresses and URL for your cells is correct and does not include any typos for the webapp.allowed.origins property.

Cause

The most common cause for this issue is that there was an uncaught typo in your public addresses resulting in an address that does not match the webapp.allowed.origins properties or any correct/resolvable IP or URL.

A common typo may be a missing the '.' character in one of the address fields, in which case listing the value for that property may show us that our URL is something like 'https://vcd1vcloud.local' instead of the intended 'https://vcd1.vcloud.local'

Resolution

To resolve this issue we must validate all of the relevant config property values to ensure the addresses are correct, resolvable, and included in the webapp.allowed.origins property as per "Failed Start: An error occurred during initialization" error while accessing the vCloud Director H5 provider and tenant UI (75305).

The relevant property values we should examine are:

restapi.baseHttpUri

restapi.baseUri

ui.baseHttpUri

ui.baseUri

consoleproxy.external.address

webapp.allowed.origins

For vCloud Director versions 10.2.x and earlier:

List values via direct database query

If you are comfortable accessing your associated database we can find those values with the following query:

select name,value from config where name in ('restapi.baseHttpUri','restapi.baseUri','ui.baseHttpUri','ui.baseUri','consoleproxy.external.address','webapp.allowed.origins');

This will return the values for all of the relevant properties.

List properties individually via Cell Management Tool

Alternatively, we can view the values for any of those individual properties via the cell management tool with the following command:

/opt/vmware/vcloud-director/bin]#./cell-management-tool manage-config -n <config-property-name> -l

For example:

/opt/vmware/vcloud-director/bin]#./cell-management-tool manage-config -n ui.baseUri -l

This will return the value for the ui.baseUri property.

Update and correct config property values

Once we have identified the property that is incorrect we can update it via the cell management tool with the following command:

/opt/vmware/vcloud-director/bin]#./cell-management-tool manage-config -n ui.baseUri -v "<property-value>"

This will update the ui.baseUri property.

For example:

/opt/vmware/vcloud-director/bin]#./cell-management-tool manage-config -n ui.baseUri -v "https://vcd1.vcloud.local"

This will update the ui.baseUri property to be "https://vcd1.vcloud.local"

After updating a value, it is a good idea to list the property again to ensure that the change was applied as intended.

Continue through the list of properties until all properties have been validated and corrected as needed.
Once this has been done for all of the listed properties you will be able to again login to your vCloud Director instance normally and will have corrected the "Failed to Start" error.

For vCloud Director versions 10.3 and later :

For vCloud Director 10.3 and later, the cell-management-tool options above do not work. The easiest way to query and modify is by using API Explorer.

To query current values :

Browse to :
https://<publicURL>/api-explorer/provider#/cors/queryAllowedOrigins

Click "Try it out" , then click on Execute to get the current settings

To modify :

Browse to :

https://<publicURL>/api-explorer/provider#/cors/setAllowedOrigins

Click "Try it out"

Make any modifications to the values from above query, paste it in the "allowedOrigins" field, then click on Execute

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Workspace ONE Content 3.22.1 for Android リリースのお知らせ (79224)

KB
•
VMware Intelligent Hub 20.04.1 for iOS リリースのお知らせ (79195)

KB
•
CRSVC-11528：「デバイス削除」などのデバイス管理操作が断続的に失敗する (79114)

KB
•
Workspace ONE SDK 20.4 for Android リリースのお知らせ (79124)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Director

Related Versions:

VMware Cloud Director 10.x

Take Our Survey

Support Assistant