-
I get the message, “Cannot Connect” when attempting to access the station from the browser.
Make sure that:
-
You’re using the correct IP address.
-
The JACE license has been updated.
-
CryptoService is installed in the Services node of the station Nav tree.
-
WebService is correctly configured (Https Enabled is set to
true)
-
-
My browser pops up the following certificate error.
The Tridium certificate, which is valid through 2054, is self-signed and the browser cannot validate its authenticity with a trusted root certificate. Some browsers will let you add the certificate so that you don’t see this message again. Other browsers will not, and you will see it every time.
-
My station is unable to start the HTTPS service.
The Key and Trust Store properties may be different. For CryptoService, the same file (default name: ssl.tks) is used for both the Key and Trust Stores. This includes the password defined for the Trust Store, which must be the same as that defined for the Key Store. If you are creating your own server certificates, make sure the Trust Store properties match their analogs for the key store. See Configure the CryptoService.
-
I get the following message when I try to start the HTTPS web service.
The private key password in the Key Store has a different password from the Key Store itself. These passwords must be identical. To set this password using the Keytool utility, see Import, verify and edit the Key Store.
