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 1r5q2f-00FLFi-EO for pgsql-general@arkaria.postgresql.org; Wed, 22 Nov 2023 16:25:33 +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 1r5q2e-00Afq2-1h for pgsql-general@arkaria.postgresql.org; Wed, 22 Nov 2023 16:25:32 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r5q2d-00Afog-3u for pgsql-general@lists.postgresql.org; Wed, 22 Nov 2023 16:25:31 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r5q2Y-006pky-Ru for pgsql-general@lists.postgresql.org; Wed, 22 Nov 2023 16:25:28 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 4FD253200A22; Wed, 22 Nov 2023 11:25:25 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 22 Nov 2023 11:25:25 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1700670324; x=1700756724; bh=El2DeAWrEBY9yOylEibCfnOy4KsBdwG+8wm YTqiHtso=; b=c6VRTdTpoup75w5C80ZOa0dtKi2tZkF7y/ruBJ5ZJYzn4mhxf9g tZRNinD1HNRlP2sQ3RvFFjhX24BPZrgKFNkQfgkTBsgkgjQoRtTGBQcTjzm8v23U Lwt0IMWxSdebMcwDlhaoAE0MBzpdgoaIvtG75FJgE0A3uT8UesELadPdSELlPwQd e9gqXhwaTgl1bxA3NvjF/SP3dRxr2P4fRZZqUVnOKQ4m4P34lHXiTKMBZh6ZmVwu LxkxKblSg1Wawwj3l1jlQcoW6atPlGFQS+x+BpzL0lR+fOuy0lK261QXhcowQeUR P0JzV6fQELSQe+m5x1rTHb3I52ponGitmAw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1700670324; x= 1700756724; bh=El2DeAWrEBY9yOylEibCfnOy4KsBdwG+8wmYTqiHtso=; b=G A9zPZ7iRmTir54yrnpPNUJlvqgjt3xobgL/NkQvMAMkOK5NUIGQ1OA5h56idkYFI ylPmuCK2PwcwLz/RZNWeEhlNi2sDq2Y7QFwpIdmnwbceQQT68hc7uPu11ZCI5a6h fRZ6XMpZqpuclyQCKQfIpWiKo25oyyuSSLH3tmV2ta8Vm8U0kwIY1itZRiKqEVrn K/xeePyLl+uRclzHp4ATYe1J6Qjohtd24NvEL/yDmqEJI2IuShb88sIj3Ea7dGlb A72bUnMY4sNM5S59bHVCHkzUkABKyPzenzGfAriqgeEkzKMwBvTkUKnScsg24CRx IlXgYeGtR/r/SqJ/efYFA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudehuddgkeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeeitdeutedvfedtleffveeuteejgedvvdevfeejtedt teegteffveekhfdtvdejjeenucffohhmrghinhepuddvjedrtddrtddrudenucevlhhush htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhl rghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 22 Nov 2023 11:25:24 -0500 (EST) Message-ID: <947a953a-e2ab-497e-9381-6abaf0796560@aklaver.com> Date: Wed, 22 Nov 2023 08:25:23 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: strange behavior of pg_hba.conf file To: Atul Kumar , pgsql-general References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/22/23 08:21, Atul Kumar wrote: > Hi, > > I have postgres 12 running in centos 7, recently I changed the > authentication of entries of pg_hba.conf to scram-sh-256 for localhost. > > Since then I have started getting the below error: > > no pg_hba.conf entry for host "::1", user "postgres", database "postgres The host is ::1 which IPv6 and your pg_hba.conf entry below is for IPv4. You need to add IPv6 line. > > > > > The entry of pg_hba.conf is like below: > > # TYPE  DATABASE USER ADDRESS METHOD > > # "local" is for Unix domain socket connections only > > local all all                                          scram-sha-256 > > # IPv4 local connections: > > host all postgres 127.0.0.1/32 scram-sha-256 > > > > What I am missing here, please suggest. > > > > > Regards, > > Atul > -- Adrian Klaver adrian.klaver@aklaver.com