Unable to connect to server postgresql windows

I have a problem to connect server for Postgres after I updated my windows.Before I update there is no problem to open the database. My database in Postgres also gone. When I want to create my new database it show this error:

Unable to connect to server: could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host «localhost» (::1) and accepting TCP/IP connections on port 5432? could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host «localhost» (127.0.0.1) and accepting TCP/IP connections on port 5432?

On windows, Just go to the ‘Services’. Start/Restart the postgresql-X64 service. It worked for me as my service was in stopped state somehow.

First press win key+R
Search for services.msc
A window will open in that find postgresql-x64-13 and open that, in that tab click start option
For me its works perfectly.

answered Aug 7, 2020 at 21:49

On windows, Just go to the ‘Services’. Start/Restart the postgresql-X64 service. It worked for me as my service was in stopped state somehow.

worked for me

answered Sep 10, 2020 at 18:00

This happened because I installed two versions of Postgres (v12 and v13). Psql 12 was installed later so got the port 5433. I needed to use Postgres 12. To fix this particular case:

• Go to Program Files/Postgres/<required_version>/data

  Open the postgresql.conf file

  Search for Port and change the port number to 5432.

• Open Windows Services (Press Cmd + R then type services.msc)

• Stop the service for the version you don’t want (You can stop it permanentally from the Right Click > Properties menu.)

• Start the service for the version you want.

answered Aug 7, 2021 at 14:30

I think the problem is with your server listening to default public IP address.
For example in the PostgreSQL package, your sever is set to listen to localhost as default public address which when you launch/ run database, the address might be something like ‘127.0.0.1’

To fix you can try change localhost to ‘‘ as in «listen_addresses = ‘‘».

As seen as "listen_addresses = 'localhost'" under «Connection Settings» in the postgresql.conf file.

Also to access your postgresql.conf file, go to:

On Windows, the file is in /Program Files/PostgreSQL/<version>/share/.
On Ubuntu, these files are in /etc/postgresql/<version>/main/.

P.S: Changing the defaults ‘localhost’; to ‘*’ will let your server listen to any public database address either «localhost, 127.0.0.1 etc.

I know you might have fix this, just for others that might run into the same issue in the future. Hope it was helpful

goto service and start postgresql-x64-10 service

steps

• run -> services.msc -> find postgresql-x64-10 -> start the service
• services image

answered Mar 12, 2021 at 14:33

I had the same issue, so, I uninstalled postgres. And during reinstallation I noticed the error:
"Failed to load SQL modules into the database cluster"
And:
"Problem running post installation step.Installition may not complete correctly. Error reading file C:/Program Files/PostgreSQL/14/data/postgresql.conf".

I cancelled the installation and then tried again, but with a plain-text password this time, and it worked. It turned out that the special characters in my password were the problem.

I got this error message when I moved my database to another computer.

I also got some error messages when starting the server first with

pg_ctl -D /wherever/your/database/is start

which were

pg_ctl: another server might be running; trying to start server anyway
server starting

DETAIL: File «/wherever/your/database/is/PG_VERSION» does not contain valid data.

HINT: You might need to initdb.

In my case rather than running initdb this command actually fixed the issue

pg_ctl -D /wherever/your/database/is restart

answered May 10, 2018 at 13:42

You might have changed the permissions of the ‘PostgreSQL 12’ in ‘services.msc’. Or maybe it is not started and you are trying to start the server when Postgre 12 is not running.

Try these:

1. Try to start the ‘PostgreSQL 12’ in ‘services.msc’ manually.
2. Try restarting your PC
3. If nothing helps, try reinstalling PostgreSQL (pgAdmin 4) from the scratch.

answered Mar 30, 2021 at 12:18

Go to C:Program FilesPostgreSQL13data, edit postgresql.conf with notepad.

Change:

#port = 54XX

To:

port = 54XX

(change requires restart)

restart service at «service system» on window.

Using psql with single quotes fails:

psql -c 'Select version();' 'postgresql://username:password@db.abcdefghi.ap-southeast-2.rds.amazonaws.com:8080/the_db'

psql: could not connect to server: Connection refused
(0x0000274D/10061)
Is the server running on host «localhost» (::1) and accepting
TCP/IP connections on port 5432? could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host «localhost» (127.0.0.1) and accepting
TCP/IP connections on port 5432?

Using double quotes works:

psql -c "Select version();" "postgresql://username:password@db.abcdefghi.ap-southeast-2.rds.amazonaws.com:8080/the_db"

PostgreSQL 10.14 on x86_64-pc-linux-gnu, compiled by x86_64-unknown-linux-gnu-gcc (GCC) 4.9.4, 64-bit
(1 row)

answered Jul 14, 2021 at 1:40

After a wasting 3-4 hrs i find the solution something like this

First set path in enviroment variable.And then make port and psql connecting same i.e 5432 or 5433

answered Sep 18, 2021 at 3:21

For me I was getting this error and unable to open the server in PgAdmin is because I very often forgot to start the server, one for the way you can start the server with is by running this commands on cmd, make sure you provide the right path

cd "C:Program FilesPostgreSQL14bin"
pg_ctl -D "C:Program FilesPostgreSQL14data" start

answered Apr 13, 2022 at 6:42

And so for the new arrivals. If you are using pgAdmin and a Windows operating system, do some research to resolve the issue.

Make sure you have Postgresql installed or active

• To do this, go to windows services (press Cmd + R and run the services.msc command)

• Look in the list for a service called postgresql-x{BIT}-{Version}-PostgreSQL Server {Version}

  

Solution 1: If you don’t find the service, then PostgreSQL is not installed or has been uninstalled, install it again.

Solution 2: If you find the service, but you still can’t log in, then most likely the service is not active for some reason, select the service and click the Start or Restart button

