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.96) (envelope-from ) id 1wdSZ0-00475K-2j for pgsql-bugs@arkaria.postgresql.org; Sat, 27 Jun 2026 12:55:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wdSYz-00FIMa-2S for pgsql-bugs@arkaria.postgresql.org; Sat, 27 Jun 2026 12:55:13 +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.96) (envelope-from ) id 1wd8vT-00BnUX-2h for pgsql-bugs@lists.postgresql.org; Fri, 26 Jun 2026 15:57:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wd8vR-00000000MAZ-1tEG for pgsql-bugs@lists.postgresql.org; Fri, 26 Jun 2026 15:57:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=ORUFSu/uM2864H7LKC/AWnhWyVdH9OMe2foM8N6i0Zc=; b=OIWmabVmBUj1v1YGIiRNmUJy12 G71Vm4+LhCWc2E0ip9LCj5FYt7Sdv8RCRq1cOcUzrBD4Sar0q1lXXknTe8Y+A7bK/o6+WFiNuBUlU ikWoVlqhS2eEfvnYKjWGUU7EFpx6f2dijXl66oM2y3p+HLSumNcB/y1SXAbwYjZZ35tCUR8LssW8H +OdKmybXrnPxgJVGTps6qTVIHb9gEJHbZuaBJ9z3CopKuCS1YogM5O32mZZG88MsZxlpWehnYpAMF 0R4SmA018vukIhrpwGTqeHE3zyQP2QqAOkJEd/aY/om+g+7l2KNGvWwxwRWNrSnlq+aPhsSo9EGfV BGkCnODA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wd8vQ-006t2p-36 for pgsql-bugs@lists.postgresql.org; Fri, 26 Jun 2026 15:57:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wd8vP-002jsz-1I for pgsql-bugs@lists.postgresql.org; Fri, 26 Jun 2026 15:57:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19537: Authentication failed regardless of typing exactly my password set from sudo passwd postgres To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: joshcabara22@gmail.com Reply-To: joshcabara22@gmail.com, pgsql-bugs@lists.postgresql.org Date: Fri, 26 Jun 2026 15:56:25 +0000 Message-ID: <19537-a8c72b8459700bfb@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19537 Logged by: JOSHUA CABANILLAS Email address: joshcabara22@gmail.com PostgreSQL version: 18.4 Operating system: Ubuntu 26.04 LTS Description: =20 Hey, I'm using pg Admin 9.16 and have Ubuntu 26.04 LTS running as my OS. So I tried to reinstall from scratch everything, just to see if this would work. However, after reinstalling postgresql postgresql-contrib and pg Admin from scratch step-by-step, and set my password and typed it exactly on the pg Admin Register Server dialog it threw me the following error: Unable to connect to server: connection failed: connection to server at "127.0.0.1", port 5432 failed: FATAL: password authentication failed for user "postgres" connection to server at "127.0.0.1", port 5432 failed: FATAL: password authentication failed for user "postgres" So I just gave up on trying to fix it for my own and followed through this forum to submit it as a bug report. Any guidance for fixing this error will be appreciated. Cheers.