Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

VIC Plugin Reports "Failed to verify the vic-machine server at endpoint" (67801)

Last Updated: 10/27/2020Categories: TroubleshootingTotal Views: 2637Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When using the VIC plugin a failure similar to below is shown.

Failed to verify the vic-machine server at endpoint https://<VIC_Applience_IP>:8443. Possible causes:
The VIC appliance VM is running, but unreachable due to network misconfiguration.
The VIC appliance VM is up, but the API endpoint is unreachable. Possible issues include, but are not limited to:
Network misconfiguration
Firewall rules
API endpoint is down
Your browser may be blocking the connection because of an untrusted certificate. View API directly in your browser to see if any warnings are presented.

Resolution

The message most commonly occurs when the local browser is not trusting the VIC Appliance when connections are made by IP. Other causes include if the VIC Appliance is not running or responding.

Replace the VIC Appliance certificate with a certificate that has the VIC Appliance IP in the Subject Alternative Name. The VIC Appliance certificates are added from the vApp options of the VIC Appliance. See the documentation for more details. Deploy the vSphere Integrated Containers Appliance Step 4

Future versions of the VIC plugin will use FQDN if it is available. Details on Github.

Workaround

Click on the View API directly in your browser link. Alternatively, navigate to https://<VIC_Appliance_IP>:8443/container/hello in a new tab. Note: It is important to use IP not FQDN.

When warned that the connection is unsafe or that "Your connection is not private" click through the warning to add an exception to the browser.

The web page should say "You have successfully accessed the VCH Management API."

Go back to the VIC Plugin and click refresh and the plugin should be able to verify the API endpoint and proceed.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Integrated Containers

VMware vSphere

Related Versions:

VMware vSphere Integrated Containers 1.5.x

VMware vSphere Integrated Containers 1.4.x

Take Our Survey

Support Assistant