Hello,

Simulation Server’s certificate for opc.https connections is not self-signed, so you’ll have to trust the certification authority (CA) certificate that was used to sign it to in order to form a connection. At the moment this has to be done manually by copying SimulationServerCA.der from \.prosysopc\prosys-opc-ua-simulation-server\PKI\CA\private to \.prosysopc\prosys-opc-ua-browser\PKI\CA\certs, where is your home folder where .prosysopc folder is located. If you do not perform this step, you will see the menu appear again and again.

If you’re using 4.0.4-247 or a newer version of Browser, then there is a programming oversigth that prevents Browser from connecting to Simulation Server via opc.https. Newer versions of Browser require that a CA certificate provides a certificate revocation list (CRL) that can be used to check the revocation status of certificates they have signed. See the OPC UA Specification for more information on the topic (https://reference.opcfoundation.org/v104/Core/docs/Part4/6.1.3/). However, the CA certificate used by Simulation Server doesn’t provide a CRL, which results in all certificates signed by the CA being treated as invalid preventing Browser from connecting to Simulation Server via opc.https.

Upcoming versions of Browser shall no longer require CA certificates to provide CRLs. Since you also contacted us by email, I shall send you a download link to a beta build of Browser that contains this change. Let us know if that solves the issue you’re facing.