answered Mar 24, 2022 at 4:41

• Cloud Server running Linux (CentOS 7 or Ubuntu 16.04)
• PostgreSQL installed and running.

Low-cost, powerful VPS hosting for running your custom applications, with a personal assistant and 24/7 support.

The PostgreSQL error “Could not connect to server: No such file or directory” usually means that PostgreSQL is not running. However, the error is actually often related to issues withpermission.

First, use the systemctl status postgresql command to check PostgreSQL’s status:

Another variant of the PostgreSQL error is “Could not connect to server: Connection refused”.

First, use the systemctl-status postgresql command to verify that PostgreSQL is running. To be sure that PostgreSQL is running, you can also restart it with systemctl restart postgresql.

If this does not fix the problem, the most likely cause of this error is that PostgreSQL is not configured to allow TCP/IP connections.

To correct this, edit your posgresql.conf file. These can be found in one of the following file paths, depending on your Linux distribution:

• Ubuntu 16.04: sudo nano /etc/postgresql/9.5/main/posgresql.conf
• CentOS 7: sudo nano /usr/pgsql-10/share/postgresql.conf

Check the listen_address configuration. To allow TCP/IP connections, it should be set to “0.0.0.0” (to allow connections from all IP addresses) or to the specific IP address of the server it will allow to connect.

If this configuration is left blank or set to localhost, PostgreSQL will not allow external TCP/IP connections. This also corresponds to the default setting of PostgreSQL.

PostgreSQL will not be able to connect to the server when the connection is blocked by a firewall. Note that all Cloud Servers are affected by the default Firewall Policy which is controlled from the Cloud Panel.

Make costly downtime a thing of the past and back up your business the easy way!

@Stepan47

Я программист, преимущественно на Python, Java, С#

Я при создании сервера на pgadmin, сталкиваюсь с ошибкой:

Unable to connect to server:

could not connect to server: Connection refused
Is the server running on host "localhost" (127.0.0.1) and accepting
TCP/IP connections on port 5432?

Вот скриншот если кому не понятно где и как я это делаю:.
Вопрос короткий довольно короткий, как создть сервер?

Сначала нужно создать базу данных postgress (или другую), сделать на ней пользователя, и подкючить ее к pgadmin.

05 февр. 2023, в 00:09

5000 руб./за проект

04 февр. 2023, в 20:45

1000 руб./за проект

04 февр. 2023, в 20:04

35000 руб./за проект

Hi,

Can you provide your docker version, docker-compose version and operating system?
Can you ping localhost:5432 to check if something it is running something?

Otherwise it is probably because, for security reasons, a PostgreSQL server “out of the box” doesn’t listen on TCP/IP ports.Instead, it has to be enabled to listen for TCP/IP requests.

This can be done by adding tcpip = true to the postgresql.conf file for Versions 7.3.x and 7.4.x, or listen_addresses=’*’ for Version 8.0.x and above; this will make the server accept connections on any IP interface.

ref: https://www.pgadmin.org/docs/pgadmin4/dev/connect_error.html

I have the same issue, offcourse changing postgres conf in a docker container is a pain in the ass, someone managed to do it ?

Thanks all

Some hack that worked for me :
docker inspect container_name_or_hah
Then find your local ip address that is bind to the postgres container and you use it in the pgAdmin configuration

Ok, I had the above trouble, and saw this screen:

So, I ran docker inspect postgres_container

I got a long stream of JSON as a result, but half way down was config block. The first entry in this was `»Hostname»: «4765bite0me3112»

I entered 4765bite0me3112 as the Host name/address in the dialog, and it connected immediately.

You can also use postgres as host name since it is the service name in the compose file.
Other services(for instance pgadmin4) in the same network will resolve it.

mac
hostname: host.docker.internal

mac
hostname: host.docker.internal

Windows works too, thank you

if you closed the pgadmin from the task manager it will be a problem after rerun it again so if you did that you just need to do the next steps:
1-go to search windows write «services» click enter
it will open a services window than
2-search for «postgresql»
3-right click and again click in proprieties
4- and last one click start

run again your pgadmin and it will work
good luck

So, I ran docker inspect postgres_container
I got a long stream of JSON as a result, but half way down was config block. The first entry in this was "Hostname": "4765bite0me3112" I entered 4765bite0me3112as theHost name/address` in the dialog, and it connected immediately.

Yes, hashed hostname worked for me too. This is very confusing though.

I also use adminer in the same way (as a docker container to access the postgres docker container) and it is able to figure this out without any user input. Worth adopting that approach as a default

You can also use postgres as host name since it is the service name in the compose file.
Other services(for instance pgadmin4) in the same network will resolve it.

Didn’t work for me:

**Unable to connect to server:

could not translate host name «93ed5fee89db» to address: nodename nor servname provided, or not known**

Ok, I had the above trouble, and saw this screen:

So, I ran docker inspect postgres_container

I got a long stream of JSON as a result, but half way down was config block. The first entry in this was `»Hostname»: «4765bite0me3112»

I entered 4765bite0me3112 as the Host name/address in the dialog, and it connected immediately.

Need to put docker container name in place of localhost:

I up this compose and all is good except when I add a new server in pgAdmin to connect to postgres, it says: Unable to connect to server:

could not connect to server: Connection refused Is the server running on host «localhost» (127.0.0.1) and accepting TCP/IP connections on port 5432? could not connect to server: Address not available Is the server running on host «localhost» (::1) and accepting TCP/IP connections on port 5432?

my new server: Host: localhost port: 5432

I can connect through local pgAdmin installation though, but not the one on localhost:5050.

Is it only me having this problem? Am I missing something?

You need to put in place of localhost, your docker container name: