Exception while performing SSL handshake

Hi Deependra Singh •,

Welcome to Microsoft Q&A forum.

As I understand, you are trying to connect to to Azure Cosmos DB for PostgreSQL 16 with Citus 12 from Framework: .NET Core 3.1, and getting "Exception while performing SSL handshake" The message received was unexpected or badly formatted.

I am checking on this and will get back to you.

Thanks

Hi,

we have the same problem with Azure Cosmos DB for PostgreSQL. Two months ago we were creating other Azure Cosmos DB instances and they are running fine currently. A newly created instance a week ago shows the mentioned problems.

Specifications:

• Minimum TLS Version: 1.2
• Framework: .NET Core 8.0
• PostgreSQL version 16
• Citus version 12.1

Library

• Npgsql 8.0.3

Npgsql.EntityFrameworkCore.PostrgeSql 8.0.4

We tested different scenarios as the applications run side by side on the same server. That means, they also have the same TLS settings. We have currently revealed that applications running on Windows Server 2022 will connect to the new instance without issue. On older OS editions 2019, 2016, connecting to a new instance already shows problems with the SSL handshake. We also tried building an older version of PostgreSQL and the problem is still there. I remind, that connecting from the same server to instances created two months ago works normally.

Log:

Connection to first db Connection failed: Npgsql.NpgsqlException (0x80004005): Exception while performing SSL handshake  ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception.  ---> System.ComponentModel.Win32Exception (0x80090304): The Local Security Authority cannot be contacted    --- End of inner exception stack trace ---    at System.Net.Security.SslStream.ForceAuthenticationAsyncTIOAdapter    at System.Net.Security.SslStream.AuthenticateAsClient(SslClientAuthenticationOptions sslClientAuthenticationOptions)    at Npgsql.Internal.NpgsqlConnector.NegotiateEncryption(SslMode sslMode, NpgsqlTimeout timeout, Boolean async, Boolean isFirstAttempt)    at Npgsql.Internal.NpgsqlConnector.NegotiateEncryption(SslMode sslMode, NpgsqlTimeout timeout, Boolean async, Boolean isFirstAttempt)    at Npgsql.Internal.NpgsqlConnector.RawOpen(SslMode sslMode, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken, Boolean isFirstAttempt)    at Npgsql.Internal.NpgsqlConnector.<Open>g__OpenCore|213_1(NpgsqlConnector conn, SslMode sslMode, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken, Boolean isFirstAttempt)    at Npgsql.Internal.NpgsqlConnector.Open(NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)    at Npgsql.UnpooledDataSource.Get(NpgsqlConnection conn, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)    at Npgsql.NpgsqlConnection.<Open>g__OpenAsync|42_0(Boolean async, CancellationToken cancellationToken)    at Npgsql.NpgsqlConnection.Open()    at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenDbConnection(Boolean errorsExpected)    at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected)    at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)    at Npgsql.EntityFrameworkCore.PostgreSQL.Storage.Internal.NpgsqlDatabaseCreator.Exists(Boolean async, CancellationToken cancellationToken)    at Npgsql.EntityFrameworkCore.PostgreSQL.Storage.Internal.NpgsqlDatabaseCreator.Exists(Boolean async, CancellationToken cancellationToken)    at Npgsql.EntityFrameworkCore.PostgreSQL.Storage.Internal.NpgsqlDatabaseCreator.Exists()    at Microsoft.EntityFrameworkCore.Storage.RelationalDatabaseCreator.EnsureCreated()    at Microsoft.EntityFrameworkCore.Infrastructure.DatabaseFacade.EnsureCreated()    at db_tester.Program.CheckConnectionTContext Connection to second db Connection sucesss

Thank you.

.....

Hi Deependra Singh •,OndrejDanis •,

Just checking if you have checked the configurations mentioned in the previous comment.

If this does not work, I request you to please raise support case for deeper investigation of the issue.

Let us know if you need any help in doing the same.

Thanks

Hi ShaktiSingh-MSFT

We've reviewed the configurations as previous comment mentioned, and everything is set up correctly, but the issue persists.

We have another instance with the same configuration used in staging environment, running the same application code, and it works without any problems. We're unsure what's happening at the instance level on Azure.