Using Encrypt=Yes in a SQL Server Connection String -> "Provider: Ssl Provider, Error: 0 - the Certificate's Cn Name Does Not Match the Passed Value."

Microsoft SQL Azure Connection Type failing with TrustServerCertificate=False from MS SQL Report builder

As mentioned here you can set TrustServerCertificate=True, setting it to False is just more secure and should help prevent man-in-the-middle attacks. If you set TrustServerCertificate to false then the Encrypt setting should be set to True, but sometimes it does not work due to non-IFS LSPs installed on your computer as explained here.

A connection was successfully established with the server, but then an error occurred during the pre-login handshake

Solution

1) Clean your VS.Net Solution

2) Rebuild Project.

3) Reset IIS

4) Run the project again.

Basically that solved my problem, but in my case i was not getting this error and suddenly my local environment starts giving me above error, so may be that trick work for me.

https sql server connection

SQL Server does not connect via HTTP, and not via HTTPS as well. In other words, you are using the wrong syntax here.

Have you enabled SSL encryption for your SQL Server? This link tells you how its done: How to enable SSL encryption for an instance of SQL Server by using Microsoft Management Console

Then, you use the Encrypt statement in the connection string:
Using Encrypt=yes in a Sql Server connection string -> "provider: SSL Provider, error: 0 - The certificate's CN name does not match the passed value."

Connect to MySQL using SSL in C#

OK, after some more searching I found the answer at How determine if using SSL in a MySql Connection?.

I had to add SSL Mode=Required instead of encrypt=true to the connection string:

var connection = new MySqlConnection("Data Source=127.0.0.1;Database=MyDb1;User Id=root;Password=blabla;SSL Mode=Required");

Now I'm getting a new error - MySql.Data.MySqlClient.MySqlException: “The host localhost does not support SSL connections.”, but I think I'll figure it out.

Postfix and OpenJDK 11: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)

After upgrading JavaMail from 1.4.7 to 1.6.2, the error is gone! I'm sure there are also other clients which use JavaMail 1.4.7 and which works. So there must also be another difference on that machine. However, now it works!