FATAL: password authentication failed for user "postgres" (postgresql 11 with pgAdmin 4)

Postgresql Problem Overview

I recently installed Postgresql 11, during the installation, there's no step to put password and username for Postgres. Now in pgAdmin 4, I wanted to connect the database to server and it's asking me to input password, and I haven't put any in the first place. Any one knows what's going on. Thank you!

Postgresql Solutions

Solution 1 - Postgresql

The default authentication mode for PostgreSQL is set to ident.

You can access your pgpass.conf via pgAdmin -> Files -> open pgpass.conf

That will give you the path of pgpass.conf at the bottom of the window (official documentation).

After knowing the location, you can open this file and edit it to your liking.

If that doesn't work, you can:

Find your pg_hba.conf, usually located under C:\Program Files\PostgreSQL\9.1\data\pg_hba.conf
If necessary, set the permissions on it so that you can modify it. Your user account might not be able to do so until you use the security tab in the properties dialog to give yourself that right by using an admin override.
Alternately, find notepad or notepad++ in your start menu, right click, choose "Run as administrator", then use File->Open to open pg_hba.conf that way.
Edit it to set the "host" line for user "postgres" on host "127.0.0.1/32" to "trust". You can add the line if it isn't there; just insert host all postgres 127.0.0.1/32 trust before any other lines. (You can ignore comments, lines beginning with #).
Restart the PostgreSQL service from the Services control panel (start->run->services.msc)
Connect using psql or pgAdmin4 or whatever you prefer
Run ALTER USER postgres PASSWORD 'fooBarEatsBarFoodBareFoot'
Remove the line you added to pg_hba.conf or change it back
Restart PostgreSQL again to bring the changes to effect.

Here is an example of the pg_hba.conf file (METHOD is already set to trust):

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# IPv4 local connections:
host    all             all             127.0.0.1/32            trust

# IPv6 local connections:
host    all             all             ::1/128                 trust

NOTE: Remember to change the METHOD back to md5 or other auth-methods listed here after changing your password (as stated above).

Solution 2 - Postgresql

For Windows variant - I too experienced this nasty bug because of pgAdmin for my Windows x64 install of version 9.2. It left my production paralyzed.

In folder C:\Program Files\PostgreSQL\9.2\data or C:\Program Files (x86)\PostgreSQL\9.x\data, you'll find the pg_hba.conf text file.

Find the following lines:

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# IPv4 local connections:
host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
host    all             all             ::1/128                 md5

and change METHOD md5 to "trust" like this:

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# IPv4 local connections:
host    all             all             127.0.0.1/32            trust
# IPv6 local connections:
host    all             all             ::1/128                 trust

From Windows>Run type "services.msc" and enter find the right PostgreSQL instance and restart it.

Your DB security is now blown wide open! Heed the warning to return it back to md5 after changing the user password expiry time to say year 2099 for all the relevant users.

Solution 3 - Postgresql

Change the password of default use ALTER USER postgres WITH PASSWORD 'new_password';

Solution 4 - Postgresql

Note: CREATE USER is the same as CREATE ROLE except that it implies LOGIN.

$ psql postgres
postgres=# create user postgres with superuser password 'postgres';

Solution 5 - Postgresql

After successfully changing the master password

If you get the same error even after following the master password reset steps Open your command prompt and execute

    psql -U postgres

It will ask you for the password, enter the new password which you set now parallelly open SQL shell(psql) and try again with the new password

Solution 6 - Postgresql

try using psql -U postgres if have put password while installing this is command where you have to use that. Thank you :)

Solution 7 - Postgresql

Option 1: If you use `trust`

Better change only postgres to trust in the pg_hba.conf, then access your db with postgres super user and add other users and passwords with the power of the postgres super user, then change all other peer to md5.

The steps: In the pg_hba.conf, change

local postgres to trust
do not change local all to trust,
instead change local all from peer to md5 - which means that a right password is enough to login.

See this solution in detail at the second answer of 'Getting error: Peer authentication failed for user "postgres", when trying to get pgsql working with rails'.

Option 2: Use `md5`, no `trust` needed (recommended)

This way is even easier because you will need to change the pg_hba.conf only once:

Change any local user from peer to md5, usually:

Change local postgres from peer to md5
Change local all from peer to md5

