You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Received unknown response E for SSLRequest (expecting S or N) #6600
Could this happen during negatiation?
Using Npgsql 10.0.2, the connectionstring has no ssl settings, so using the default, which is Prefer (I think)
PostgreSQL server is 18.3
Ugh. Technically, it doesn't make much sense because E means that the server sent us an error instead of the expected S (server supports SSL) or N (server doesn't support SSL), as in, if you don't support SSL, then just send N, no reason to actually try and complain about it. But the docs do specify that the server is allowed to send E and in that case we can retry without SSL.
Guess we'll just relax the catch block and retry even if we failed before establishing SSL connection, similar to GSS encryption.
Activity
vonzshik commentedon Jun 9, 2026
Ugh. Technically, it doesn't make much sense because
Emeans that the server sent us an error instead of the expectedS(server supports SSL) orN(server doesn't support SSL), as in, if you don't support SSL, then just sendN, no reason to actually try and complain about it. But the docs do specify that the server is allowed to sendEand in that case we can retry without SSL.Guess we'll just relax the catch block and retry even if we failed before establishing SSL connection, similar to GSS encryption.