Reputation: 6880
I either forgot or mistyped (during the installation) the password to the default user of PostgreSQL. I can't seem to be able to run it, and I get the following error:
psql: FATAL: password authentication failed for user "hisham"
hisham-agil: hisham$ psql
Is there a way to reset the password or how do I create a new user with superuser privileges?
I am new to PostgreSQL and just installed it for the first time. I am trying to use it with Ruby on Rails and I am running Mac OS X v10.7 (Lion).
Upvotes: 312
Views: 766839
Reputation: 101800
If your postgres is running in a docker container, try the following line instead:
host all all 172.17.0.1/32 trust
172.17.0.1
is the gateway address for the docker bridge network.
Upvotes: 0
Reputation: 1
ALTER USER yourusername WITH SUPERUSER
Upvotes: -1
Reputation: 99
sudo -u postgres psql
ALTER USER user_name WITH PASSWORD 'new_password';
Upvotes: 6
Reputation: 4171
If you are running PostgreSQL on macOS, try these:
1. Edit the pg_hba.conf file
sudo vi /Library/PostgreSQL/9.2/data/pg_hba.conf
and Change the "md5" method for all users to "trust" near the bottom of the file
2. Find the name of the postgres service
ls /Library/LaunchDaemons
Look for postgresql
3. Restart the postgresql service
sudo launchctl stop com.edb.launchd.postgresql-9.2
sudo launchctl start com.edb.launchd.postgresql-9.2
(com.edb.launchd.postgresql-9.2 should be name postgresql service from step 3)
4. Start a psql session as postgres
psql -U postgres
(shouldn't ask for password because of 'trust' setting)
5. Reset password in the psql session by typing:
ALTER USER postgres with password 'secure-new-password';
6. Edit the pg_hba.conf file Switch it back to 'md5'
8. Restart services again
Upvotes: 4
Reputation: 1054
I didn't manage to find the file pg_hba.conf
in the folder C:\Program Files\PostgreSQL\14\data
, because there is not a folder data
at all.
I solved the problem by creating a new user using pgAdmin and gave it super system administrator rights.
Upvotes: 0
Reputation: 451
This is the document I am referring to: How can I reset a PostgreSQL password?
Open your cmd and go to C:\Program Files\PostgreSQL\12\data
.
This is usually the right path. You might have it stored somewhere else. Note that, if you have a different PostgreSQL version, there will be a different number. That doesn't matter.
Find a pg_hba.conf file and copy it to somewhere else (that way you will have an unmodified version of this file, so you will be able to look at it after we make some changes)
Open the pg_hba.conf file (not the backup, but the original)
Find the multiple lines that start with host near the bottom of the file:
host all all 127.0.0.1/32 md5
host all all ::1/128 md5
host replication all 127.0.0.1/32 md5
host replication all ::1/128 md5
Replace md5 with trust:
host all all 127.0.0.1/32 trust
host all all ::1/128 trust
host replication all 127.0.0.1/32 trust
host replication all ::1/128 trust
Close this file
Go to your search bar on windows and open Services app. Find postgres and restart it.
Write cd.. in cmd and then cd bin. Your path should be C:\Program Files\PostgreSQL\12\bin
Enter: psql -U postgres -h localhost
Enter: ALTER USER postgres with password '<your new password>';
Make sure that you include ; at the end
“ALTER ROLE” should be displayed as an indication that the previous line was executed successfully
Open original pg_hba.conf file and change back from trust to md5
Restart the server with Services app as before
Upvotes: 45
Reputation: 1
Add the below line to your pg_hba.conf file. Which will be present in the installation directory of PostgreSQL
hostnossl all all 0.0.0.0/0 trust
It will start working.
Upvotes: -1
Reputation: 29
Follow step 1 on the best answer.
Here is my addition if you use the Windows operating system. Follow only step 1, and then open pgAdmin or postgres on web and click on file on the top nav. Click on reset layout, and finally reload the application. Whatever password you put should work. I used 1234.
Upvotes: 0
Reputation: 1370
For a Windows user for the latest PostgreSQL version (greater than 10):
Go to your PostgreSQL installation location, and search for pg_hba.conf
, you will find it in ..\postgres\data\pg_hba.conf
.
Open that file with Notepad, and find this line:
# 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
#..
Change the method from *md5* 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
# ...
Now go to your SQL shell (PSQL) and leave everything blank,
Server [localhost]:
Database [postgres]:
Port [8000]:
Username [postgres]:
It will not ask for a password this time, and you will be logged in,
Now run this line:
`ALTER USER yourusername WITH SUPERUSER`
Now you can leave the shell with \q.
Again, go to the file pg_hba.conf and change METHOD from trust to md5 again, and save it.
Now log in with your new user and password, and you can check \du for its attributes.
Upvotes: 10
Reputation: 5704
I did this to resolve the same problem:
Open the pg_hba.conf file with the gedit editor from the terminal:
sudo gedit /etc/postgresql/9.5/main/pg_hba.conf
It will ask for a password. Enter your admin login password. This will open gedit with the file. Paste the following line:
host all all 127.0.0.1/32 trust
just below -
# Database administrative login by Unix domain socket
Save and close it.
Close the terminal, open it again and run this command:
psql -U postgres
You will now enter the psql console.
Now change the password by entering this:
ALTER USER [your preferred user name] with password '[desired password]';
If it says the user does not exist then instead of ALTER
, use CREATE
.
Lastly, remove that certain line you pasted in pg_hba and save it.
Upvotes: 2
Reputation: 199
Just a note: On Linux, you can simply run sudo su - postgres
to become the postgres user and from there change what is required using psql.
Upvotes: 17
Reputation: 15547
Edit the file /etc/postgresql/<version>/main/pg_hba.conf
and find the following line:
local all postgres md5
Edit the line and change md5
at the end to trust
and save the file
Reload the postgresql service
sudo service postgresql reload
This will load the configuration files. Now you can modify the postgres
user by logging into the psql
shell
psql -U postgres
Update the postgres
user's password
alter user postgres with password 'secure-passwd-here';
Edit the file /etc/postgresql/<version>/main/pg_hba.conf
and change trust
back to md5
and save the file
Reload the postgresql service
sudo service postgresql reload
Verify that the password change is working
psql -U postgres -W
Upvotes: 24
Reputation: 39
If you are on Windows you can just run
net user postgres postgres
And log in in PostgreSQL with postgres/postgres as the user/password.
Upvotes: 0
Reputation: 17024
The pg_hba.conf
(C:\Program Files\PostgreSQL\9.3\data
) file has changed since these answers were given. What worked for me, in Windows, was to open the file and change the METHOD
from md5
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
Then, using pgAdmin III, I logged in without using a password and changed user postgres
's password by going to menu File → Change Password.
Upvotes: 96
Reputation: 18681
When connecting to PostgreSQL from the command line, don't forget to add -h localhost
as a command line parameter. If not, PostgreSQL will try to connect using PEER authentication mode.
The below shows a reset of the password, a failed login with PEER authentication and a successful login using a TCP connection.
# sudo -u postgres psql
could not change directory to "/root"
psql (9.1.11)
Type "help" for help.
postgres=# \password
Enter new password:
Enter it again:
postgres=# \q
Failing:
# psql -U postgres -W
Password for user postgres:
psql: FATAL: Peer authentication failed for user "postgres"
Working with -h localhost
:
# psql -U postgres -W -h localhost
Password for user postgres:
psql (9.1.11)
SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
Type "help" for help.
postgres=#
Upvotes: 174
Reputation: 21
For a Windows installation, a Windows user is created. And "psql" uses this user for connection to the port. If you change the PostgreSQL user's password, it won't change the Windows one. The command line just below works only if you have access to the command line.
Instead, you could use the Windows GUI application "c:\Windows\system32\lusrmgr.exe". This application manages users created by Windows. So you can now modify the password.
Upvotes: 2
Reputation: 12820
Find the file pg_hba.conf. It may be located, for example, in /etc/postgresql-9.1/pg_hba.conf.
cd /etc/postgresql-9.1/
Back it up
cp pg_hba.conf pg_hba.conf-backup
Place the following line (as either the first uncommented line, or as the only one):
For all occurrence of below (local and host) , except replication section if you don't have any it has to be changed as follow ,no MD5 or Peer authentication should be present.
local all all trust
Restart your PostgreSQL server (e.g., on Linux:)
sudo /etc/init.d/postgresql restart
If the service (daemon) doesn't start reporting in log file:
local connections are not supported by this build
you should change
local all all trust
to
host all all 127.0.0.1/32 trust
You can now connect as any user. Connect as the superuser postgres (note, the superuser name may be different in your installation. In some systems it is called pgsql, for example.)
psql -U postgres
or
psql -h 127.0.0.1 -U postgres
(note that with the first command you will not always be connected with local host)
Reset the password ('replace my_user_name with postgres since you are resetting the postgres user)
ALTER USER my_user_name with password 'my_secure_password';
Restore the old pg_hba.conf file as it is very dangerous to keep around
cp pg_hba.conf-backup pg_hba.conf
Restart the server, in order to run with the safe pg_hba.conf file
sudo /etc/init.d/postgresql restart
Further reading about that pg_hba file: 19.1. The pg_hba.conf File (official documentation)
Upvotes: 478
Reputation: 12222
I was just having this problem on Windows 10 and the issue in my case was that I was just running psql
and it was defaulting to trying to log in with my Windows username ("Nathan"), but there was no PostgreSQL user with that name, and it wasn't telling me that.
So the solution was to run psql -U postgres
rather than just psql
, and then the password I entered at installation worked.
Upvotes: 23