Add a postgres pw with the power of your Linux pw only:

 sudo su postgres
 psql (or psql -p <port> if you have more than one PostgreSQL)
 \password
 \q

See the accepted answer and the comments of "Getting error: Peer authentication failed for user "postgres", when trying to get pgsql working with rails".

Solution 8 - Postgresql

I have tried all the above mentioned solutions, trust me northing worked! I have resolved the issue by using following commands

psql -U default
\password

Enter new password:

Enter it again:

my username is : default

This worked perfectly for me.

Solution 9 - Postgresql

For Linux user try this

//CHECK POSTGRES IS WORKING OR NOT
sudo systemctl status postgresql

//THIS WILL ACCEPT PORTS
sudo pg_isready
sudo su postgres

//NAVIGATE TO SQL TERMINAL / BASH
psql

//CREATE A NEW USER WITH PASSWORD
CREATE USER shayon WITH PASSWORD 'shayon';

Solution 10 - Postgresql

I solved this problem by changing peer to trust in the file "pg_hba.conf" at local postgres then I restarted the postgres service with the command:

sudo service postgresql restart

That's it.

Solution 11 - Postgresql

I know this is an old question, but I had the same problem, e.g. no dialog for setting password for Postgres during installation with Postgresql 11.

Instead of doing all the file manipulations suggested in the other answers, I deleted Postgresql 11 and installed Postgresql 12, where I was prompted for setting password during installation.

Solution 12 - Postgresql

I currently had a headhache solving this case. A friend helped me I decided to post my solution here.

Open pg_hba.conf in any text editor (you can find this file in your postgres instalation folder > data);
Change all the methods fields to trust (meaning you don't need a password for postgre);
Run in your console this comand: "alter user postgres with password '[my password]';" | psql -U postgres (meaning to alter some user password for [my password] for the user as parameter -U postgres);
Et voilà (don't forget to change back the method from trust for the one that should be best for you).

I hope this help someone someday.

Solution 13 - Postgresql

Follow below stepsif you are using pgAdmin4 and facing error in updating password :

1] Open file "pg_hba.conf" and find "IPv4 local connections"

2] See the value under "Method" column, it must be set to "md5" becase you selected it while installing.

3] Make "md5" value blank and save the file. Restart pgAdmin4 application.

4] Now again set the value back to "md5" and input your password in pgAdmin application.

You should be successfully able to do it.

Solution 14 - Postgresql

Loggin to PgAdmin4

Go to

Object > Create > Login/Group Role
Create the "username" that was named in the psql terminal
Create password
Give it all the rights
Save
try the password immediately in the psql terminal.

It worked for me.

Hope this works for you.

Solution 15 - Postgresql

You can use the "superuser" password for the first time.

After that you can use Object > Create > Login/Group Role to change the password for the "postgres" user.

Solution 16 - Postgresql

For those of you who got this error and NONE of these answers helped, I may not have StackOverflow fish for you, but I'll teach you how to fish!

You likely don't have the correct order of lines in the pg_hba.conf file. If you read this PostgreSQL documentation link below, it says this error can be thrown if "no matching entry is found". However, that is NOT always true! Documentation is written by humans and humans make mistakes.

https://www.postgresql.org/docs/current/client-authentication-problems.html

The truth is that a line further up might take precedence, is qualifying and is forcing you to use a password stored in PostgreSQL rather than delegated authentication or some other method. If you are not specifying a password stored in PostgreSQL, then you do not need the LOGIN role attribute. Put a line at the very top of this list with your specific user, authentication protocol, network details and other criteria. Also, many may think that most computers use IPv4. Try IPv6 and you'll be surprised. Once you know the very specific criteria of your issue and place a line at the top, then you have established the ONLY RELIABLE WAY to troubleshoot these pg_hba.conf issues without source code debugging!

Another helpful trick is to create a crapload of Server entries in pg_admin (SQL IDE for PostgreSQL) with all of your users and authentication protocols for testing. When you test different scenarios, you'll instantly know which ones fail.

Also, whenever you change this file, restart the PostgreSQL service, before testing the user.

You're welcome my friend. :)

Solution 17 - Postgresql

windown 11 - postgres 14

