Hi,

Do you have another URL under the certificate that can be used instead of the current one? I say this because, many times we can have an SAN certificate that have many domains and sub-domains, but only one is configured in the environment to be the primary one (I have a case in Cloud that we have the same problem and changed the URL for Integration Studio to the one configured as primary for the environment and it worked). 

I don't know if this can solve your problem, but, maybe you can take a look and try if possible.

Hope this can help you.

Best regards,

Ricardo Pereira

I'm also facing the same issue as Rossi.

My installation is on-premise in a hyper-v VM.

There's also an AD VM with a CA installed and it signs the certificate used for SSL.

My host computer is not joined to the AD VM but is able to access the service center and the SSL is verified and valid.

However, the service studio (11.14.12) throws the same warning as Rossi has provided but is able to connect.

The latest integration studio (11.14.12) throws the SSL error.

Attached is the log and the screenshot is below:

I've contacted outsystems on the issue.

They're troubleshooting the issue but provided a workaround to my current version (11.14.12) of integration studio. Basically add ":80" without the quotes to your url to force it to http.

It'll give the insecure prompt and then integration studio should load.