The new VCC messaging structure no longer talks directly with the local browser. Instead it talks to the Manitou REST API using SignalR (websockets). This is the proper way for this messaging and uses the server certificate instead of hacky local workstation self-signed cert. BUT some customers still choose to use a self-signed cert on the server. This leads to the message saying it may not be secure, do you want to continue when accessed through the browser. This same thing happens but now in VCC where there is no user interface.
You will end up with a message like this.
To work around this, a parameter must be added when launching VCC. This is done in SWS under Subtypes.
