Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q2UVi-0007wf-Fr for pgsql-general@arkaria.postgresql.org; Fri, 26 May 2023 10:17:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q2UVh-0007Qu-A9 for pgsql-general@arkaria.postgresql.org; Fri, 26 May 2023 10:17:25 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q2UVg-0007Qj-V8 for pgsql-general@lists.postgresql.org; Fri, 26 May 2023 10:17:24 +0000 Received: from mail.hjp.at ([212.17.106.138] helo=rorschach.hjp.at) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q2UVZ-001ypE-Jg for pgsql-general@lists.postgresql.org; Fri, 26 May 2023 10:17:22 +0000 Received: by rorschach.hjp.at (Postfix, from userid 1000) id 4A08449355; Fri, 26 May 2023 12:17:14 +0200 (CEST) Date: Fri, 26 May 2023 12:17:14 +0200 From: "Peter J. Holzer" To: pgsql-general@lists.postgresql.org Subject: Re: Having issue with SSL. Message-ID: <20230526101714.v7ffvr2clz35c4de@hjp.at> Mail-Followup-To: pgsql-general@lists.postgresql.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="yob3xl6nb2nfkse3" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --yob3xl6nb2nfkse3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 tha= t SSL > was in fact working on the server. "SSL connection (protocol: TLSv1.3, ci= pher: > 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. >=20 > [2672] LOG: could not accept SSL connection: An existing connection was > forcibly closed by the remote host. >=20 > The error from pgAdmin 4 on the remote client is this. >=20 > connection failed: server closed the connection unexpectedly This probably > means the server terminated abnormally before or while processing the req= uest.=20 > 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 --=20 _ | Peter J. Holzer | Story must make more sense than reality. |_|_) | | | | | hjp@hjp.at | -- Charles Stross, "Creative writing __/ | http://www.hjp.at/ | challenge!" --yob3xl6nb2nfkse3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEETtJbRjyPwVTYGJ5k8g5IURL+KF0FAmRwhyQACgkQ8g5IURL+ KF0U5BAAnIFLy8tsLyhuVbnka0ho6xbNnGcYVihY93lK5lJh7UxA9NUmfLmpWqh6 Y+VovGivf2bMGcM3X8OU+/TtdCLG9pyoD7XZWDGcKmVh3n4KtULXD+yRMF6163og 40Hv0rKrBXHA7OikKEVvc8dNOkWFakr1hR7O7C4B/VnZvUWVDvko1sg/AIa6y0C9 R8sdStYQTy+M+HzXk0jYg3kKIYEQf1j7ZrSRxIcXA+qivo1IP7hvvuU76DORgSU2 d/U319DEDbbGAipE2VnD7SWnOEj+0OxSeCYP8TMDCEP9S92K5qxJTNiu5VwSJVLb YdFxkT97x5N32UaSJADFtqhVwB/ys5r5t2KxhJMYqFZKB+07RRMFF9OvMDg3Uk+s ThTK0evOCywqYAQ7AEYjIfdvWMSkK19m31Wi0W7ETWrmDLGRmgcNv6N0Tnq4/5c/ kREPbVbRKR8PpTqwR4z8Yf8dEHP5GX+JK+tPz0Y7QYrSLBkkAhRwt74TYI8exl28 PQUkAvcj3MP3FrsFBiL4ZLe3JDpveQQNIfeCaRpxKRqNWCGfnSAyH1YtFAFQ5c3+ o6AuIvZVDsWgUH39Z6rNHzB5austTFWqpSk9Xnq9qvq8vx2PtGprrJE/PpgaGtB7 Fgsn+9LdBNRddGeECKQ4UW5aXfkMw8uKO5hihWSiLTTdzLrNixI= =XSBD -----END PGP SIGNATURE----- --yob3xl6nb2nfkse3--