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.