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 1kpu8V-00064u-8w for pgsql-general@arkaria.postgresql.org; Thu, 17 Dec 2020 14:20:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kpu8U-0006hM-26 for pgsql-general@arkaria.postgresql.org; Thu, 17 Dec 2020 14:20:06 +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 1kpu8T-0006hF-QI for pgsql-general@lists.postgresql.org; Thu, 17 Dec 2020 14:20:05 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kpu8R-0005Se-No for pgsql-general@postgresql.org; Thu, 17 Dec 2020 14:20:04 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 0BHEK1cA065645; Thu, 17 Dec 2020 09:20:01 -0500 From: Tom Lane To: Gustavsson Mikael cc: Kyotaro Horiguchi , "pgsql-general@postgresql.org" , "Svensson Peter" Subject: Re: SV: Problem with ssl and psql in Postgresql 13 In-reply-to: <06191eae74d045e192a786a84a73ba53@smhi.se> References: ,<20201217.172938.170511532557914014.horikyota.ntt@gmail.com> <06191eae74d045e192a786a84a73ba53@smhi.se> Comments: In-reply-to Gustavsson Mikael message dated "Thu, 17 Dec 2020 09:11:13 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <65643.1608214801.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 17 Dec 2020 09:20:01 -0500 Message-ID: <65644.1608214801@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Gustavsson Mikael writes: > Clarification, its the same postgresql13 server. I just connect with dif= ferent psql-clients. Perhaps turning on log_connections on the server would offer some insight. It sort of looks like the v13 client is trying to connect with SSL, failing for some unknown reason, and falling back to non-SSL which also fails. regards, tom lane