How to fix 'Could not establish trust relationship for the SSL/TLS secure channel'

DM 546 Reputation points
2023-05-10T19:25:06.0666667+00:00

We are trying to generate a communication with regulator body server for some specific valid business process. It happens on one of the server; however on other server it prompts message that 'The underlying connection was closed. Could not establish trust relationship for the SSL/TLS secure channel'. We tried by checking fire wall settings/antivirus disabled and checked/windows rights/dot net framework etc checked however solution not in sight. OS on both servers is Windows Server 2012. Suggest please. Thanks.

Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} vote

Accepted answer
  1. Limitless Technology 44,771 Reputation points
    2023-05-18T13:20:12.54+00:00

    Hello,

    Here are the main causes of the “Could not establish trust relationship for the SSL/TLS Secure Channel with Authority” message:

    -Self-signed certificates: These certificates are often generated for free. However, they don’t provide as much trust as commercial certificates.

    -Expired certificates: Most SSL certificates are only valid for a year. Therefore, you’ll need to renew your certificate as it nears its expiration date.

    -Certificates not signed by a trusted Certificate Authority (CA): Like self-signed certificates, a lesser-known certificate provider might not be trusted by every browser.

    -Free SSL certificates: There are a few free CAs, but sometimes their root certificates must be manually imported into your browser to clear the error.

    -Certificates that are missing a chain/intermediate certificate: Most trusted certificates ask you to install at least one other chain/intermediate certificate to link your SSL certificate to a trusted source. However, this process depends on the browser you use. For example, Internet Explorer can automatically download intermediate certificates, but Mozilla Firefox can’t.

    All in all, try to access the same address in a browser suing the HTTPS:// prefix in order to show the certificate validity, then depending on your browser click on the "padlock" symbol next to the URL and go to "More Information" or "Certificate Information" in order to find which of the previous causes may be applying here.

    Also, ensure that you are using TLS 1.1 and 1.2, since most of the secure connection services will require this level of encryption in order to allow the communication. TLS 1.0 is considered highly vulnerable and therefor rejected by default.

    You can check TLS 1.2 enablement in the registry on Windows 2012 and 2012R2 as:

    -Press the Windows key + R to start Run, type regedit, and press Enter or click OK.

    -Now go to the following key and check it. If it’s present, the value should be 0:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client\DisabledByDefault

    -Also, check the following key. If you find it, its value should be 1:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client\Enabled

    -If you can’t find any of the keys or if their values are not correct, then TLS 1.2 is not enabled.

    --If the reply is helpful, please Upvote and Accept as answer--

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.