open pgAdmin4 - click servers
right-click on your windows user name rule, e.g: MyUserName.
definition tab - enter password, click save.
open/re-open terminal
run: psql "postgres:///"

if you get "MyName database doesn't exist" you're good to go

Solution 18 - Postgresql

This particular situation I'm about to mention probably doesn't come up very often, but I was getting this error as well. After looking into it, it was because I had a local postgres instance listening on port 5433, and I was trying to set up a Kubernetes tunnel to a remote PG instance mapped to local port 5433 as well. It turns out the command I was running was attempting to connect to the local instance rather than the remote instance. When I temporarily stopped the local instance, I was able to connect to the remote instance through the tunnel without changing the psql command I was using.

Content Type	Original Author	Original Content on Stackoverflow
Question	Michelley	View Question on Stackoverflow
Solution 1 - Postgresql	iLuvLogix	View Answer on Stackoverflow
Solution 2 - Postgresql	Pavan Patel	View Answer on Stackoverflow
Solution 3 - Postgresql	Gaurav Patil	View Answer on Stackoverflow
Solution 4 - Postgresql	user1575148	View Answer on Stackoverflow
Solution 5 - Postgresql	pAce	View Answer on Stackoverflow
Solution 6 - Postgresql	VASU TIWARI	View Answer on Stackoverflow
Solution 7 - Postgresql	questionto42standswithUkraine	View Answer on Stackoverflow
Solution 8 - Postgresql	Arya Mohanan	View Answer on Stackoverflow
Solution 9 - Postgresql	MD SHAYON	View Answer on Stackoverflow
Solution 10 - Postgresql	Younes Belouche	View Answer on Stackoverflow
Solution 11 - Postgresql	Drublic	View Answer on Stackoverflow
Solution 12 - Postgresql	Germano SoftwareDev	View Answer on Stackoverflow
Solution 13 - Postgresql	Pushkaraj Bhandari	View Answer on Stackoverflow
Solution 14 - Postgresql	Walter Clayton	View Answer on Stackoverflow
Solution 15 - Postgresql	Nilo Guimaraes	View Answer on Stackoverflow
Solution 16 - Postgresql	MacGyver	View Answer on Stackoverflow
Solution 17 - Postgresql	Itay Tur	View Answer on Stackoverflow
Solution 18 - Postgresql	Eric Walker	View Answer on Stackoverflow

FATAL: password authentication failed for user "postgres" (postgresql 11 with pgAdmin 4)

Postgresql Problem Overview

Postgresql Solutions

Solution 1 - Postgresql

Solution 2 - Postgresql

Solution 3 - Postgresql

Solution 4 - Postgresql

Solution 5 - Postgresql

Solution 6 - Postgresql

Solution 7 - Postgresql

Option 1: If you use `trust`

Option 2: Use `md5`, no `trust` needed (recommended)

Solution 8 - Postgresql

Solution 9 - Postgresql

Solution 10 - Postgresql

Solution 11 - Postgresql

Solution 12 - Postgresql

Solution 13 - Postgresql

Solution 14 - Postgresql

Solution 15 - Postgresql

Solution 16 - Postgresql

Solution 17 - Postgresql

windown 11 - postgres 14

Solution 18 - Postgresql

Manipulate system/visible clipping region in Windows 1809

Kotlin could not find the required JDK tools in the Java installation

Attributions

Postgresql Problem Overview

Postgresql Solutions

Solution 1 - Postgresql

Solution 2 - Postgresql

Solution 3 - Postgresql

Solution 4 - Postgresql

Solution 5 - Postgresql

Solution 6 - Postgresql

Solution 7 - Postgresql

Option 1: If you use trust

Option 2: Use md5, no trust needed (recommended)

Solution 8 - Postgresql

Solution 9 - Postgresql

Solution 10 - Postgresql

Solution 11 - Postgresql

Solution 12 - Postgresql

Solution 13 - Postgresql

Solution 14 - Postgresql

Solution 15 - Postgresql

Solution 16 - Postgresql

Solution 17 - Postgresql

windown 11 - postgres 14

Solution 18 - Postgresql

Manipulate system/visible clipping region in Windows 1809

Kotlin could not find the required JDK tools in the Java installation

Attributions

Option 1: If you use `trust`

Option 2: Use `md5`, no `trust` needed (recommended)