From: Peter J. Holzer <hjp-pgsql@hjp.at>
To: pgsql-general@lists.postgresql.org
Subject: Re: Having issue with SSL.
Date: Fri, 26 May 2023 12:17:14 +0200
Message-ID: <20230526101714.v7ffvr2clz35c4de@hjp.at> (raw)
In-Reply-To: <BYAPR07MB544877479FEC89102CFE9DBCA4419@BYAPR07MB5448.namprd07.prod.outlook.com>
References: <BYAPR07MB544877479FEC89102CFE9DBCA4419@BYAPR07MB5448.namprd07.prod.outlook.com>
On 2023-05-24 21:02:04 +0000, Randy Needham wrote:
> The problem I am running into is my remote client can't connect via SSL to
> postgrsql. I am able to from the server itself. This is using pgAdmin 4 and
> making ssl mode as required. Also ran psql.exe on the server to show that SSL
> was in fact working on the server. "SSL connection (protocol: TLSv1.3, cipher:
> TLS_AES_256_GCM_SHA384, bits: 256, compression: off)". In the logs it is
> showing this when I try to connect via my remote client.
>
> [2672] LOG: could not accept SSL connection: An existing connection was
> forcibly closed by the remote host.
>
> The error from pgAdmin 4 on the remote client is this.
>
> connection failed: server closed the connection unexpectedly This probably
> means the server terminated abnormally before or while processing the request.
> SSL SYSCALL error: Connection reset by peer (0x00002746/100054)
So both the server and the client claim that the connection was
terminated by the other side?
I suspect that the server and client cannot agree on a common cypher.
But if both are reasonably up to date that shouldn't happen (it can
happen if the SSL library on your server is much older than that on your
client or vice versa).
Can you use wireshark (or something similar) to record the session and
see where in the protocol they give up?
hp
--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp@hjp.at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: hjp-pgsql@hjp.at
Subject: Re: Having issue with SSL.
In-Reply-To: <20230526101714.v7ffvr2clz35c4de@hjp.at>
References: <BYAPR07MB544877479FEC89102CFE9DBCA4419@BYAPR07MB5448.namprd07.prod.outlook.com> <20230526101714.v7ffvr2clz35c4de@hjp.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox