SH Integration runtime

Question

In my scans from Purview seeing errors

Code: InternalError, Error Message: The SSL connection could not be established, see inner exception.

Answer 1

The error message you are encountering, "The SSL connection could not be established, see inner exception," typically indicates that there is an issue with the SSL/TLS certificate validation during the connection process. This can occur for a couple of reasons:

1. Untrusted Certificate: The root CA of the service's server certificate may not be trusted on the machine where the self-hosted integration runtime (SHIR) is installed. Ensure that the service's server certificate and its certificate chain are trusted by the machine.
2. Proxy Issues: If you are using a proxy, it might be replacing the server's SSL certificate with its own, which may not be trusted by your machine. In this case, you can either trust the replaced root CA on the SHIR machine or configure the proxy not to replace the service's server certificate.

To resolve this issue, you can check the server certificate by opening the service URL in your browser and viewing the server certificate information. Additionally, ensure that the DigiCert Global Root G2 is in the trusted root CA list on your machine, as it is the new SSL certificate being used.

If the problem persists, you may need to consult your network team to troubleshoot any potential network settings or firewall rules that could be affecting the connection.

Answer 2

Hi @kumarlankada

Thank you for reaching out to Microsoft Q&A. Here are the detailed mitigation steps you can try to resolve your issue:

It looks like you’re running into an SSL connection error while working with Azure Purview. The message “The SSL connection could not be established” usually points to a problem with either your network setup or the SSL certificates in use.

Here are a few practical steps you can take to troubleshoot:

Check your network settings: Make sure your network allows SSL traffic. If you’re using a self-hosted integration runtime, confirm it’s configured correctly and can reach the required endpoints.

Validate SSL certificates: Ensure the certificates are valid and trusted. If you’re using self-signed certificates, double-check that they’re installed properly on both the client and server.

Test connectivity: Try using tools like curl or Postman to manually test the endpoint. This helps you figure out whether the issue is specific to Azure Purview or something broader in your network.

Review integration runtime settings: If you’re on a self-hosted runtime, verify its configuration. Make sure it has the right permissions and isn’t being blocked by firewall rules.

Check the logs: Logs often provide detailed error messages that can give you clues about why the SSL handshake is failing.

Answer 3

It was an issue with Purview accounts across multiple regions. Once that was fixed, issue is good. not a SHIR issue