Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r0l8Q-007fTo-1Z for pgsql-general@arkaria.postgresql.org; Wed, 08 Nov 2023 16:10:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r0l8O-005h8q-Oo for pgsql-general@arkaria.postgresql.org; Wed, 08 Nov 2023 16:10:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r0l8O-005h8i-DZ for pgsql-general@lists.postgresql.org; Wed, 08 Nov 2023 16:10:28 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r0l8I-005NMC-5N for pgsql-general@lists.postgresql.org; Wed, 08 Nov 2023 16:10:27 +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 3A8GAKon685935; Wed, 8 Nov 2023 11:10:20 -0500 From: Tom Lane To: Johnathan Tiamoh cc: pgsql-general@lists.postgresql.org Subject: Re: PGE-XX000: ERROR: Problem with the SSL CA cert (path? access rights?) In-reply-to: References: Comments: In-reply-to Johnathan Tiamoh message dated "Wed, 08 Nov 2023 10:21:38 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <685933.1699459820.1@sss.pgh.pa.us> Date: Wed, 08 Nov 2023 11:10:20 -0500 Message-ID: <685934.1699459820@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Johnathan Tiamoh writes: > How can this error be resolved? > PGE-XX000: ERROR: Problem with the SSL CA cert (path? access rights?) > Is there any postgresql documentation on this ? No, because it's not a Postgres error: there is no such message string anywhere in our source code. You should start by trying to identify what component is actually throwing that error. regards, tom lane