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 1pr5hh-0006UJ-A0 for pgsql-general@arkaria.postgresql.org; Mon, 24 Apr 2023 23:34:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pr5hf-00062k-5w for pgsql-general@arkaria.postgresql.org; Mon, 24 Apr 2023 23:34:39 +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 1pr5hd-00062b-Vw for pgsql-general@lists.postgresql.org; Mon, 24 Apr 2023 23:34:38 +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 1pr5ha-001iDZ-3i for pgsql-general@lists.postgresql.org; Mon, 24 Apr 2023 23:34:36 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 9F891320069B; Mon, 24 Apr 2023 19:34:31 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 24 Apr 2023 19:34:31 -0400 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=fm2; t= 1682379271; x=1682465671; bh=A4RBsL4hxNS47nG5ofrG8AkID1jxjYk57mi g85zDkHs=; b=rQxxAJ0/fyqCo372jq8/CqYU7rrVX33sJO4q/3BS6mcXQUwSbme U2apKXkrqQLcSq6qPu42JRDBkN8NbQp2bHRcsPCZXLX9lLswyn8PGApnZtQS01se UyC9PCtl/ITlgkIFec03XYe+xZX0aeMxw/ntOy9t3I4+I4n4c0Wbha3Bgxm+2t7d rjfe0ftewGYokOi6v2xeZDKzH/lRrniCXdvu313j/KJh2rzO7cwoBiNJjsZUacEM PnfdFIO4K0n83U1jTGdZ4YD/AXcJAL9o/wejxbilcxA3oVPg6w5K03gYTIChwvob Qjt0ati+aa1NxHEBolaHCfDx2yDQ2N6Vjyw== 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=fm3; t=1682379271; x= 1682465671; bh=A4RBsL4hxNS47nG5ofrG8AkID1jxjYk57mig85zDkHs=; b=i t4tIZ7UmphFAtQ3E5lcIUCC22h526tZMJgYnWlXGVSm2UDEgeknV7hG5pxoEfOqW 53zkwlAK/NyZPsYkk5v7d8AedVQPKB+KO4ETeyROpDELpOOMHTv3f8f+D1Iajc6U wdYWVhYkg9BnXMU+Qaj8ryxesd3yoPaK+DLayK9H2xHR7BTjm5xSlVK2Kde8AkAf mTlb0mF7Guv6XQJ4576ZZFh8dvuQkKzeESvEA/uHkvH/Q/uADuqeY51XEqN74WeG 6WBoYJvl/LvWPkmaj05MAL24LfYT8PVYZJ6OwA1agzW6qSYQV86/Aw0Ua3OhBEx+ DOvPxiacLM4uAVgwyOXVQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeduuddgvdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttdefjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeejfeegiefhfedukeduueetleeffedugedugeehueei udelueelgfektdeltdejveenucffohhmrghinhepmhhitghrohhsohhfthdrtghomhdpph hoshhtghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 24 Apr 2023 19:34:30 -0400 (EDT) Message-ID: <2b291cb1-bd10-bea6-e2d9-4872e4fe01d1@aklaver.com> Date: Mon, 24 Apr 2023 16:34:29 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: FW: Error! Content-Language: en-US To: Arquimedes Aguirre , pgsql-general list References: <1546b75f-d622-644b-2741-a5d061d9163a@aklaver.com> <3a35bb32-2e19-b22a-5bd2-c56a799f9413@aklaver.com> <124f49a3-5f47-de91-7677-59f7c16d5060@aklaver.com> <22bc24a9-4899-fd40-d209-e76573578d5b@aklaver.com> 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 4/24/23 16:16, Arquimedes Aguirre wrote: > No, it has not changed the error that I have been experiencing since the > beginning. This is the error: > > psql: error: connection to server at "localhost" (::1), port 5432 > failed: FATAL: password authentication failed for user "punta" Press any > key to continue . . 1) To be clear what password are you using the master password you set up for pgAdmin4 or the one for the Postgres server/database you are trying to connect to? 2) Did you create a password for the punta user on that server? 3) Find the pg_hba.conf file for that server and post it as text. > > Has always been the same error > > I got question, because can’t you send a screenshots, with the image > it’s much easier to identify the error or problem and you can also read > the message, I don’t understand? Many folks on this list only use text email so screenshots have to be opened in another program. Also it is simple to get the text. In the terminal/console right click and click on Select All and then hit Enter to copy the content and then paste to your email. > > Thanks! > > Sent from Mail for Windows > > *From: *Adrian Klaver > *Sent: *Monday, April 24, 2023 5:42 PM > *To: *Arquimedes Aguirre ; pgsql-general > list > *Subject: *Re: FW: Error! > > On 4/24/23 15:00, Arquimedes Aguirre wrote: > > Hi Dear > > > > Ok thanks so much for the explanation, but I don't understand, what does > > that connection have to do with the error that I described at the > > beginning, it gives me a password error with any user, what should I do > > to solve this problem and be able to start the connection?. > > > Well your problem description has changed over the course of this > conversation so at this point I don't really know what the error is that > you are referring to. > > USING TEXT not screenshots provide the command you are having the > problem with and the error message you are getting. > > You also need to be more specific about what connection as the last > screenshot you provided showed you where connected using pgAdmin4. > > > > > I would like to know other opinions from other people since this is a > > bigger large list of help users regarding this matter. > > 1) I'm going to say as a generalization the  users on this list probably: > >     a) Don't use pgAdmin4. >        and/or >     b) Don't use Windows. > > 2) There is a pgAdmin support list > > https://www.postgresql.org/list/pgadmin-support/ > > > > > > With any user that I enter, I get the same error when I go to enter the > > password. > > > > In the link that you sent, there is the operation of the entire program > > pgadmin 4 and it is very good, but where I can see some explanation in > > detail to the problem that is being presented to me, at what point > > exactly could be the answers or support for this type of failure > > Without knowing the command used and the error message it will be > difficult to point at a documented answer. > > > > > Thanks so much for attention and collaboration! > > > > Best regards! > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > -- Adrian Klaver adrian.klaver@aklaver.com