No pg hba conf entry for host

03.09.202203.09.2022 admin 0 Comments

No pg hba conf entry for host

Heroku Postgres: «psql: FATAL: no pg_hba.conf entry for host»

There are a number of Heroku CLI Postgres commands that all return the same error. For example:

At least one of these commands has worked in the past, but does not now.

The database appears to be working fine otherwise. I can access it via my application’s interfaces.

I do not see a way to toggle SSL in the Heroku Postgres dashboard. What could be causing this and how could I fix it?

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I solved it by setting PGSSLMODE on Heroku to require. This tells Postres to default to SSL. On the command line this can be done via the following command.

The error basically says that you are trying to connect to a database instance without using SSL connection, but the server is setup to reject connection without SSL connection.

pg_hba.conf file resides in the server, and contains details of the allowed connections. In your case there’s no matching record to be found in the file with the given details(under non-ssl connection).

You can fix this by forcing the connection to be follow SSL protocol. As Raj already mentioned, you need to modify your connection string to include the ‘sslmode=require’. Here’s a heroku documentation regarding the same. Check out the ‘external connections’ block in the doc.

how to fix no pg_hba.conf entry for host «::1»

I’m standing up a new application and having some issues with host based authentication. I know there are other posts out there (espec this one) but nothing I try seems to work.

no pg_hba.conf entry for host «::1», user «root», database «db_name_here», SSL off

My pg_hba.conf file looks like:

I have a note to myself from the past where I said the following worked:

even that didn’t work, same error.

I’ve read the postgresql docs, and while the helped explain what was going on, (and made me try hostnossl, to no avail) I’m still getting the same error.

Do you see my mistake?

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Your pg_hba.conf entry is missing the netmask; a plain IP address is a syntax error. This one should work:

Make sure you reload the database with

and check the log file for errors (that is important, as a syntactically wrong file won’t be loaded).

The alternative is to enable SSL on the server side and use it for the local connection.

The fastest way to connect would be via Unix sockets (if you are not on Windows or use the JDBC driver), perhaps that is the best thing to do.

org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host

I am trying to connect to PostgreSQL database which is in remote location using Spring JDBC template. I am getting

org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host «139.126.243.71», user «guest», database «masterdb», SSL off error

I don’t have access to pg_hba.conf file of the remote location.

This is the configuration I gave in my spring servlet.xml

Can we solve the issue by giving any properties?

6 Answers 6

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

It seems that DB server does not allow SSL off connection, You will have to enable it. Change URL from jdbc:postgresql://100.64.35.52″:5432/masterdb to jdbc:postgresql://100.64.35.52″:5432/masterdb?sslmode=require

You must apply below changes to connect:

Navigate to the the following location C:\Program Files (maybe x86)\PostgreSQL\(your version)\data

postgresql.conf file:

pg_hba.conf file:

( use of above row is better) or

And finally it’s very important that the ssl mode is to be on. For this add below command in the end of your url:

In Terms of Bean as

Error explanation

The file pg_hba.conf (host-based authentication configuration file) is used to control the client authentication. This file is located in the database cluster’s data directory.

The error java.sql.SQLException: FATAL: no pg_hba.conf entry for host » «, user «

«, database » «, SSL off means that Postgres accepts SSL connections but your are trying to connect without SSL.

Secured connection

Check if database server is using SSL

If you want to connect with a given user at a given port:

Or if you want to connect at the default port with your current user:

You should see an such output if you have established a SSL connection:

Note that the last line contains ‘SSL connection’.

JDBC connection parameters

The JDBC driver provdies an option to establish a SSL connection without doing any validation (but it’s risky!).

A non-validating connection is established via a custom SSLSocketFactory class that is provided with the driver. Setting the connection URL parameter sslfactory=org.postgresql.ssl.NonValidatingFactory will turn off all SSL validation.

This was my case and why I also got the same error you had. So, to establish the connection I have:

connect to PostgreSQL server: FATAL: no pg_hba.conf entry for host

Hello I am trying to run a website sent to me but after doing so this error appeared

after Googling it it says that i just need to add an entry in the pg_hba.conf file for that particular user. this is my pg_hba.conf file.

but after doing so, the error still persist. I restarted my XAMPP server several times but no changes appears. Thanks in advance

12 Answers 12

Add or edit the following line in your postgresql.conf :

Restart Postgresql after adding this with service postgresql restart or the equivalent command for your setup. For brew, brew services restart postgresql

This solution works for IPv4 / IPv6:

Edit pga_hba.conf File

Open up the pga_hba.conf file in your favourite editor:

Append To pga_hba.conf File

Append the following lines to the end of the pga_hba.conf file:

Quit and save the editor of your preference.

Restart Service

Restart the postgresql service with the following command:

The way I solved this was:

Added the line as below in pg_hba.conf :

I had this instance running on a Centos 7.3 and Postgres 9.5 in a VM in Azure, given this was a POC (proof of concept) you won’t want to connect without SSL in your actual prod environment.

To connect to the instance I was using pgAdmin 4 on macOS Sierra.

Fresh Postgres 9.5 install, Ubuntu.

The key was the local connection type, since psql uses domain socket connection.

Instructions for Debian users.

Get the location of pg_hba.conf by quering the database:

Add configuration where it says «Put your actual configuration here»:

Logout to your user:

Restart your postgres server for changes to take effect:

Add the following line in the bottom of pg_hba.conf :

hostnossl all all 0.0.0.0/0 md5

Add/modify the line in postgresql.conf :

MAKE SURE THAT the user that is connecting has a password: (Example connect user named postgres )

a. Run the following psql command with the postgres user account:

b. Set the password:

This below worked for me: (pg_hba.conf)

Allow the connection unconditionally. This method allows anyone that can connect to the PostgreSQL database server to login as any PostgreSQL user they wish, without the need for a password or any other authentication.

Require the client to supply a double-MD5-hashed password for authentication.

In my case I ran into this where I didn’t have access to edit any conf files on the server (.NET connecting to a managed db on DigitalOcean) so the other answers weren’t an option.

That may not be the optimal solution for me or for you, but I wanted to point out it’s possible that this is an issue with the connection string rather than the server config.

In my case, I had to add the exact line as suggested by the error information. Cannot bypass it by adding «all» users with all IPs as rule. Now it is like:

PosgreSQL 10.5 on CentOS 7.

Find the correct configuration file:

Add the following at the end of file:

Then restart your PostgreSQL application:

For PgAdmin 4 on Windows. I added these lines below

and modify postgresql.config:

Not the answer you’re looking for? Browse other questions tagged postgresql php pg-hba.conf or ask your own question.

Linked

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

no pg_hba.conf entry for host

I get following error when I try to connect using DBI

Here is my pg_hba.conf file:

My perl code is

May I know what i miss here?

16 Answers 16

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

If you can change this line:

You can see if this solves the problem.

But another consideration is your postgresql port(5432) is very open to password attacks with hackers (maybe they can brute force the password). You can change your postgresql port 5432 to ‘33333’ or another value, so they can’t know this configuration.

In your pg_hba.conf file, I see some incorrect and confusing lines:

I suspect that if you md5’d the password, this might work if you trim the lines. To get the md5 you can use perl or the following shell script:

So then your connect line would like something like:

Your postgres server configuration seems correct That should grant access from the client to the postgres server. So that leads me to believe the username / password is whats failing.

Test this by creating a specific user for that database

Then adjust your perl script to use the newly created user

To resolve this problem, you can try this.

first, you have found out your pg_hba.conf by:

cd /etc/postgresql/9.5/main from your root directory

and open file using

then add this line:

to your pg_hba.conf and then restart by using the command:

Add the following in line in pg_hba.conf

hostnossl all all 0.0.0.0/0 trust

And then restart the Service.

To resolved this problem, you can try this.

first you have find out your pg_hba.conf and write :

after that restart pg server:

If you are getting an error like the one below:

then add an entry like the following, with your mac address.

If you are getting this error using node and pg module you can set ssl to not reject unauthorized access like this

I faced the same issue. My db was on cloud

ERROR: no pg_hba.conf entry for host «. «, user «. «, database «. «, SSL off

I add this configuration to resolve this,

SSL parameter is the key telling DB to always use SSL for making connections.

For those who are getting this error in DBeaver the solution was found here at line:

@lcustodio on the SSL page, set SSL mode: require and either leave the SSL Factory blank or use the org.postgresql.ssl.NonValidatingFactory

also check the PGHOST variable:

to see if it matches the local machine name

BTW, in my case it was that I needed to specify the user/pwd in the url, not as independent properties, they were ignored and my OS user was used to connect

My config is in a WebSphere 8.5.5 server.xml file

This would not work and was getting the error:

Resolve «FATAL:no pg_hba.conf entry for host» Error when you Connect from PGAdmin4

Available Languages

Download Options

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

This document describes how to resolve «FATAL: no pg_hba.conf entry for host» error when login to CloudCenter Manager Postgres standalone server with the use of PGAdmin tool.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

Components Used

The information in this document is based on these software versions:

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

Problem

When you try to connect the CloudCenter Postgres server with the use of pgAdmin, it fails with the «UNAUTHORIZED» error as shown in the image.

Solution

This authentication issue happens when you try to connect to the Postgres SQL server remotely other than the CloudCenter Manager server. In order to resolve this error, follow these steps:

1. Log in to Postgres SQL server with the use of ssh console.

2. cd to /var/lib/pgsql/9.6/data/.

3. Open pg_hba.conf file in an editor.

4. Add an entry of the host IP address from which you try to connect. You can input the entry of the host which you would like to provide access to as shown in the image.

5. Restart the postgres SQL server.

6. Try again in order to connect with the use of pgAdmin tool and you should be able to connect without any errors as shown in the image.

FATAL: no pg_hba.conf entry for host «fe80::1%lo0»

In my pg_hba.conf file I have this:

Maybe I’m doing it wrong?

6 Answers 6

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I had the same problem. somehow, this line was added to my /etc/hosts file:

commenting out or removing that line from /etc/hosts should fix it

I’m on OSX 10.9.3 and Postgres 9.3.4.

I’ve managed to resolve this problem in the following way:

Now add the following line to pg_hba.conf :

Oo, that’s an interesting one.

Assuming you’re connecting to localhost (you didn’t say and didn’t show your database.yml ), it appears that localhost is resolving to an IPv6 link-local address with zone index.

If you use ::1 or 127.0.0.1 it should work.

This is very likely an operating system misconfiguration or bug, so lots more detail (see comment above) should be added to the question if you want any concrete advice on that.

I bound the rails server to port 80 so that I wouldn’t have to specify a port in the url localhost:3000 during development. This appears to write fe80::1%lo0»localhost to my /etc/hosts file.

The same error occurs for me when I execute pg_dump command to take backup of my server database (external) like below

I solved it (work around) by replacing my to my actual server IP ( 10.1.0.18 ).

So the issue here is my system didn’t understand the host.

It might solve permanently when you add host in /private/etc/hosts file.

I’m trying to move my bot to an Ubuntu virtual server from Vultr but it’s having a problem connecting to the postgres database. I’ve tried editing the config from md5 to true, and host to local, etc. But those only give me different errors and also make it stop working on my original machine too. It’s working perfectly fine on my Windows machine. Here is the error I’m facing:

So I’ve tried to change this line:

and that gives me this error:

So I don’t know what else to try. I’ve been stuck on this for a while. If it’s relevant, it connects at the bottom of the bot.py file like this:

Whether ssl is True or not, the database seems to still function on my Windows machine. But I can’t get it to work on my Ubuntu virtual server.

If I edit my config to this:

Then I get a call error like this:

This is really driving me crazy. I have no idea what to do. I bought this virtual server to host my bot on but I can’t even get it to connect to the database.

When I simply type psql in the terminal, I get this error:

docker-compose install gets «no pg_hba.conf entry» #4736

Comments

javexed commented Sep 13, 2019

ISSUE TYPE

SUMMARY

Standard docker install fails to work.

ENVIRONMENT

STEPS TO REPRODUCE

EXPECTED RESULTS

A working AWX install

ACTUAL RESULTS

From the docker logs of the postgres image, I see lots of these:
no pg_hba.conf entry for host

So postgres is looking for another location? Will keep running tests to see if I can figure out where it is trying to pull from.

ADDITIONAL INFORMATION

The text was updated successfully, but these errors were encountered:

ryanpetrello commented Sep 13, 2019

@shanemcd @rooftopcellist is this related to the recent postgres10 update?

javexed commented Sep 14, 2019

Ok, got the fix, I think.
Based the solution from here: docker-library/postgres#482
Added the following line to pg_hba.conf

NOTE: no idea if this is kosher.
Then did a

javexed commented Sep 14, 2019

It looks like we should be able to fix the issue by adding the following line to
https://github.com/ansible/awx/blob/devel/installer/roles/local_docker/templates/docker-compose.yml.j2
in the postgres section

However, doing that doesn’t seem to fix the issue. Wondering if it is that issue mentioned in that ticket.
Thus, the band-aid solution is to do the above, namely manually edit the pg_hba.conf file and then restart.

treyd commented Oct 24, 2019

Has anyone successfully worked around the pg_hba.conf issue and gotten AWX to deploy on a local docker? I’ve tried but now I’m getting messages about the awx and postgres databases not existing.

rooftopcellist commented Oct 25, 2019

@treyd can you try with the latest code, and share any tracebacks you of seeing in the logs?

@javexed are you still seeing this issue?

treyd commented Oct 25, 2019

Here is the traceback in the awx_task logs:

treyd commented Oct 25, 2019

Also, when I edit pg_hba.conf to allow connections from 0.0.0.0/0 I get the following in the logs:

rooftopcellist commented Oct 25, 2019

@treyd Is this a fresh install? If it is in an upgrade scenario, my hunch is that this could be the culprit:

Some of the settings from postgresql9.6 may not be compatible with postgres10 as is.

I am trying to reproduce this locally. If it is possible for you to share your pg_hba.conf or the relevant sections, that might be useful.

treyd commented Oct 25, 2019 •

Here is my pg_hba.conf :

rooftopcellist commented Oct 25, 2019

I just did a fresh install and built images locally as you did (build.yml, then install.yml with the dockerhub line commented out in the inventory file) and it was successful.

I should mention that I deleted all old awx containers before doing so (since you are seeing postgresql10, this is probably not your issue, but it doesn’t hurt).

This is the pg_hba.conf in the resulting awx_postgres container:

Postgresql 10 does not allow passwords in plain-text for pg users iirc. You might try adding that last line to your pg_hba.conf and giving it a go. Let me know if that helps or not.

javexed commented Oct 30, 2019

Will try again and let you know.

treyd commented Oct 31, 2019

@rooftopcellist I am still getting the below error. This after completely blowing away my repo checkout, making sure there is no

gtie commented Nov 6, 2019 •

To get around the connection failure error:

This still leaves you with a missing database (or any initialization whatsoever) inside the postgres container, which is the error @treyd reported just above. Trying to work that one out.

gtie commented Nov 6, 2019

So, in addition to the above pg_hba.conf modification, what I had to do extra to get the DB initialized was:

treyd commented Nov 6, 2019

@gtie this worked for me, thanks!

Sounds like the install.yml playbook needs to do this? Or maybe this is something that should be done from the docker-compose context?

gtie commented Nov 7, 2019

The pg_hba line is conditional on the usage of docker-compose. So, that file needs to be templetized, rather than copied (as it is now), and the extra line needs to be made conditional on the type of installation.

The DB initialization needs more debugging to see how to best fix it. The commands above are a hack.

javexed commented Nov 18, 2019

Ok, redid my steps and the error is gone and AWX is installed correctly without the need for the additional hacks. Thank you!

fgierlinger commented Apr 13, 2020

I’d like to reopen this issue since exactly the error described above happened to me while trying to deploy awx on a fresh centos7. After running the install.yml playbook, the message FATAL: no pg_hba.conf appears multiple times in the awx_task container logs.

I could solve the problem by appending manually the following line in /root/.awx/pgdocker/10/data/pg_hba.conf :

w7089 commented Apr 30, 2020

Ok, got the fix, I think.
Based the solution from here: docker-library/postgres#482
Added the following line to pg_hba.conf

NOTE: no idea if this is kosher.
Then did a

Thanks, it helped

ArjonBu commented May 28, 2020

Why is this issue closed? This is happening again all the time. Tested on the latest version.

ptran32 commented Jun 15, 2020

For any reason I tried to install it on my mac with docker deployment and I hit this issue as well.

I switched to centos and I didn’t have any issues. (Using AWX release 11.2.0)

neutralrockets commented Jun 25, 2020

Happening to me with new AWX 13.0.0 release and also on macOS using docker-compose install method.

nevotheless commented Jul 3, 2020

I’m trying to install AWX 13.0.0 right now. On Mac OS as well as using docker-compose install method, as @neutralrockets did and i’m getting the same issue here. I can workaround but this issues still exists. Please consider adding a proper hba config.

iloominaty commented Jul 15, 2020

Just tried installing AWX 13.0.0 on a ubuntu 20.04 VM using docker-compose.

joefodor commented Jul 15, 2020 •

This is is happening to me on Mac OS AWX 13.0.0
2020-07-15 20:50:05,253 WARNING awx.main.dispatch.periodic periodic beat started
Traceback (most recent call last):
File «/var/lib/awx/venv/awx/lib/python3.6/site-packages/django/db/backends/base/base.py», line 217, in ensure_connection
self.connect()
File «/var/lib/awx/venv/awx/lib/python3.6/site-packages/django/db/backends/base/base.py», line 195, in connect
self.connection = self.get_new_connection(conn_params)
File «/var/lib/awx/venv/awx/lib/python3.6/site-packages/django/db/backends/postgresql/base.py», line 178, in get_new_connection
connection = Database.connect(**conn_params)
File «/var/lib/awx/venv/awx/lib/python3.6/site-packages/psycopg2/init.py», line 126, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: FATAL: no pg_hba.conf entry for host «172.22.0.4», user «awx», database «awx», SSL off

The above exception was the direct cause of the following exception:

Psycopg2 reporting pg_hba.conf error

I’ve run into a weird situation while trying to use PostgreSQL and Psycopg2. For some reason, every time I attempt to connect to the postgre database via python, I get the following error:

Naturally, I checked pg_hba.conf to see what the issue was, but everything appeared to be configured correctly as far as I can see:

pg_hba.conf:

In addition, I’ve found that I can connect to the database via psql as I would expect:

Anyone have any ideas as to what could be going on here? Thanks in advance!

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Typical explanations include:

You are connecting to the wrong server.
Is the DB server running on the same host as Python does?

Use pg_ctl or pg_ctlcluser on Debian and derivatives for that.

Or, on modern Linux installations with systemd (incl. Debian & friends), typically:

Or, if there are multiple installations, check with:

And then realod the one you want with something like:

I recently got into this same issue and I found the solution for this problem.

System:

Error:

django.db.utils.OperationalError: FATAL: no pg_hba.conf entry for host «10.0.0.1», user «your_user», database «your_db», SSL off

Solution:

I am trying to run migrations on my Nodejs application hosted on Heroku using the Heroku free Postgres database.

I am using Sequelize as my ORM.This is my configuration for the production connection.

When I use the above configuration, I get the following error: no pg_hba.conf entry for host «000.000.000.0», user «yyyyyyyyyyyyyy», database «xxxxxxxxxxxxx», SSL off

However when I add the options below to the config, I get a self-signed certificate error.

Please, how do I resolve this?

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Change your dialectOptions to:

As explained in this related answer, setting rejectUnauthorized: false is a bad idea because it allows you to create non-encrypted connections to your database and can, thus, expose you to MITM attack (man-in-the-middle attacks).

A better solution is to give your Postgres client the CA that you want it to use. In my case it was a CA used by AWS RDS for the North Virginia region (us-east-1). I downloaded the CA from this AWS page, placed it in the same directory as the file I wanted to use connect to the DB and then modified my config to:

FATAL: no pg_hba.conf entry for host «fe80::1%lo0»

In my pg_hba.conf file I have this:

Maybe I’m doing it wrong?

6 Answers 6

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I had the same problem. somehow, this line was added to my /etc/hosts file:

commenting out or removing that line from /etc/hosts should fix it

I’m on OSX 10.9.3 and Postgres 9.3.4.

I’ve managed to resolve this problem in the following way:

Now add the following line to pg_hba.conf :

Oo, that’s an interesting one.

Assuming you’re connecting to localhost (you didn’t say and didn’t show your database.yml ), it appears that localhost is resolving to an IPv6 link-local address with zone index.

If you use ::1 or 127.0.0.1 it should work.

This is very likely an operating system misconfiguration or bug, so lots more detail (see comment above) should be added to the question if you want any concrete advice on that.

I bound the rails server to port 80 so that I wouldn’t have to specify a port in the url localhost:3000 during development. This appears to write fe80::1%lo0»localhost to my /etc/hosts file.

The same error occurs for me when I execute pg_dump command to take backup of my server database (external) like below

I solved it (work around) by replacing my to my actual server IP ( 10.1.0.18 ).

So the issue here is my system didn’t understand the host.

It might solve permanently when you add host in /private/etc/hosts file.

Heroku Postgres: «psql: FATAL: no pg_hba.conf entry for host»

There are a number of Heroku CLI Postgres commands that all return the same error. For example:

At least one of these commands has worked in the past, but does not now.

The database appears to be working fine otherwise. I can access it via my application’s interfaces.

I do not see a way to toggle SSL in the Heroku Postgres dashboard. What could be causing this and how could I fix it?

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I solved it by setting PGSSLMODE on Heroku to require. This tells Postres to default to SSL. On the command line this can be done via the following command.

The error basically says that you are trying to connect to a database instance without using SSL connection, but the server is setup to reject connection without SSL connection.

Heroku Postgres: «psql: FATAL: no pg_hba.conf entry for host»

There are a number of Heroku CLI Postgres commands that all return the same error. For example:

At least one of these commands has worked in the past, but does not now.

The database appears to be working fine otherwise. I can access it via my application’s interfaces.

I do not see a way to toggle SSL in the Heroku Postgres dashboard. What could be causing this and how could I fix it?

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I solved it by setting PGSSLMODE on Heroku to require. This tells Postres to default to SSL. On the command line this can be done via the following command.

The error basically says that you are trying to connect to a database instance without using SSL connection, but the server is setup to reject connection without SSL connection.

no pg_hba.conf entry for host «x.x.x.x», user » «, database » «, SSL off

I’ve seen many incarnations of this issue on Stack Overflow and the like over the past few hours, but none of the recommendations seem to be helping me. I am building an app using Node, Express, Heroku, and Postgresql, and when I tried to make my first migration, I ran the following commands:

When I ran this, I got an error that reads:

is my computer’s ip address, is my postgres database’s username that can be seen from the Heroku console, and is my postgres database’s name which can be seen on that same console, if that info is helpful whatsoever. From what I understand, this means I need to add a line to my pg_hba.conf file, which is located at /usr/local/var/postgres. I tried many different lines based on suggestions and my own understanding of the format used in this configuration file, but alas, that error persisted. This is a shame too because it really seems host all all all trust should have worked (even if that is bad practice from a security standpoint). I have also been restarting postgres before trying to migrate again using the following command:

Any help on this issue would be greatly appreciated!

how to fix no pg_hba.conf entry for host «::1»

I’m standing up a new application and having some issues with host based authentication. I know there are other posts out there (espec this one) but nothing I try seems to work.

no pg_hba.conf entry for host «::1», user «root», database «db_name_here», SSL off

My pg_hba.conf file looks like:

I have a note to myself from the past where I said the following worked:

even that didn’t work, same error.

I’ve read the postgresql docs, and while the helped explain what was going on, (and made me try hostnossl, to no avail) I’m still getting the same error.

Do you see my mistake?

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Your pg_hba.conf entry is missing the netmask; a plain IP address is a syntax error. This one should work:

Make sure you reload the database with

and check the log file for errors (that is important, as a syntactically wrong file won’t be loaded).

The alternative is to enable SSL on the server side and use it for the local connection.

The fastest way to connect would be via Unix sockets (if you are not on Windows or use the JDBC driver), perhaps that is the best thing to do.

Heroku Postgres: «psql: FATAL: no pg_hba.conf entry for host»

There are a number of Heroku CLI Postgres commands that all return the same error. For example:

At least one of these commands has worked in the past, but does not now.

The database appears to be working fine otherwise. I can access it via my application’s interfaces.

I do not see a way to toggle SSL in the Heroku Postgres dashboard. What could be causing this and how could I fix it?

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I solved it by setting PGSSLMODE on Heroku to require. This tells Postres to default to SSL. On the command line this can be done via the following command.

The error basically says that you are trying to connect to a database instance without using SSL connection, but the server is setup to reject connection without SSL connection.

Heroku Postgres: «psql: FATAL: no pg_hba.conf entry for host»

There are a number of Heroku CLI Postgres commands that all return the same error. For example:

At least one of these commands has worked in the past, but does not now.

The database appears to be working fine otherwise. I can access it via my application’s interfaces.

I do not see a way to toggle SSL in the Heroku Postgres dashboard. What could be causing this and how could I fix it?

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I solved it by setting PGSSLMODE on Heroku to require. This tells Postres to default to SSL. On the command line this can be done via the following command.

The error basically says that you are trying to connect to a database instance without using SSL connection, but the server is setup to reject connection without SSL connection.

подключиться к серверу PostgreSQL: FATAL: нет записи в pg_hba.conf для хоста

Здравствуйте, я пытаюсь запустить отправленный мне сайт, но после этого появилась эта ошибка

после Google это говорит, что мне просто нужно добавить запись в файле pg_hba.conf для этого конкретного пользователя. это мой файл pg_hba.conf.

но после этого ошибка все еще сохраняется. Я перезагружал свой сервер XAMPP несколько раз, но никаких изменений не появляется. заранее спасибо

Добавьте или отредактируйте следующую строку в вашем postgresql.conf :

Перезапустите Postgresql после добавления этого с помощью service postgresql restart или эквивалентной команды для вашей установки.

Это решение работает для IPv4 / IPv6

добавить в финал

а затем перезапустите сервис postgresql

Я решил это следующим образом:

Добавлена строка, как показано ниже pg_hba.conf :

Fresh Postgres 9.5 установить, Ubuntu.

Ключ был локальным типом соединения, так как psql использует соединение с сокетом домена.

Heroku Postgres: «psql: FATAL: no pg_hba.conf entry for host»

There are a number of Heroku CLI Postgres commands that all return the same error. For example:

At least one of these commands has worked in the past, but does not now.

The database appears to be working fine otherwise. I can access it via my application’s interfaces.

I do not see a way to toggle SSL in the Heroku Postgres dashboard. What could be causing this and how could I fix it?

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I solved it by setting PGSSLMODE on Heroku to require. This tells Postres to default to SSL. On the command line this can be done via the following command.

The error basically says that you are trying to connect to a database instance without using SSL connection, but the server is setup to reject connection without SSL connection.

Unable to connect to Heroku postgres from outside of Heroku #278

Comments

thiago-soliveira commented Feb 11, 2017

In order to connect to Heroku postgres from outside of Heroku we need to use SSL.

So, I’m getting the following message when trying to connect typeorm to the Heroku postgres.

I believe this is happening because the postgres driver is trying to connect without SSL. If I’m correct, how can I tell the sql driver to use SSL.

The text was updated successfully, but these errors were encountered:

pleerock commented Feb 11, 2017

Solution is here. To do so in typeorm you need to provide option in special «extra» section of connection options:

AngelMunoz commented Nov 22, 2017

pleerock commented Nov 24, 2017

You need to set

AngelMunoz commented Nov 24, 2017

thanks it did work

pie6k commented Mar 11, 2018

N-CP commented Jun 27, 2018

I m trying to connect postgresql heroku to oracle sql developer. But i m getting the below error

message»: «no pg_hba.conf entry for host «xxx», user «xxx», database «xxx», SSL off»

what could be the solution?
can anybody help me in this pls??

jmaicaaan commented Jul 20, 2018

@N-CP, what is your ormconfig looks like?

a1300 commented Jan 17, 2019

For me it worked with:

yaroslav-ilin commented Mar 31, 2019

I believe the original issue and the solutions (both JSON & env) has to be documented.

Would such pull request for docs website be accepted?

Kononnable commented Apr 6, 2019

SSL options are already documented (https://github.com/typeorm/typeorm/blob/master/docs/connection-options.md). However if you find a good place to remind about that(common problem?) PR will be accepted.

AllanPamplona-zz commented Apr 8, 2019

Also PGSSLMODE=require solves this problem.

rakeshta commented Sep 25, 2019

worked for me too.

idudinov commented Nov 26, 2019 •

hi there!
still don’t able to connect to remote Heroku Postgres server from local machine, my config looks like:

also tried to set up PGSSLMODE=require as env var.

TypeORM in package.json:
«typeorm»: «0.2.20»

getting the error:

not sure what certificate should I use, or can I bypass it somehow?

thanks in advance!

idudinov commented Nov 26, 2019 •

jeez it fails on Heroku as well!

UPDATE: sorry, false alarm! it’s actually node-postgres issue: brianc/node-postgres#2009

JakeSidSmith commented Apr 16, 2020

not sure what certificate should I use, or can I bypass it somehow?

I’ve just run into this issue and it seems that node-postgres have added an option to disable rejecting unauthorized connections. I don’t think this is safe to run in production though. I’m just using it to run my migrations.

I believe the ideal solution is to get a new SSL certificate, but for now I have:

aliskhanoff commented Jun 27, 2020

not sure what certificate should I use, or can I bypass it somehow?
thanks in advance!

I believe the ideal solution is to get a new SSL certificate, but for now I have:

it works for me. Thanks!

italodeandra commented Jul 3, 2020

What fixed for me while using Postgres from Heroku was only adding the following environment variable:

Haple commented Aug 21, 2020

What worked for me:

kvarela commented Oct 31, 2020

Yes, this for me also, AND I had to REMOVE:

altschuler commented Jan 4, 2021

agilatakishiyev commented Jan 13, 2021

not sure what certificate should I use, or can I bypass it somehow?
thanks in advance!

I believe the ideal solution is to get a new SSL certificate, but for now I have:

Typescript «error: no pg_hba.conf entry for host «x», user «x», database «x», SSL off»

Setup

I’m currently using Kubernetes to manage my NodeJS services.

Every NodeJS service has its own PostgreSQL database, I’m using TypeORM to access each database. Everything worked fine until I converted my Kubernetes Deployment to a StatefulSet. I did this because I wanted my databases to keep their data, even after being shut down.

Problem

The NodeJS service ( confirmation-deployment- ) which represents a REST API can’t connect to the PostgreSQL database ( confirmation-postgres-statefulset- )

Error

The logs return this error: error: no pg_hba.conf entry for host «x», user «x», database «x», SSL off

I’m basically stuck at the moment. The first error tells me to convert to , while the other error tells me to do the opposite. I’ve no idea why this happens, all of this started when I converted the Deployment to a StatefulSet inside Kubernetes.

If I can take a guess, it’s perhaps an internal cluster network issue inside Kubernetes? Anyway, I’m not familiar with those errors.

Heroku Postgres: «psql: FATAL: no pg_hba.conf entry for host»

There are a number of Heroku CLI Postgres commands that all return the same error. For example:

At least one of these commands has worked in the past, but does not now.

The database appears to be working fine otherwise. I can access it via my application’s interfaces.

I do not see a way to toggle SSL in the Heroku Postgres dashboard. What could be causing this and how could I fix it?

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I solved it by setting PGSSLMODE on Heroku to require. This tells Postres to default to SSL. On the command line this can be done via the following command.

The error basically says that you are trying to connect to a database instance without using SSL connection, but the server is setup to reject connection without SSL connection.

Postgresql error, «no pg_hba.conf entry»

I am a newbie to programming. I am building a rails app and now want to push it to Heroku. I followed Heroku’s guidelines for converting my database from sqlite 3 to postresql. After doing that I get this error when I try to migrate or even check out my app on local host

«PG::ConnectionBad: FATAL: no pg_hba.conf entry for host «[local]», user «keemtaker», database «tuma_database_development», SSL off»

I checked out previous answers to this same problem but it is so confusing and overwhelming for me. It would be nice if I can get a step by step guide to solve this error. I have used PostgreSQL before with no issues. This is how my gemfile looks like

In my database.yml, i have

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

According to Heroku Support this is not an error coming from your Rails application but from someone malicious trying to authenticate to your PostgreSQL database:

I’m seeing failed connection attempts in my Heroku Postgres logs, but I’m not creating these connections and they come from an IP address that I don’t recognize. It looks like someone might be trying to hack my database:

sql_error_code = 28000 FATAL: no pg_hba.conf entry for host «122.180.247.11», user «postgres», database «postgres», SSL off

Resolution

These errors indicate a failed login attempt was made to your database, which means that the connection wasn’t established.

pg_hba.conf rejects connection for host «myip»

Information: I’m accessing an appliance database with the correct user, password, dbname (because it is on their document).

However, after I configure my IP to the pg_hba.conf I did restart PostgreSQL on services.msc but the error still there.

I had already restarted my PC but the error still there.

What should I do?

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Your pg_hba file seems to be on point, and you said that you had restarted the postgres service.

May I ask, which postgres service did you restart? The server’s or the client’s?

The pg_hba file is a server config. Therefore, the server must be restarted for it to take effect.

You can check hba_file value in postgresql.conf if you have specified separately and try to reload the configuration. Also check you have correct entry of IP.

Database server restarted successfully it means you have no configuration errors.

I hope help with my case. (I know this is an old case)

Couple a weeks ago I faced same error but was weird ’cause I had been working well for severals months. After do double checks a realize all config was ok, I read a post with a warning. And that was we were hacked and attacker added these 3 lines before all comments in the pg_hba.conf file.

after delete first two lines, all connections were possible. Obviously security team in my company was alerted and vulnerability scan was performed to discard some other damages.

Azure Database for PostgreSQL server: no pg_hba.conf entry for host

In my Azure portal I created the resource «Azure Database for PostgreSQL server». I set up the firewall to enable two Virtual Networks (in order to allow the correct functioning of two applications) and the IP address of my local computer (in order to be able to work on the database using DBeaver as client). This has worked for several months although, since I have a dynamic IP address, I often have to change the enabled address. Now I’m trying to update it but, when I try to connect to the database via DBeaver, I get the following error:

FATAL: no pg_hba.conf entry for host «XX.XX.XX.XX», user «myuser», database «mydatabase», SSL on

where «XX.XX.XX.XX» is exactly the IP address I have enabled in Azure.

I tried to install a second Client (pgAdmin) but I get the same error. Also, since my applications that use the database seem to work properly, I tried to verify the connection data that I use in DBeaver (host, database, user, password) but they are all correct.

In Azure, in the «Connection security» tab of my database (see image below) I read the following warning:

Some network environments may not report the actual public-facing IP address needed to access your server. Contact your network administrator if adding your IP address does not allow access to your server.

So changing the IP address has no effect? How can I solve the problem?

So I’ve tried to change this line:

and that gives me this error:

So I don’t know what else to try. I’ve been stuck on this for a while. If it’s relevant, it connects at the bottom of the bot.py file like this:

Whether ssl is True or not, the database seems to still function on my Windows machine. But I can’t get it to work on my Ubuntu virtual server.

If I edit my config to this:

Then I get a call error like this:

This is really driving me crazy. I have no idea what to do. I bought this virtual server to host my bot on but I can’t even get it to connect to the database.

When I simply type psql in the terminal, I get this error:

“FATAL: no pg_hba.conf entry” – How to fix the PostgreSQL error

by Arya MA | May 31, 2021

While connecting to PostgreSQL, users often notice the error “FATAL: no pg_hba.conf entry”.

As a part of our Server Management Service, we help our customers to fix PostgreSQL-related errors regularly.

Today, let us discuss the possible reasons and fixes for the error.

What is “FATAL: no pg_hba.conf entry” error

Connecting to PostgreSQL often triggers the error as shown below:

This error generally triggers due to incomplete entries in the pg_hba.conf file. Generally, this configuration file controls the client authentication and is stored in the database cluster’s data directory.

The general format of the pg_hba.conf file contains a set of records, one per line. A record contains a number of fields separated by spaces and/or tabs. Fields can contain white space, but we need to quote the field value.

Each record specifies a connection type, a client IP address range, a database name, a user name, and the authentication method for connections matching these parameters.

Further, the first record with a matching connection type, client address, requested database, and user name is used to perform authentication. There is no “fall-through” or “backup” : if one record is chosen and the authentication fails, subsequent records are not considered. If no record matches, access is denied.

How to fix “FATAL: no pg_hba.conf entry” error

1. Log in to Postgres SQL server with the use of ssh console.

2. Now, move to the data directory with the cd command.

3. Then, open pg_hba.conf file in an editor.

4. Add an entry of the host IP address from which we try to connect. We can input the entry of the host to which we would like to provide access to:

5. Then, restart the postgres SQL server.

6. Try again in order to connect with the use of pgAdmin tool and we should be able to connect without any errors.

[Need help to fix PostgreSQL error? We are available 24*7]

Conclusion

In short, the “no pg_hba.conf entry” can happen due to missing entries in the configuration file. Today, we saw how our Support Engineers fix this error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

Postgresql error, «no pg_hba.conf entry»

«PG::ConnectionBad: FATAL: no pg_hba.conf entry for host «[local]», user «keemtaker», database «tuma_database_development», SSL off»

In my database.yml, i have

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

According to Heroku Support this is not an error coming from your Rails application but from someone malicious trying to authenticate to your PostgreSQL database:

sql_error_code = 28000 FATAL: no pg_hba.conf entry for host «122.180.247.11», user «postgres», database «postgres», SSL off

Resolution

These errors indicate a failed login attempt was made to your database, which means that the connection wasn’t established.

org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host Linux error that works on Windows

I have looked at many (too many) similar questions here and tried over and over to solve this one but I can’t quite get it to resolve.

I have a java code that connects to a PostGreSQL server on a RHEL 8.2 box to query and return a value. When I run it on my Windows 10 laptop; it works with no issues. However, when I run it locally on the Linux box it fails with the dreaded org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host.

The java code is made by a ETL software called Talend; and the code is run on Linux by RunDeck.

To make matters more confusing, I can login on Linux as the postgres user and use the psql interface to connect to the db with the same host, port, db, and user I’m using in Java without error-

I have checked the server settings, the pg_hba.conf file, the user permissions, the log files and tried changing all of the above to get some sort of return; all to no avail.

I have added to pg_hba.conf:

I have tried multiple connection modifiers like:

OS NAME : Linux RHEL 8.2

NAME : OpenJDK 64-Bit Server VM

VENDOR : Amazon.com Inc.

Under server > properties > SSL

SSL Mode: Prefer

Client Cert: [blank]

Client Cert Key: [blank]

Root Cert: [blank]

Cert Rev List: [blank]

SSL compression?: no

UPDATE: Here is a much of the java error message as I can share; given some of the restrictions on what I can post;

Update 2: Entry from this mornings logs at /data_folder/log after trying again and getting the same error

From the postgresql.conf file:

After doing some more searching, I have found that the default for the postgres logging isn’t verbose; so this is the verbose part:

I have gotten this error even after the following updates-

update to the postgresql.conf file:

updated the log level in the postgresql.conf file to

updated the pg_hba.conf file to start with:

also updated the connection params with-

According to postgres this is supposed to stop any and all SSL issues and just let the connections through-

«A non-validating connection is established via a custom SSLSocketFactory class that is provided with the driver. Setting the connection URL parameter sslfactory=org.postgresql.ssl.NonValidatingFactory will turn off all SSL validation.»

Logging settings from postgresql.conf file:

I made edits to the logging part of the config, and now have a lot of output from the log

new logging settings:

I couldn’t paste the error log here because after making it verbose it was very long- so I made a gist

I removed the Gist because the peeps here helped me find my error:

FATAL: no pg_hba.conf entry for host «::1» trying to connect to postgresql server over ssh tunnel

I’m trying to connect to a postgresql server with java, over an SSH tunnel. I do not have administrator access to the postgresql server so I can’t modify any setting.

When I run it, it correctly creates the two ssh connections, but I get this error from the postgre:

FATAL: no pg_hba.conf entry for host «::1», user «taschinfed», database «taschinfed», SSL off at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:473) at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:205) at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49) at org.postgresql.jdbc.PgConnection.(PgConnection.java:195) at org.postgresql.Driver.makeConnection(Driver.java:452) at org.postgresql.Driver.connect(Driver.java:254) at java.sql.DriverManager.getConnection(DriverManager.java:664) at java.sql.DriverManager.getConnection(DriverManager.java:247) at SSHConnection.connect(SSHConnection.java:65) at SSHConnection.(SSHConnection.java:54) at Main.main(Main.java:10)

I don’t know what to do

Edit: I can easily access the database through windows power shell, by creating an ssh connection to the first domain, and another ssh connection from the first domain to the second domain, using then the psql command. This means that the ssh connections have no problem, and in fact I can reach the server from my java code, but I don’t understand what does that error message means.

FATAL: no pg_hba.conf entry for host «fe80::1%lo0»

In my pg_hba.conf file I have this:

Maybe I’m doing it wrong?

6 Answers 6

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I had the same problem. somehow, this line was added to my /etc/hosts file:

commenting out or removing that line from /etc/hosts should fix it

I’m on OSX 10.9.3 and Postgres 9.3.4.

I’ve managed to resolve this problem in the following way:

Now add the following line to pg_hba.conf :

Oo, that’s an interesting one.

Assuming you’re connecting to localhost (you didn’t say and didn’t show your database.yml ), it appears that localhost is resolving to an IPv6 link-local address with zone index.

If you use ::1 or 127.0.0.1 it should work.

This is very likely an operating system misconfiguration or bug, so lots more detail (see comment above) should be added to the question if you want any concrete advice on that.

I bound the rails server to port 80 so that I wouldn’t have to specify a port in the url localhost:3000 during development. This appears to write fe80::1%lo0»localhost to my /etc/hosts file.

The same error occurs for me when I execute pg_dump command to take backup of my server database (external) like below

I solved it (work around) by replacing my to my actual server IP ( 10.1.0.18 ).

So the issue here is my system didn’t understand the host.

It might solve permanently when you add host in /private/etc/hosts file.

Heroku Postgres: «psql: FATAL: no pg_hba.conf entry for host»

There are a number of Heroku CLI Postgres commands that all return the same error. For example:

At least one of these commands has worked in the past, but does not now.

The database appears to be working fine otherwise. I can access it via my application’s interfaces.

I do not see a way to toggle SSL in the Heroku Postgres dashboard. What could be causing this and how could I fix it?

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I solved it by setting PGSSLMODE on Heroku to require. This tells Postres to default to SSL. On the command line this can be done via the following command.

The error basically says that you are trying to connect to a database instance without using SSL connection, but the server is setup to reject connection without SSL connection.

Heroku Postgres: «psql: FATAL: no pg_hba.conf entry for host»

There are a number of Heroku CLI Postgres commands that all return the same error. For example:

At least one of these commands has worked in the past, but does not now.

The database appears to be working fine otherwise. I can access it via my application’s interfaces.

I do not see a way to toggle SSL in the Heroku Postgres dashboard. What could be causing this and how could I fix it?

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I solved it by setting PGSSLMODE on Heroku to require. This tells Postres to default to SSL. On the command line this can be done via the following command.

The error basically says that you are trying to connect to a database instance without using SSL connection, but the server is setup to reject connection without SSL connection.

Heroku Postgres: «psql: FATAL: no pg_hba.conf entry for host»

There are a number of Heroku CLI Postgres commands that all return the same error. For example:

At least one of these commands has worked in the past, but does not now.

The database appears to be working fine otherwise. I can access it via my application’s interfaces.

I do not see a way to toggle SSL in the Heroku Postgres dashboard. What could be causing this and how could I fix it?

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I solved it by setting PGSSLMODE on Heroku to require. This tells Postres to default to SSL. On the command line this can be done via the following command.

The error basically says that you are trying to connect to a database instance without using SSL connection, but the server is setup to reject connection without SSL connection.

PostgreSQL FATAL: no pg_hba.conf entry for host ipv6

При создании новой базы 1C на сервере PostgreSQL в OS Windows Server 2008 R2 система вываливает ошибку :

Ошибка при создании информационной базы 1С:

Сервер баз данных не обнаружен

FATAL: no pg_hba.conf entry for host «fe80::2cc8:3744:3f57:fe94/128», user «postgres», database «template1»

Идем в файл pg_hba.conf (находится в папке установленного PostgreSQL) и добавляем строчку:

После чего перезапускаем PostgreSQL.

Как включить интерфейс такси в 1С

Редактор Битрикс, выбираем IDE

CodeLobster IDE – бесплатный PHP, HTML, CSS, JavaScript редактор

такой подход решает проблему только до перезагрузки, пока нашел выход отключить ipv6 и её вспомогательную службу.

Спасибо ВАМ добрые люди!
Спасли от инфаркта человека, выполняющего не свойственную ему роль Сисадмина!
Удалил с сервера роль Hyper-V и 1С начала выдавать эту ошибку!

problem with pg_hba #951

Comments

binooetomo commented Jan 26, 2019

Below is patroni generated pg_hba on my master node (192.168.5.81):

local all all trust
host all all 127.0.0.1/32 trust
host all all ::1/128 trust
local replication all trust
host replication all 127.0.0.1/32 trust
host replication all ::1/128 trust
host replication repl 192.168.5.0/24 md5
host all dba all md5

I try to start my second node (192.168.5.82), and got this error message :

2019-01-26 12:10:05,392 INFO: Local timeline=None lsn=None
2019-01-26 12:10:05,398 ERROR: Can not fetch local timeline and lsn from replication connection
Traceback (most recent call last):
File «/var/lib/pgsql/.local/share/virtualenvs/patroni-QGg7MClq/lib/python3.6/site-packages/patroni/postgresql.py», line 1273, in _get_local_timeline_lsn_from_replication_connection
with self._get_replication_connection_cursor(**self._local_replication_address) as cur:
File «/usr/lib64/python3.6/contextlib.py», line 81, in enter
return next(self.gen)
File «/var/lib/pgsql/.local/share/virtualenvs/patroni-QGg7MClq/lib/python3.6/site-packages/patroni/postgresql.py», line 1257, in _get_replication_connection_cursor
connect_timeout=3, options=’-c statement_timeout=2000′) as cur:
File «/usr/lib64/python3.6/contextlib.py», line 81, in enter
return next(self.gen)
File «/var/lib/pgsql/.local/share/virtualenvs/patroni-QGg7MClq/lib/python3.6/site-packages/patroni/postgresql.py», line 1246, in _get_connection_cursor
with psycopg2.connect(**kwargs) as conn:
File «/var/lib/pgsql/.local/share/virtualenvs/patroni-QGg7MClq/lib/python3.6/site-packages/psycopg2/init.py», line 130, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: FATAL: no pg_hba.conf entry for replication connection from host «192.168.5.82», user «repl», SSL off

2019-01-26 12:10:05,402 INFO: no action. i am a secondary and i am following a leader
^C2019-01-26 12:10:12,971 INFO: Lock owner: patroni-ceph-node1; I am patroni-ceph-node2

Kindly please give me some clue to fix this problem
Sincerely
-bino-

The text was updated successfully, but these errors were encountered:

no pg_hba.conf entry for host «10.1.1.91», user «user» database «testing», SSL off

I’ve come across different versions of this same issue on stackoverflow and on this forum. I’ve tried the recommendations posted on these forums but I am still unable to connect to a database. I’ve run out of leads to try and I’m hoping someone can explain to me what is happening and why I am unable to connect. The context of my question follows:

I pg_dumped a database on a server host named test-crawl-1 and have pg_restored the database onto a new server host named test-qa-db where it resides with 4 other databases. I’ve changed the database. yml file to look like this:

Next, because of the error I’m receiving I tried the following, I sshed into a VM named test-utility-1 and modified the pg_hba.conf file there to reflect the following:

Then I tried this:

And then I tried to implement in the postgresql.conf file:

I pretty much tried that line with the above variations but I have still yet been able to make it work. Is there anything that I’m missing. I’m not sure what else is there to try. Help would be appreciated thank you.

I forgot to mention that I also hard coded the database, user, and Ip address into the corresponding fields but the SSl but the error still persists.

Postgres pg_hba.conf

There is server being set-up for one of my client, after installations of postgres when we run the server we are encountering the error below. When I goggled for it there were a few solutions available but none worked for me, could you look into it and say what’s happening.

My pg_hba.conf file:

Thanks in Advance.

4 Answers 4

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I figured it out myself, though it took a long time. The solution was simple, I just had to add an entry in the pg_hba.conf file for that particular user. This is what I did:

Hope this helps others. 🙂

I think that the just configuration is:

If you want connect by other network use:

use the two octet 192.159.0.0 for example

I reply here cause I can’t comment your solution.

It is not mandatorry to add the entry to that specific user only. You can replace the option «samerole» with the database or all.

I’m seeing that 2 of the lines that you have are collisioning each other.

In this case, last line wins, so be careful to add unexpected behaviors on your access methods. If you want to ask the password for the universe on local, you must delete the last line.

no pg_hba.conf entry for replication connection from host

I have been configuring a slave server that needs to connect to the host. Both the master and the standby servers have a pg_hba.conf that looks like this:

This should allow access from every IP address, right? Evidently, though, the standby server cannot connect using the REP_USER credentials via primary_conninfo

I know this doesn’t work because I never see in my logs:

..and I cannot connect to the master server via psql either:

Why? I don’t get it.

1 Answer 1

When doing this:

The value replication specifies that the record matches if a replication connection is requested (note that replication connections do not specify any particular database). Otherwise, this is the name of a specific PostgreSQL database.

So if you expected that this line:

As for the other line:

If the real problem is the replication not happening, I don’t think psql is very useful to test this since psql must connect to a specific database before doing anything useful, whereas the replication process must not and does not.

PostgreSQL pg_hba.conf Issue

In pg_hba.conf, I have

I am using pgAdminIII, trying create a «New Server Registration». When I connect to (localhost), it works fine. But when I change the host to the actual workstation name it says:

Any help on this would be highly appreciated.

6 Answers 6

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

This is the issue of PostgreSQL installations on Windows computers having IPv6 enabled. Temporary workaround would be passing paramter «-h 127.0.01» as described in this article.

This has been answered by other user here, but I want to show the answer here to make more clear for others:

In pg_hba.conf, add your ipv6 address like this:

fe80::c81c:9e9c:6570:d0bf is your ipv6 address.

Note that the interface enumeration code that samehost and samenet rely on is very platform-dependent. (There are currently 5 separate implementations for different platforms.) So what works for one setup might not work somewhere else.

That said, the analogous setup works for me on Linux, that is, I can connect to the database server on the local host using

after setting listening_addresses and samenet appropriately.

So it’s conceivable that the interface enumeration code in Windows somehow fails to include the link-local addresses.

If you have isolated this problem enough, I would send a bug report to PostgreSQL to analyze the issue further.

Connect to SSL database #43

Comments

chrisdl commented Jan 25, 2019

I’m having an issue trying to connect o an SSL enabled postgres database, which does not live locally.

FATAL: no pg_hba.conf entry for host » «, user » «, database » «, SSL off

The text was updated successfully, but these errors were encountered:

willvincent commented Jan 26, 2019

Interesting.. I don’t have an ssl enabled server to test against at the moment, but if I try appending the ssl=true param to the end of the connect string, I get the sort of message I expect.

chrisdl commented Jan 28, 2019

I think this may be a heroku specific issue. but I tried it with bdash (https://www.bdash.io/) just to make sure I wasn’t eating crazy pills, and I could connect to it just fine.

I would like to keep using postbird.

osmuse commented Jan 29, 2019

I am having the same issue. How do you specify SSL in the standard connection tab?

Paxa commented Jan 30, 2019

What OS do you use?

On MacOS postbird will use https://github.com/brianc/node-pg-native and on Linux with Windows https://github.com/brianc/node-postgres (I can only many static build of libpq for mac)

Change ssl=verify-full to ssl=1 and try to connect via URL form

For now there is no way to specify ssl via normal form, only with «Connect URL»

This is defiantly a bug, will try to fix it

chrisdl commented Jan 31, 2019

VEEV-USA commented Apr 25, 2019

How do I fix this?

Paxa commented May 6, 2019

Can you please try with new version? I made small improvements for enabling ssl

chrisdl commented May 6, 2019

Is there some other configuration I should try?

Paxa commented Jun 16, 2019

chrisdl commented Jun 18, 2019

@Paxa with the version provided in #43 (comment) the ssl=true at the end of the connection string worked!

thiagofasano commented Jul 16, 2019

I have the same error =( connection Digital Ocean error: SSL off.

chrisdl commented Jul 17, 2019

@thiagofasano you could rock it cutting edge style and run the package from #43 (comment)

@Paxa I feel like this issue is actually resolved now, or do you want to wait for it to get released?

thiagofasano commented Jul 22, 2019

@chrisdl not work.. ssl=true

adsteel commented Feb 4, 2020

stevennyman commented Jul 19, 2020

btd1337 commented Dec 19, 2020 •

The problem in connect via URL is don’t save the connection.

Heroku message

Applications outside of the Heroku network must support and enable SSL to connect to a Heroku Postgres database. Most clients connect over SSL by default, but sometimes it’s necessary to add the sslmode=require query parameter to your database URL before connecting.

Be sure to append the sslmode=require parameter to your database’s URL from code, rather than by editing the value of your DATABASE_URL config var directly. Various automated events (such as a failover) can change the value of the config var, which overwrites any edits you make.

Is any way to connect in standard mode adding ssl?

Postgresql error, «no pg_hba.conf entry»

«PG::ConnectionBad: FATAL: no pg_hba.conf entry for host «[local]», user «keemtaker», database «tuma_database_development», SSL off»

In my database.yml, i have

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

According to Heroku Support this is not an error coming from your Rails application but from someone malicious trying to authenticate to your PostgreSQL database:

sql_error_code = 28000 FATAL: no pg_hba.conf entry for host «122.180.247.11», user «postgres», database «postgres», SSL off

Resolution

These errors indicate a failed login attempt was made to your database, which means that the connection wasn’t established.

Seeing «FATAL: no pg_hba.conf entry» errors in Postgres

Issue

I’m seeing «no pg_hba.conf entry for host» errors:

Resolution

«FATAL: no pg_hba.conf entry for host» errors indicate that there was a failed authentication attempt to the database, so the connection couldn’t be established. This can happen because of different reasons:

The authentication failed because the user/password credentials were invalid: ( (user «xxxx», database «yyyy») ). This could happen if you’re trying to connect to the database using wrong or revoked credentials. (See also: Why am I seeing connection errors for my Heroku Postgres database from an unexpected IP address?).

The authentication failed because the connection didn’t use SSL encryption: ( SSL off ). All Heroku Postgres production databases require using SSL connections to ensure that communications between applications and the database remain secure. If your client is not using SSL to connect to your database, you would see these errors even if you’re using the right credentials to connect to it.

Ask on Stack Overflow

Engage with a community of passionate experts to get the answers you need

Heroku Support

Create a support ticket and our support experts will get back to you

PostgreSQL pg_hba.conf Issue

In pg_hba.conf, I have

I am using pgAdminIII, trying create a «New Server Registration». When I connect to (localhost), it works fine. But when I change the host to the actual workstation name it says:

Any help on this would be highly appreciated.

6 Answers 6

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

This is the issue of PostgreSQL installations on Windows computers having IPv6 enabled. Temporary workaround would be passing paramter «-h 127.0.01» as described in this article.

This has been answered by other user here, but I want to show the answer here to make more clear for others:

In pg_hba.conf, add your ipv6 address like this:

fe80::c81c:9e9c:6570:d0bf is your ipv6 address.

That said, the analogous setup works for me on Linux, that is, I can connect to the database server on the local host using

after setting listening_addresses and samenet appropriately.

So it’s conceivable that the interface enumeration code in Windows somehow fails to include the link-local addresses.

If you have isolated this problem enough, I would send a bug report to PostgreSQL to analyze the issue further.

Heroku/Ecto/Postgres 28000 FATAL: no pg_hba.conf entry for host «115.159.183.134», user «postgres», database «postgres», SSL off

While there have been similar posts, none seems to match this situation so thank you for reading. On our production application (Heroku/Elixir/Phoenix/Ecto/Postgres), I am seeing thousands of errors of the form:

While such errors are commonly diagnosed as an issue with the pga_hba.conf file, in this case I believe the issue is an non-SSL attempt to read/write from the database, though I have no idea why that would be occurring with the following configuration:

With SSL as true, I don’t know why any non-SSL DB read/writes would be attempted. If it’s something outside of Ecto, I don’t know what it would be. Each attempt is coming from a unique IP, it seems, which seems unusual to me. I am trying to figure out what steps to take to track down what’s going on, so any advice is highly welcome.

The most mystifying aspect of this issue is that there are handful of such errors in the log reports over the past couple months and then out of the blue we’ve had thousands of errors of this kind in the last few days.

connect to PostgreSQL server: FATAL: no pg_hba.conf entry for host

Hello I am trying to run a website sent to me but after doing so this error appeared

after Googling it it says that i just need to add an entry in the pg_hba.conf file for that particular user. this is my pg_hba.conf file.

but after doing so, the error still persist. I restarted my XAMPP server several times but no changes appears. Thanks in advance

12 Answers 12

Add or edit the following line in your postgresql.conf :

Restart Postgresql after adding this with service postgresql restart or the equivalent command for your setup. For brew, brew services restart postgresql

This solution works for IPv4 / IPv6:

Edit pga_hba.conf File

Open up the pga_hba.conf file in your favourite editor:

Append To pga_hba.conf File

Append the following lines to the end of the pga_hba.conf file:

Quit and save the editor of your preference.

Restart Service

Restart the postgresql service with the following command:

The way I solved this was:

Added the line as below in pg_hba.conf :

I had this instance running on a Centos 7.3 and Postgres 9.5 in a VM in Azure, given this was a POC (proof of concept) you won’t want to connect without SSL in your actual prod environment.

To connect to the instance I was using pgAdmin 4 on macOS Sierra.

Fresh Postgres 9.5 install, Ubuntu.

The key was the local connection type, since psql uses domain socket connection.

Instructions for Debian users.

Get the location of pg_hba.conf by quering the database:

Add configuration where it says «Put your actual configuration here»:

Logout to your user:

Restart your postgres server for changes to take effect:

Add the following line in the bottom of pg_hba.conf :

hostnossl all all 0.0.0.0/0 md5

Add/modify the line in postgresql.conf :

MAKE SURE THAT the user that is connecting has a password: (Example connect user named postgres )

a. Run the following psql command with the postgres user account:

b. Set the password:

This below worked for me: (pg_hba.conf)

Require the client to supply a double-MD5-hashed password for authentication.

In my case I ran into this where I didn’t have access to edit any conf files on the server (.NET connecting to a managed db on DigitalOcean) so the other answers weren’t an option.

That may not be the optimal solution for me or for you, but I wanted to point out it’s possible that this is an issue with the connection string rather than the server config.

In my case, I had to add the exact line as suggested by the error information. Cannot bypass it by adding «all» users with all IPs as rule. Now it is like:

PosgreSQL 10.5 on CentOS 7.

Find the correct configuration file:

Add the following at the end of file:

Then restart your PostgreSQL application:

For PgAdmin 4 on Windows. I added these lines below

and modify postgresql.config:

Not the answer you’re looking for? Browse other questions tagged postgresql php pg-hba.conf or ask your own question.

Linked

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

no pg_hba.conf entry for host

I get following error when I try to connect using DBI

Here is my pg_hba.conf file:

My perl code is

May I know what i miss here?

16 Answers 16

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

If you can change this line:

You can see if this solves the problem.

In your pg_hba.conf file, I see some incorrect and confusing lines:

I suspect that if you md5’d the password, this might work if you trim the lines. To get the md5 you can use perl or the following shell script:

So then your connect line would like something like:

Your postgres server configuration seems correct That should grant access from the client to the postgres server. So that leads me to believe the username / password is whats failing.

Test this by creating a specific user for that database

Then adjust your perl script to use the newly created user

To resolve this problem, you can try this.

first, you have found out your pg_hba.conf by:

cd /etc/postgresql/9.5/main from your root directory

and open file using

then add this line:

to your pg_hba.conf and then restart by using the command:

Add the following in line in pg_hba.conf

hostnossl all all 0.0.0.0/0 trust

And then restart the Service.

To resolved this problem, you can try this.

first you have find out your pg_hba.conf and write :

after that restart pg server:

If you are getting an error like the one below:

then add an entry like the following, with your mac address.

If you are getting this error using node and pg module you can set ssl to not reject unauthorized access like this

I faced the same issue. My db was on cloud

ERROR: no pg_hba.conf entry for host «. «, user «. «, database «. «, SSL off

I add this configuration to resolve this,

SSL parameter is the key telling DB to always use SSL for making connections.

For those who are getting this error in DBeaver the solution was found here at line:

@lcustodio on the SSL page, set SSL mode: require and either leave the SSL Factory blank or use the org.postgresql.ssl.NonValidatingFactory

also check the PGHOST variable:

to see if it matches the local machine name

BTW, in my case it was that I needed to specify the user/pwd in the url, not as independent properties, they were ignored and my OS user was used to connect

My config is in a WebSphere 8.5.5 server.xml file

This would not work and was getting the error:

fatal no pg_hba.conf entry error when using Heroku and Postgresql

I’m getting this error when pushing my Django project to Heroku:

I’ve looked at the postgres database that is attached to my heroku project and the credentials are not the same as displayed we have not made any changes to the database only the django project itself. Heroku was working up until like 10 days ago and now every time we push to heroku the deployment fails because of this error.

My settings.py file:

Error after updating the database variable:

1 Answer 1

Perhaps Heroku changed your credentials. That would mean if you hard coded DATABASE_URL the password authentication would fail. Resolution: run heroku config or visit your apps settings and select «Reveal Config Vars» to get the new credentials.

Here’s the exert from the Heroku docs:

Occasionally we will roll Heroku Postgres credentials, this can happen for several reasons.

You can get the new credentials by running this command via the CLI: heroku config or visiting your app’s Settings page and clicking the «Reveal Config Vars».

Edit
I see that you do indeed have the DATABASE_URL hardcoded, and it should NOT be.

This should get the updated DATABASE_URL that Heroku generates.

Edit 2
I changed the above to deal with the DATABASE[‘default’] KeyError, but I see you also have a separate issue with running collectstatic. Check out this answer

Edit 3
Is it possible you have more than one database attached? Install the Heroku CLI if you don’t have it already then

That should list the databases. Then promote the correct one, by running

Where example-app is the name of your app, and replace with the correct database. Finally, destroy the unwanted databases with

Where is the database you want destroyed.

Another option is to delete the app, then re-add the postgres addon after you add the app in again.

connect to PostgreSQL server: FATAL: no pg_hba.conf entry for host

Hello I am trying to run a website sent to me but after doing so this error appeared

after Googling it it says that i just need to add an entry in the pg_hba.conf file for that particular user. this is my pg_hba.conf file.

but after doing so, the error still persist. I restarted my XAMPP server several times but no changes appears. Thanks in advance

12 Answers 12

Add or edit the following line in your postgresql.conf :

Restart Postgresql after adding this with service postgresql restart or the equivalent command for your setup. For brew, brew services restart postgresql

This solution works for IPv4 / IPv6:

Edit pga_hba.conf File

Open up the pga_hba.conf file in your favourite editor:

Append To pga_hba.conf File

Append the following lines to the end of the pga_hba.conf file:

Quit and save the editor of your preference.

Restart Service

Restart the postgresql service with the following command:

The way I solved this was:

Added the line as below in pg_hba.conf :

I had this instance running on a Centos 7.3 and Postgres 9.5 in a VM in Azure, given this was a POC (proof of concept) you won’t want to connect without SSL in your actual prod environment.

To connect to the instance I was using pgAdmin 4 on macOS Sierra.

Fresh Postgres 9.5 install, Ubuntu.

The key was the local connection type, since psql uses domain socket connection.

Instructions for Debian users.

Get the location of pg_hba.conf by quering the database:

Add configuration where it says «Put your actual configuration here»:

Logout to your user:

Restart your postgres server for changes to take effect:

Add the following line in the bottom of pg_hba.conf :

hostnossl all all 0.0.0.0/0 md5

Add/modify the line in postgresql.conf :

MAKE SURE THAT the user that is connecting has a password: (Example connect user named postgres )

a. Run the following psql command with the postgres user account:

b. Set the password:

This below worked for me: (pg_hba.conf)

Require the client to supply a double-MD5-hashed password for authentication.

In my case I ran into this where I didn’t have access to edit any conf files on the server (.NET connecting to a managed db on DigitalOcean) so the other answers weren’t an option.

That may not be the optimal solution for me or for you, but I wanted to point out it’s possible that this is an issue with the connection string rather than the server config.

In my case, I had to add the exact line as suggested by the error information. Cannot bypass it by adding «all» users with all IPs as rule. Now it is like:

PosgreSQL 10.5 on CentOS 7.

Find the correct configuration file:

Add the following at the end of file:

Then restart your PostgreSQL application:

For PgAdmin 4 on Windows. I added these lines below

and modify postgresql.config:

Not the answer you’re looking for? Browse other questions tagged postgresql php pg-hba.conf or ask your own question.

Linked

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

connect to PostgreSQL server: FATAL: no pg_hba.conf entry for host

Hello I am trying to run a website sent to me but after doing so this error appeared

after Googling it it says that i just need to add an entry in the pg_hba.conf file for that particular user. this is my pg_hba.conf file.

but after doing so, the error still persist. I restarted my XAMPP server several times but no changes appears. Thanks in advance

12 Answers 12

Add or edit the following line in your postgresql.conf :

Restart Postgresql after adding this with service postgresql restart or the equivalent command for your setup. For brew, brew services restart postgresql

This solution works for IPv4 / IPv6:

Edit pga_hba.conf File

Open up the pga_hba.conf file in your favourite editor:

Append To pga_hba.conf File

Append the following lines to the end of the pga_hba.conf file:

Quit and save the editor of your preference.

Restart Service

Restart the postgresql service with the following command:

The way I solved this was:

Added the line as below in pg_hba.conf :

I had this instance running on a Centos 7.3 and Postgres 9.5 in a VM in Azure, given this was a POC (proof of concept) you won’t want to connect without SSL in your actual prod environment.

To connect to the instance I was using pgAdmin 4 on macOS Sierra.

Fresh Postgres 9.5 install, Ubuntu.

The key was the local connection type, since psql uses domain socket connection.

Instructions for Debian users.

Get the location of pg_hba.conf by quering the database:

Add configuration where it says «Put your actual configuration here»:

Logout to your user:

Restart your postgres server for changes to take effect:

Add the following line in the bottom of pg_hba.conf :

hostnossl all all 0.0.0.0/0 md5

Add/modify the line in postgresql.conf :

MAKE SURE THAT the user that is connecting has a password: (Example connect user named postgres )

a. Run the following psql command with the postgres user account:

b. Set the password:

This below worked for me: (pg_hba.conf)

Require the client to supply a double-MD5-hashed password for authentication.

In my case I ran into this where I didn’t have access to edit any conf files on the server (.NET connecting to a managed db on DigitalOcean) so the other answers weren’t an option.

That may not be the optimal solution for me or for you, but I wanted to point out it’s possible that this is an issue with the connection string rather than the server config.

In my case, I had to add the exact line as suggested by the error information. Cannot bypass it by adding «all» users with all IPs as rule. Now it is like:

PosgreSQL 10.5 on CentOS 7.

Find the correct configuration file:

Add the following at the end of file:

Then restart your PostgreSQL application:

For PgAdmin 4 on Windows. I added these lines below

and modify postgresql.config:

Not the answer you’re looking for? Browse other questions tagged postgresql php pg-hba.conf or ask your own question.

Linked

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Heroku Postgres: «psql: FATAL: no pg_hba.conf entry for host»

There are a number of Heroku CLI Postgres commands that all return the same error. For example:

At least one of these commands has worked in the past, but does not now.

The database appears to be working fine otherwise. I can access it via my application’s interfaces.

I do not see a way to toggle SSL in the Heroku Postgres dashboard. What could be causing this and how could I fix it?

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I solved it by setting PGSSLMODE on Heroku to require. This tells Postres to default to SSL. On the command line this can be done via the following command.

The error basically says that you are trying to connect to a database instance without using SSL connection, but the server is setup to reject connection without SSL connection.

Azure Database for PostgreSQL server: no pg_hba.conf entry for host

FATAL: no pg_hba.conf entry for host «XX.XX.XX.XX», user «myuser», database «mydatabase», SSL on

where «XX.XX.XX.XX» is exactly the IP address I have enabled in Azure.

In Azure, in the «Connection security» tab of my database (see image below) I read the following warning:

So changing the IP address has no effect? How can I solve the problem?

Rake aborted after FATAL no pg_hba.conf entry

Trying to run my Rails 4.0.4 (Ruby 2.1.1) application on CentOS 6.5

Failing when I attempt to migrate:

I am not sure how to tackle this one. On my mac setup all worked fine without having to touch the pg_hba.conf.

Any lead is welcome.

I have created my_user as follow:

CREATE ROLE my_user WITH CREATEDB SUPERUSER LOGIN;

And allowed my_user to access all database with ‘trust’ in the pg_hba.conf

my config/database.yml contains

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

::1 is localhost in ipv6. Your PostgreSQL config doesn’t have a config for v6. Try setting your server to 127.0.0.1 the ipv4 address of localhost.

It looks like rake is for some reason passing a bad host, as I assume ::1 is not the name of your server (it looks more like an IP mask of sorts from the Postgres config). (Edit: ::1 is IPv6 localhost, per Doon’s comment below.)

Not sure offhand why the same code would work OK on your Mac, but I assume there’s a database.yml involved in your Rails config? You may want to try specifying a host attribute in there (it can point to localhost if your server is local) and see if that helps.

You’d also want to include one for the port if Postgres is not on the standard port for your Postgres install (5432 with a default install).

No pg hba conf entry for host

Authentication failures and related problems generally manifest themselves through error messages like the following:

This is what you are most likely to get if you succeed in contacting the server, but it does not want to talk to you. As the message suggests, the server refused the connection request because it found no matching entry in its pg_hba.conf configuration file.

Messages like this indicate that you contacted the server, and it is willing to talk to you, but not until you pass the authorization method specified in the pg_hba.conf file. Check the password you are providing, or check your Kerberos or ident software if the complaint mentions one of those authentication types.

The indicated database user name was not found.

The database you are trying to connect to does not exist. Note that if you do not specify a database name, it defaults to the database user name, which might or might not be the right thing.

The server log might contain more information about an authentication failure than is reported to the client. If you are confused about the reason for a failure, check the server log.

Prev	Up	Next
20.14. BSD Authentication	Home	Chapter 21. Database Roles

Submit correction

If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.

I am trying to get Postgres 9.2.4 to run as a service on Windows 7. After installing postgres, the service was running fine. However, after setting postgres up as a server for another program, the service stopped running. When I try to start the service now, I get a message saying :

When I try running the program that should use the database server, I get this error :

«A problem was encountered while attempting to log into or create the production database. Details: Could not connect to the server; Could not connect to remote socket. The application must now close»

I have also encountered this error once while opening the same program :

«A problem was encountered while attempting to log into or create the production database. Details: FATAL: could not load pg_hba.conf The application must now close.»

I have tried running the service logged on as a local system account as well as my own account (In the postgres service properties) to no avail. I also tried restarting my computer. After a lot of troubleshooting online, I learned that a good thing to check is the pg_log file. Here are the contents of the latest pg_log entry :

It seems to be having issues with the pg_hba.conf file, which looks like this :

When I searched for examples of what a pg_hba.conf file normally looks like, the examples looked slightly different from my file. I noticed that in the PostgreSQL program file, in addition to pg_hba.conf, there was also a «20130529-150444-old-pg_hba.conf» file which looked a lot more like the examples I was finding online. This file has several lines of comments before these last few lines :

I was hoping that this was the original pg_hba.conf file and that if I replaced the new file with the contents of the old one, postgres would start working again. No such luck. I have been hoping for more error files to be logged in pg_log to see if the previously stated error had disappeared or changed to something else, but no more files have been logged.

I have been troubleshooting online for a few days now and nothing I’ve found has worked. Sorry for having such a long question, but I wanted to be thorough and include all relevant information. I would appreciate it if anyone could shed some light on this problem or offer suggestions.

connect to PostgreSQL server: FATAL: no pg_hba.conf entry for host

Hello I am trying to run a website sent to me but after doing so this error appeared

after Googling it it says that i just need to add an entry in the pg_hba.conf file for that particular user. this is my pg_hba.conf file.

but after doing so, the error still persist. I restarted my XAMPP server several times but no changes appears. Thanks in advance

12 Answers 12

Add or edit the following line in your postgresql.conf :

Restart Postgresql after adding this with service postgresql restart or the equivalent command for your setup. For brew, brew services restart postgresql

This solution works for IPv4 / IPv6:

Edit pga_hba.conf File

Open up the pga_hba.conf file in your favourite editor:

Append To pga_hba.conf File

Append the following lines to the end of the pga_hba.conf file:

Quit and save the editor of your preference.

Restart Service

Restart the postgresql service with the following command:

The way I solved this was:

Added the line as below in pg_hba.conf :

I had this instance running on a Centos 7.3 and Postgres 9.5 in a VM in Azure, given this was a POC (proof of concept) you won’t want to connect without SSL in your actual prod environment.

To connect to the instance I was using pgAdmin 4 on macOS Sierra.

Fresh Postgres 9.5 install, Ubuntu.

The key was the local connection type, since psql uses domain socket connection.

Instructions for Debian users.

Get the location of pg_hba.conf by quering the database:

Add configuration where it says «Put your actual configuration here»:

Logout to your user:

Restart your postgres server for changes to take effect:

Add the following line in the bottom of pg_hba.conf :

hostnossl all all 0.0.0.0/0 md5

Add/modify the line in postgresql.conf :

MAKE SURE THAT the user that is connecting has a password: (Example connect user named postgres )

a. Run the following psql command with the postgres user account:

b. Set the password:

This below worked for me: (pg_hba.conf)

Require the client to supply a double-MD5-hashed password for authentication.

In my case I ran into this where I didn’t have access to edit any conf files on the server (.NET connecting to a managed db on DigitalOcean) so the other answers weren’t an option.

That may not be the optimal solution for me or for you, but I wanted to point out it’s possible that this is an issue with the connection string rather than the server config.

In my case, I had to add the exact line as suggested by the error information. Cannot bypass it by adding «all» users with all IPs as rule. Now it is like:

PosgreSQL 10.5 on CentOS 7.

Find the correct configuration file:

Add the following at the end of file:

Then restart your PostgreSQL application:

For PgAdmin 4 on Windows. I added these lines below

and modify postgresql.config:

Not the answer you’re looking for? Browse other questions tagged postgresql php pg-hba.conf or ask your own question.

Linked

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

pg_hba.conf in postgresql; FATAL: no pg_hba.conf entry for host “ “, user “XXXXX”, database “XXXX”, SSL off ; psql: could not connect to server: Connection refused

We often face with following connection refused errors while accessing postgresql from different clients (pg_admin, jdbc connection, psql ).

Let me first discuss about what pg_hba.conf file in postgresql.

pg_hba.conf

It stands for host based authentication for any client access. This file gets created automatically during initialization of the database(via initdb) and stored within “data” directory.

You can find following default entry in pg_hba.conf file in any new postgresql instance.

In the above image you can clearly see there are four sections.

We are clear that we will use mostly section 2 and section 4 for our activities. Now if you see column-wise you will find following columns.

5. METHOD: Specifies the authentication method to use when a connection matches this record. We generally use following three method which are shown below. There are many other options which you can find here.

Resolution to connection refused error

The connection refused error can come because of 2 reasons.

Обсуждение: no pg_hba.conf entry for replication connection from host

no pg_hba.conf entry for replication connection from host

Re: no pg_hba.conf entry for replication connection from host

Can you connect remotely from the standby using psql?

Yes, I can connect directly from the standby using psql and DB_USER and DB_PASS.

Re: no pg_hba.conf entry for replication connection from host

Also what file do you have primary_conninfo in?

On 04/09/2015 12:05 PM, Volkan Unsal wrote:

Can you connect remotely from the standby using psql?

Yes, I can connect directly from the standby using psql and DB_USER and
DB_PASS.

And you are sure the REP_USER is being correctly substituted in and that it has the REPLICATION attribute.

Have you tried the primary_conninfo with the values directly entered?

postgres@test=# create role rep_user with login replication;
CREATE ROLE

Also what file do you have primary_conninfo in?

Re: no pg_hba.conf entry for replication connection from host

So did you make the following entry in pg_hba,conf?

host replication rep 104.131.66.183/32 md5

Is rep a valid postgres user in the cluster?

Did you remember to do:
SELECT pg_reload_conf();

After making the changes to pg_hba.conf?

> *Volkan Unsal*
> *web and mobile development*
> volkanunsal.com
>

—
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.

Re: no pg_hba.conf entry for replication connection from host

Also what do the standby server logs show while you are trying to connect?

The logs show that pg_basebackup competed successfully. But then something goes wrong.

LOG: database system was interrupted; last known up at 2015-04-09 19:22:50 GMT
LOG: entering standby mode
LOG: redo starts at 0/A000028
LOG: consistent recovery state reached at 0/A0000F0

Re: no pg_hba.conf entry for replication connection from host

wal_level = hot_standby
hot_standby = on
max_standby_streaming_delay = 15min

listen_addresses = ‘*’
wal_level = hot_standby
max_wal_senders = 10
max_connections=100
checkpoint_segments = 8
wal_keep_segments = 8
archive_mode = on
archive_command = ‘cp %p /var/lib/postgresql/archive/%f’

LOG: database system was interrupted; last known up at 2015-04-09 19:22:50 GMT
LOG: entering standby mode

So did you make the following entry in pg_hba,conf?

host replication rep 104.131.66.183/32 md5

Is rep a valid postgres user in the cluster?

Did you remember to do:
SELECT pg_reload_conf();

After making the changes to pg_hba.conf?

—
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.

—
Sent via pgsql-general mailing list ( )
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: no pg_hba.conf entry for replication connection from host

So in your recovery.conf is standby_mode set to on?

On 04/09/2015 12:46 PM, Volkan Unsal wrote:

My postgresql.conf file in the standby server looks like this:

wal_level = hot_standby
hot_standby = on
max_standby_streaming_delay = 15min

In the master server, it looks like this:

listen_addresses = ‘*’
wal_level = hot_standby
max_wal_senders = 10
max_connections=100
checkpoint_segments = 8
wal_keep_segments = 8
archive_mode = on
archive_command = ‘cp %p /var/lib/postgresql/archive/% f’

So in your recovery.conf is standby_mode set to on?

Re: no pg_hba.conf entry for replication connection from host

1) What version(s) of Postgres are you using on either end?

I’m using Postgres 9:3.

2) Are the primary and the standby in different containers?

Yes, and they are on different servers as well.

3) What is the container/machine/network layout?

I created a gist of all the files in my setup.

The init-slave.sh and init-master.sh scripts are executed before the
server is started, so that’s where I do all my preprocessing of conf
files. I checked the results and the substituted values are indeed correct.

Well if I am understanding. This:

primary_conninfo = ‘host=$ ADDR> port=5432

is getting translated to:

Now the primary can receive connections from 0.0.0.0, which basically means it can receive from the Internet. The problem is that the standby can not connect to 0.0.0.0, that would mean it is connecting to the whole Internet. You will need to provide either the actual IP for the primary or its hostname.

Re: no pg_hba.conf entry for replication connection from host

On 04/09/2015 01:14 PM, Volkan Unsal wrote:

Oops. I used a dummy IP address in the yml file for privacy reasons. The
actual IP addresses would be placed there in my setup. The pg_basebackup
connection to the MASTER_PORT_5432_TCP___ADDR is successful, so I know
that slave can connect to the master at least. But it just cannot open a
streaming backup connection.

Yeah, that would have been too easy:) I am not seeing anything else at the moment.

On Thu, Apr 9, 2015 at 4:11 PM, Adrian Klaver > wrote:

On 04/09/2015 01:00 PM, Volkan Unsal wrote:

1) What version(s) of Postgres are you using on either end?

I’m using Postgres 9:3.

2) Are the primary and the standby in different containers?

Yes, and they are on different servers as well.

3) What is the container/machine/network layout?

I created a gist of all the files in my setup.

Well if I am understanding. This:

primary_conninfo = ‘host=$ _ADDR> port=5432

is getting translated to:

Now the primary can receive connections from 0.0.0.0, which
basically means it can receive from the Internet. The problem is
that the standby can not connect to 0.0.0.0, that would mean it is
connecting to the whole Internet. You will need to provide either
the actual IP for the primary or its hostname.

Re: no pg_hba.conf entry for replication connection from host

Is there a chance you have a recovery.conf in your primary server directory?

Re: no pg_hba.conf entry for replication connection from host

On 04/09/2015 01:48 PM, Volkan Unsal wrote:

Is there a chance you have a recovery.conf in your primary server
directory?

No, this file is only in the standby server. From the gist, here is
where recovery.conf gets created
.

Re: no pg_hba.conf entry for replication connection from host

On 04/09/2015 01:52 PM, Volkan Unsal wrote:

Yup, just did. Can never be too paranoid about this. 🙂

So where did the below come from?:

LOG: database system was interrupted; last known up at 2015-04-09 16:35:05 GMT
LOG: entering standby mode
LOG: redo starts at 0/E000028
LOG: consistent recovery state reached at 0/E0000F0

On Thu, Apr 9, 2015 at 4:51 PM, Adrian Klaver > wrote:

On 04/09/2015 01:48 PM, Volkan Unsal wrote:

Is there a chance you have a recovery.conf in your primary
server
directory?

No, this file is only in the standby server. From the gist, here is
where recovery.conf gets created

—
*Volkan Unsal*
/web and mobile development/
volkanunsal.com

Re: no pg_hba.conf entry for replication connection from host

Not sure that is a problem as the logs show the database reaching a consistent state:

Also setting up logging connects/disconnects on the primary to see if an attempt is even being made.

Re: no pg_hba.conf entry for replication connection from host

LOG: connection received: host=104.131.66.183 port=38912
LOG: replication connection authorized: user=postgres
LOG: connection received: host=104.131.66.183 port=38913
LOG: replication connection authorized: user=postgres

Not sure that is a problem as the logs show the database reaching a consistent state:

Also setting up logging connects/disconnects on the primary to see if an attempt is even being made.

Re: no pg_hba.conf entry for replication connection from host

If you on the outside looking in would that not depend on firewall rules also?

What do the FATAL errors say?

I forgot their contents now, but I think they showed up for trying to connect via psql, and not as part of replication process.

Re: no pg_hba.conf entry for replication connection from host

Could it be that pg_basebackup is still running and your CONNECTION LIMIT on the replication user is preventing any more connections?

Re: no pg_hba.conf entry for replication connection from host

On 04/09/2015 02:38 PM, Volkan Unsal wrote:

If you on the outside looking in would that not depend on firewall
rules also?

Hm, I guess. But I’m not behind a firewall and neither is the server.

This is what I see on the standby

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 *:ssh *:* LISTEN
tcp6 0 0 [::]:ssh [::]:* LISTEN
tcp6 0 0 [::]:postgresql [::]:* LISTEN

So it is using IPv6. If you are looking for the port using IPv4 then you will probably not see it.

Might try in your primary pg_hba.conf changing to:

I forgot their contents now, but I think they showed up for trying to
connect via psql, and not as part of replication process.

Re: no pg_hba.conf entry for replication connection from host

On 04/09/2015 03:01 PM, Volkan Unsal wrote:

Good point. But that didn’t work either. Back to reading the source code
for me.

Before you sent:

My postgresql.conf file in the standby server looks like this:

wal_level = hot_standby
hot_standby = on
max_standby_streaming_delay = 15min

Is that your entire postgresql.conf file on the standby?

Re: no pg_hba.conf entry for replication connection from host

On 04/09/2015 03:01 PM, Volkan Unsal wrote:

Good point. But that didn’t work either. Back to reading the source code
for me.

Before you sent:

My postgresql.conf file in the standby server looks like this:

wal_level = hot_standby
hot_standby = on
max_standby_streaming_delay = 15min

Is that your entire postgresql.conf file on the standby?

Re: no pg_hba.conf entry for replication connection from host

I did not see any postgres log entry complaining about invalid entry in pg_hba.conf.

The pg_hba.conf entry in your original post is wrong. What you need is

host replication replication 104.131.66.183/32 md5

the invalid or non pg_hba.conf entry.

Re: no pg_hba.conf entry for replication connection from host

I did not see any postgres log entry complaining about invalid entry in pg_hba.conf.

The pg_hba.conf entry in your original post is wrong. What you need is

host replication replication 104.131.66.183/32 md5

the invalid or non pg_hba.conf entry.

Re: no pg_hba.conf entry for replication connection from host

On 04/10/2015 11:04 AM, Volkan Unsal wrote:

I followed your instructions above and modified the pg_hba.conf in
master to hardcode the IP address of the standby server. I kept the same
pg_hba.conf file for the standby server –– I hope that was right. The
log output hasn’t changed much, but I’m enclosing it in this gist:

I hope the answer is in there.

I would say it is this:

backend>
PostgreSQL stand-alone backend 9.3.6

My guess is these:

LOG: connection received: host=104.131.66.183 port=46406
LOG: replication connection authorized: user=replication
LOG: connection received: host=104.131.66.183 port=46407

are pg_basebackup connecting.

Pretty sure the stand alone(single user) does not support streaming replciation.

On Fri, Apr 10, 2015 at 9:28 AM, Melvin Davidson > wrote:

What I see in the link is the original post.
I did not see any postgres log entry complaining about invalid entry
in pg_hba.conf.

The pg_hba.conf entry in your original post is wrong. What you need is

host replication replication 104.131.66.183/32
md5

If you get an error after making that change, then please attach the
complete new
version of the pg_hba.conf AND the entry from postgres log where it
complains about
the invalid or non pg_hba.conf entry.

Re: no pg_hba.conf entry for replication connection from host

On 04/10/2015 11:04 AM, Volkan Unsal wrote:

I hope the answer is in there.

I would say it is this:

backend>
PostgreSQL stand-alone backend 9.3.6

My guess is these:

LOG: connection received: host=104.131.66.183 port=46406
LOG: replication connection authorized: user=replication
LOG: connection received: host=104.131.66.183 port=46407

are pg_basebackup connecting.

Pretty sure the stand alone(single user) does not support streaming replciation.

On Fri, Apr 10, 2015 at 9:28 AM, Melvin Davidson > wrote:

What I see in the link is the original post.
I did not see any postgres log entry complaining about invalid entry
in pg_hba.conf.

The pg_hba.conf entry in your original post is wrong. What you need is

host replication replication 104.131.66.183/32
md5

Re: no pg_hba.conf entry for replication connection from host

On 04/10/2015 12:06 PM, Volkan Unsal wrote:

I didn’t realize stand-alone was the same thing as single-user mode ––
are you sure? I guess I don’t know what the alternative is to «a
stand-alone backend.»

PostgreSQL stand-alone backend 9.4rc1
backend>

Your log entries in the second Gist match the command you have in init-master.sh in your first Gist.

The alternative is either to use a system script to start Postgres or pg_ctl:

No, single-user mode is a special case for recovering from mistakes:

The postgres command can also be called in single-user mode. The primary use for this mode is during bootstrapping by initdb. Sometimes it is used for debugging or disaster recovery; note that running a single-user server is not truly suitable for debugging the server, since no realistic interprocess communication and locking will happen. When invoked in single-user mode from the shell, the user can enter queries and the results will be printed to the screen, but in a form that is more useful for developers than end users. In the single-user mode, the session user will be set to the user with ID 1, and implicit superuser powers are granted to this user. This user does not actually have to exist, so the single-user mode can be used to manually recover from certain kinds of accidental damage to the system catalogs.

Thread: no pg_hba.conf entry for replication connection from host

no pg_hba.conf entry for replication connection from host

Re: no pg_hba.conf entry for replication connection from host

Can you connect remotely from the standby using psql?

Yes, I can connect directly from the standby using psql and DB_USER and DB_PASS.В

Re: no pg_hba.conf entry for replication connection from host

Also what file do you haveВ primary_conninfo in?

On 04/09/2015 12:05 PM, Volkan Unsal wrote:

В В Can you connect remotely from the standby using psql?

Yes, I can connect directly from the standby using psql and DB_USER and
DB_PASS.

And you are sure the REP_USER is being correctly substituted in and that it has the REPLICATION attribute.

Have you tried theВ primary_conninfoВ with the values directly entered?

postgres@test=# create role rep_user with login replication;
CREATE ROLE

Also what file do you haveВ primary_conninfo in?

Re: no pg_hba.conf entry for replication connection from host

hostВ В replicationВ В В repВ В В В В 104.131.66.183/32 В В В В В В md5

So did you make the following entry in pg_hba,conf?

hostВ В replicationВ В В repВ В В В 104.131.66.183/32В В В В В В md5

Is rep a valid postgres user in the cluster?

Did you remember to do:
SELECT pg_reload_conf();

After making the changes to pg_hba.conf?

> *Volkan Unsal*
> *web and mobile development*
> volkanunsal.com
>

—
*Melvin Davidson*
I reserve the right to fantasize.В Whether or not you
wish to share my fantasy is entirely up to you.

Re: no pg_hba.conf entry for replication connection from host

Also what do the standby server logs show while you are trying to connect?

The logs show that pg_basebackup competed successfully. But then something goes wrong.

LOG: В database system was interrupted; last known up at 2015-04-09 19:22:50 GMT
LOG: В entering standby mode
LOG: В redo starts at 0/A000028
LOG: В consistent recovery state reached at 0/A0000F0

Re: no pg_hba.conf entry for replication connection from host

wal_level = hot_standby
hot_standby = on
max_standby_streaming_delay = 15min

listen_addresses = ‘*’
wal_level = hot_standby
max_wal_senders = 10
max_connections=100
checkpoint_segments = 8
wal_keep_segments = 8
archive_mode = on
archive_command = ‘cp %p /var/lib/postgresql/archive/%f’

LOG: В database system was interrupted; last known up at 2015-04-09 19:22:50 GMT
LOG: В entering standby mode

So did you make the following entry in pg_hba,conf?

hostВ В replicationВ В repВ В В В 104.131.66.183/32В В В В В В md5

Is rep a valid postgres user in the cluster?

Did you remember to do:
SELECT pg_reload_conf();

After making the changes to pg_hba.conf?

—
*Melvin Davidson*
I reserve the right to fantasize.В Whether or not you
wish to share my fantasy is entirely up to you.

—
Sent via pgsql-general mailing list ( )
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: no pg_hba.conf entry for replication connection from host

So in your recovery.conf is standby_mode set to on?

On 04/09/2015 12:46 PM, Volkan Unsal wrote:

My postgresql.conf file in the standby server looks like this:

В В wal_level = hot_standby
В В hot_standby = on
В В max_standby_streaming_delay = 15min

In the master server, it looks like this:

В В listen_addresses = ‘*’
В В wal_level = hot_standby
В В max_wal_senders = 10
В В max_connections=100
В В checkpoint_segments = 8
В В wal_keep_segments = 8
В В archive_mode = on
В В archive_command = ‘cp %p /var/lib/postgresql/archive/% f’

So in your recovery.conf is standby_mode set to on?

Re: no pg_hba.conf entry for replication connection from host

В В 1) What version(s) of Postgres are you using on either end?

I’m using Postgres 9:3.

В В 2) Are the primary and the standby in different containers?

Yes, and they are on different servers as well.

В В 3) What is the container/machine/network layout?

I created a gist of all the files in my setup.

Well if I am understanding. This:

primary_conninfo = ‘host=$ ADDR> port=5432

is getting translated to:

Re: no pg_hba.conf entry for replication connection from host

On 04/09/2015 01:14 PM, Volkan Unsal wrote:

Oops. I used a dummy IP address in the yml file for privacy reasons. The
actual IP addresses would be placed there in my setup. The pg_basebackup
connection to the MASTER_PORT_5432_TCP___ADDR is successful, so I know
that slave can connect to the master at least. But it just cannot open a
streaming backup connection.

Yeah, that would have been too easy:) I am not seeing anything else at the moment.

On Thu, Apr 9, 2015 at 4:11 PM, Adrian Klaver > wrote:

В В On 04/09/2015 01:00 PM, Volkan Unsal wrote:

В В В В Hi Adrian,

В В В В В В В 1) What version(s) of Postgres are you using on either end?

В В В В I’m using Postgres 9:3.

В В В В В В В 2) Are the primary and the standby in different containers?

В В В В Yes, and they are on different servers as well.

В В В В В В В 3) What is the container/machine/network layout?

В В В В I created a gist of all the files in my setup.

В В В В The init-slave.sh and init-master.sh scripts are executed before the
В В В В server is started, so that’s where I do all my preprocessing of conf
В В В В files. I checked the results and the substituted values are
В В В В indeed correct.

В В Well if I am understanding. This:

В В primary_conninfo = ‘host=$ _ADDR> port=5432

В В is getting translated to:

В В host=0.0.0.0 port=5432

В В Now the primary can receive connections from 0.0.0.0, which
В В basically means it can receive from the Internet. The problem is
В В that the standby can not connect to 0.0.0.0, that would mean it is
В В connecting to the whole Internet. You will need to provide either
В В the actual IP for the primary or its hostname.

Re: no pg_hba.conf entry for replication connection from host

Is there a chance you have a recovery.conf in your primary server directory?

Re: no pg_hba.conf entry for replication connection from host

On 04/09/2015 01:48 PM, Volkan Unsal wrote:

В В Is there a chance you have a recovery.conf in your primary server
В В directory?

No, this file is only in the standby server. From the gist, here is
where recovery.conf gets created
.

Re: no pg_hba.conf entry for replication connection from host

On 04/09/2015 01:52 PM, Volkan Unsal wrote:

Yup, just did. Can never be too paranoid about this. 🙂

So where did the below come from?:

LOG:В database system was interrupted; last known up at 2015-04-09 16:35:05 GMT
LOG:В entering standby mode
LOG:В redo starts at 0/E000028
LOG:В consistent recovery state reached at 0/E0000F0

On Thu, Apr 9, 2015 at 4:51 PM, Adrian Klaver > wrote:

В В On 04/09/2015 01:48 PM, Volkan Unsal wrote:

В В В В HI Adrian,

В В В В В В В Is there a chance you have a recovery.conf in your primary
В В В В server
В В В В В В В directory?

В В В В No, this file is only in the standby server. From the gist, here is
В В В В where recovery.conf gets created
В В В В
В В В В >.

Re: no pg_hba.conf entry for replication connection from host

Not sure that is a problem as the logs show the database reaching a consistent state:

Also setting up logging connects/disconnects on the primary to see if an attempt is even being made.

Re: no pg_hba.conf entry for replication connection from host

LOG: В connection received: host=104.131.66.183 port=38912
LOG: В replication connection authorized: user=postgres
LOG: В connection received: host=104.131.66.183 port=38913
LOG: В replication connection authorized: user=postgres

Not sure that is a problem as the logs show the database reaching a consistent state:

Also setting up logging connects/disconnects on the primary to see if an attempt is even being made.

Re: no pg_hba.conf entry for replication connection from host

If you on the outside looking in would that not depend on firewall rules also?

What do the FATAL errors say?

I forgot their contents now, but I think they showed up for trying to connect via psql, and not as part of replication process.

Re: no pg_hba.conf entry for replication connection from host

Could it be that pg_basebackup is still running and your CONNECTION LIMIT on the replication user is preventing any more connections?

Re: no pg_hba.conf entry for replication connection from host

On 04/09/2015 02:38 PM, Volkan Unsal wrote:

В В If you on the outside looking in would that not depend on firewall
В В rules also?

Hm, I guess. But I’m not behind a firewall and neither is the server.

This is what I see on the standby

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local AddressВ В В В В В Foreign AddressВ В В В В State
tcpВ В В В 0В В В 0 *:sshВ В В В В В В В В В *:*В В В В В В В В В В В LISTEN
tcp6В В В В 0В В В 0 [::]:sshВ В В В В В В В [::]:*В В В В В В В В В LISTEN
tcp6В В В В 0В В В 0 [::]:postgresqlВ В В В В [::]:*В В В В В В В В В LISTEN

So it is using IPv6. If you are looking for the port using IPv4 then you will probably not see it.

Might try in your primary pg_hba.conf changing to:

В В What do the FATAL errors say?

I forgot their contents now, but I think they showed up for trying to
connect via psql, and not as part of replication process.

Re: no pg_hba.conf entry for replication connection from host

On 04/09/2015 03:01 PM, Volkan Unsal wrote:

Good point. But that didn’t work either. Back to reading the source code
for me.

Before you sent:

My postgresql.conf file in the standby server looks like this:

В В wal_level = hot_standby
В В hot_standby = on
В В max_standby_streaming_delay = 15min

Is that your entire postgresql.conf file on the standby?

Re: no pg_hba.conf entry for replication connection from host

On 04/09/2015 03:01 PM, Volkan Unsal wrote:

Good point. But that didn’t work either. Back to reading the source code
for me.

Before you sent:

My postgresql.conf file in the standby server looks like this:

В В wal_level = hot_standby
В В hot_standby = on
В В max_standby_streaming_delay = 15min

Is that your entire postgresql.conf file on the standby?

Re: no pg_hba.conf entry for replication connection from host

I did not see any postgres log entry complaining about invalid entry in pg_hba.conf.

The pg_hba.conf entry in your original post is wrong. What you need is

hostВ В В replicationВ В В В replicationВ В В В 104.131.66.183/32В В В В В В В md5

the invalid or non pg_hba.conf entry.

Re: no pg_hba.conf entry for replication connection from host

I did not see any postgres log entry complaining about invalid entry in pg_hba.conf.

The pg_hba.conf entry in your original post is wrong. What you need is

hostВ В В replicationВ В В В replicationВ В В В 104.131.66.183/32В В В В В В В md5

the invalid or non pg_hba.conf entry.

Re: no pg_hba.conf entry for replication connection from host

On 04/10/2015 11:04 AM, Volkan Unsal wrote:

I followed your instructions above and modified the pg_hba.conf in
master to hardcode the IP address of the standby server. I kept the same
pg_hba.conf file for the standby server вЂ“вЂ“ I hope that was right. The
log output hasn’t changed much, but I’m enclosing it in this gist:

I hope the answer is in there.

I would say it is this:

backend>
PostgreSQL stand-alone backend 9.3.6

My guess is these:

LOG:В connection received: host=104.131.66.183 port=46406
LOG:В replication connection authorized: user=replication
LOG:В connection received: host=104.131.66.183 port=46407

are pg_basebackup connecting.

Pretty sure the stand alone(single user) does not support streaming replciation.

On Fri, Apr 10, 2015 at 9:28 AM, Melvin Davidson > wrote:

В В What I see in the link is the original post.
В В I did not see any postgres log entry complaining about invalid entry
В В in pg_hba.conf.

В В The pg_hba.conf entry in your original post is wrong. What you need is

В В hostВ В replicationВ В В replication 104.131.66.183/32
В В В В В В md5

В В If you get an error after making that change, then please attach the
В В complete new
В В version of the pg_hba.conf AND the entry from postgres log where it
В В complains about
В В the invalid or non pg_hba.conf entry.

Re: no pg_hba.conf entry for replication connection from host

On 04/10/2015 11:04 AM, Volkan Unsal wrote:

I followed your instructions above and modified the pg_hba.conf in
master to hardcode the IP address of the standby server. I kept the same
pg_hba.conf file for the standby server вЂ“вЂ“ I hope that was right. The
log output hasn’t changed much, but I’m enclosing it in this gist:

I hope the answer is in there.

I would say it is this:

backend>
PostgreSQL stand-alone backend 9.3.6

My guess is these:

LOG:В connection received: host=104.131.66.183 port=46406
LOG:В replication connection authorized: user=replication
LOG:В connection received: host=104.131.66.183 port=46407

are pg_basebackup connecting.

Pretty sure the stand alone(single user) does not support streaming replciation.

On Fri, Apr 10, 2015 at 9:28 AM, Melvin Davidson > wrote:

В В What I see in the link is the original post.
В В I did not see any postgres log entry complaining about invalid entry
В В in pg_hba.conf.

В В The pg_hba.conf entry in your original post is wrong. What you need is

В В hostВ В replicationВ В В replication 104.131.66.183/32
В В В В В В md5

Re: no pg_hba.conf entry for replication connection from host

On 04/10/2015 12:06 PM, Volkan Unsal wrote:

I didn’t realize stand-alone was the same thing as single-user mode вЂ“вЂ“
are you sure? I guess I don’t know what the alternative is to «a
stand-alone backend.»

PostgreSQL stand-alone backend 9.4rc1
backend>

Your log entries in the second Gist match the command you have in init-master.sh in your first Gist.

The alternative is either to use a system script to start Postgres or pg_ctl:

No, single-user mode is a special case for recovering from mistakes:

19.4. Проблемы аутентификации

Сбои и другие проблемы с аутентификацией обычно дают о себе знать через сообщения об ошибках, например:

Это сообщение вы, скорее всего, получите, если сможете связаться с сервером, но он не захочет с вами общаться. В сообщении содержится предположение, что сервер отказывает вам в подключении, поскольку не может найти подходящую запись в файле pg_hba.conf.

Такое сообщение показывает, что вы связались с сервером, он готов общаться с вами, но только после того, как вы прошли авторизацию по методу, указанному в файле pg_hba.conf. Проверьте пароль, который вы вводите, и как настроен Kerberos или ident, если в сообщении упоминается один из этих типов аутентификации.

Указанное имя пользователя базы данных не найдено.

База данных, к которой вы пытаетесь подключиться, не существует. Имейте в виду, что если вы не указали имя базы данных, по умолчанию берётся имя пользователя базы данных, что может приводить к ошибкам.

Подсказка: В журнале сервера может содержаться больше информации, чем в выдаваемых клиенту сообщениях об ошибке аутентификации, поэтому, если вас интересуют причины сбоя, проверьте журнал сервера.

No pg hba conf entry for host

Created on ‎08-26-2017 05:11 AM

While accessing psql for HAWQ, the command fails with the following error:

This issue occurs when the etl_user is missing under pg_hba.conf and Postgres database.

To resolve the issue, create a new user from postgres by performing the following steps:

Re: ERROR: «FATAL: no pg_hba.conf entry for host «[local]», user «etl_user», database «etl_user», SSL off» while accessing psql for HAWQ

Created on ‎08-28-2017 03:11 PM

Ack! No, don’t add «trust». And «host all 0.0.0.0/0 trust» means that the user_name you picked can log into the database without a password. Plus, you made the user a superuper. That is bad idea. Instead, add this to the end of the pg_hba.conf file on the master.

host all all 0.0.0.0/0 md5

This means it will use an encrypted password.

When you create your user, use this:

create user identified by ‘your_password’;

or, if you already created your user:

alter user identified by ‘new_password’;

And you don’t have to restart the cluster.

That will update the cluster with the new pg_hba.conf file.

Re: ERROR: «FATAL: no pg_hba.conf entry for host «[local]», user «etl_user», database «etl_user», SSL off» while accessing psql for HAWQ

Created on ‎08-29-2017 03:03 PM

Node.Js + PostgreSQL + Heroku Error: No pg_hba.conf entry for host, SSL off

Subscribe to our newsletter and never miss any upcoming articles

If you deploy your Node.Js and PostgreSQL application on Heroku, you might run into the following error:

error: no pg_hba.conf entry for host «93.68.220.97», user «dbusername», database «musicdb», SSL off

Your error will differ slightly because your host, user and database name will be different from mine.

With that being said, let’s see how you can fix it and make your application work.

Solution

In this example, we use the «pg» package. Thus, let’s say you create a new pool with the following configuration:

If you run the application now, you get an error.

The solution to the error is to add a new property to the pool configuration. All you need to do is to pass the following SSL configuration object to the pool constructor:

Now, your pool configuration should look as follows:

Save the changes, and you are done. Your application should run without problems now.

The above solution is for the «pg» raw driver, but if you use an ORM like Sequelize, the solution syntax differs a bit.

The above code snippet shows how to solve the error when using Sequelize.

Alternative

You can omit the SSL configuration object by running heroku config:set PGSSLMODE=no-verify in the Heroku CLI.

If you do not know how to do that, you can read this article to learn how to set environment variables on Heroku.

Server Error: No pg_hba.conf Entry for Host

In this entry, you will find resolutions for this error when attempting to connect remotely to a PostgreSQL database.

Date Entered: 3/18/2020 Last Updated: 3/18/2020 Author: Garrett Bird

When using one of the PostgreSQL connectors provided by CData, the error below is one of the common errors a user may face when connecting with a remote PostgreSQL database for the first time:

Server error: no pg_hba.conf entry for host «10.0.1.128», user «postgres», database «postgres», SSL off Connection was forcibly closed

This error can also occur if the user provides the actual IP address of a local PostgreSQL instance to the Server connection property, rather than «localhost.» In any case, the solution can be quickly resolved if the user can access the PostgreSQL instance itself, or can contact an administrator that manages it. The below steps will be all that is needed to enable remote connections to the server from your machine:

Once the above steps are finished, you should now be able to remotely execute queries to your PostgreSQL server from your machine with any of the connectors provided by CData.

no pg_hba.conf entry for host #24

Comments

daxhuiberts commented May 20, 2019 •

I’m trying to run pgmetrics against our Heroku postgres database, but I’m receiving the following error message:
pgmetrics: pq: no pg_hba.conf entry for host «xxx.xxx.xx.xx», user «xxxxxxxx», database «xxxxxxxx», SSL off

The the host ip in the error message is not the public ip of the database instance, but looks like the private ip.
Connecting to the database using psql from the same terminal with the same credentials works as expected.
pgmetrics runs succesfully against my localhost database.
I’m using the darwin build of v1.6.3 from https://github.com/rapidloop/pgmetrics/releases
I also tried running the docker image version but there I get the same error message.

Is there a setting I need to provide on the command line for it to work with a Heroku postgres database?

The text was updated successfully, but these errors were encountered:

No pg hba conf entry for host

The general format of the pg_hba.conf file is a set of records, one per line. Blank lines are ignored, as is any text after the # comment character. A record can be continued onto the next line by ending the line with a backslash. (Backslashes are not special except at the end of a line.) A record is made up of a number of fields which are separated by spaces and/or tabs. Fields can contain white space if the field value is double-quoted. Quoting one of the keywords in a database, user, or address field (e.g., all or replication ) makes the word lose its special meaning, and just match a database, user, or host with that name. Backslash line continuation applies even within quoted text or comments.

Each record specifies a connection type, a client IP address range (if relevant for the connection type), a database name, a user name, and the authentication method to be used for connections matching these parameters. The first record with a matching connection type, client address, requested database, and user name is used to perform authentication. There is no “ fall-through ” or “ backup ” : if one record is chosen and the authentication fails, subsequent records are not considered. If no record matches, access is denied.

A record can have several formats:

The meaning of the fields is as follows:

This record matches connection attempts using Unix-domain sockets. Without a record of this type, Unix-domain socket connections are disallowed.

This record matches connection attempts made using TCP/IP, but only when the connection is made with SSL encryption.

To make use of this option the server must be built with SSL support. Furthermore, SSL must be enabled by setting the ssl configuration parameter (see Section 19.9 for more information). Otherwise, the hostssl record is ignored except for logging a warning that it cannot match any connections.

This record matches connection attempts made using TCP/IP, but only when the connection is made with GSSAPI encryption.

This record type has the opposite behavior of hostgssenc ; it only matches connection attempts made over TCP/IP that do not use GSSAPI encryption.

Specifies the client machine address(es) that this record matches. This field can contain either a host name, an IP address range, or one of the special key words mentioned below.

Typical examples of an IPv4 address range specified this way are 172.20.143.89/32 for a single host, or 172.20.143.0/24 for a small network, or 10.6.0.0/16 for a larger one. An IPv6 address range might look like ::1/128 for a single host (in this case the IPv6 loopback address) or fe80::7a31:c1ff:0000:0000/96 for a small network. 0.0.0.0/0 represents all IPv4 addresses, and ::0/0 represents all IPv6 addresses. To specify a single host, use a mask length of 32 for IPv4 or 128 for IPv6. In a network address, do not omit trailing zeroes.

An entry given in IPv4 format will match only IPv4 connections, and an entry given in IPv6 format will match only IPv6 connections, even if the represented address is in the IPv4-in-IPv6 range. Note that entries in IPv6 format will be rejected if the system’s C library does not have support for IPv6 addresses.

You can also write all to match any IP address, samehost to match any of the server’s own IP addresses, or samenet to match any address in any subnet that the server is directly connected to.

If a host name is specified (anything that is not an IP address range or a special key word is treated as a host name), that name is compared with the result of a reverse name resolution of the client’s IP address (e.g., reverse DNS lookup, if DNS is used). Host name comparisons are case insensitive. If there is a match, then a forward name resolution (e.g., forward DNS lookup) is performed on the host name to check whether any of the addresses it resolves to are equal to the client’s IP address. If both directions match, then the entry is considered to match. (The host name that is used in pg_hba.conf should be the one that address-to-name resolution of the client’s IP address returns, otherwise the line won’t be matched. Some host name databases allow associating an IP address with multiple host names, but the operating system will only return one host name when asked to resolve an IP address.)

These fields do not apply to local records.

Users sometimes wonder why host names are handled in this seemingly complicated way, with two name resolutions including a reverse lookup of the client’s IP address. This complicates use of the feature in case the client’s reverse DNS entry is not set up or yields some undesirable host name. It is done primarily for efficiency: this way, a connection attempt requires at most two resolver lookups, one reverse and one forward. If there is a resolver problem with some address, it becomes only that client’s problem. A hypothetical alternative implementation that only did forward lookups would have to resolve every host name mentioned in pg_hba.conf during every connection attempt. That could be quite slow if many names are listed. And if there is a resolver problem with one of the host names, it becomes everyone’s problem.

Also, a reverse lookup is necessary to implement the suffix matching feature, because the actual client host name needs to be known in order to match it against the pattern.

Note that this behavior is consistent with other popular implementations of host name-based access control, such as the Apache HTTP Server and TCP Wrappers.

These two fields can be used as an alternative to the IP-address / mask-length notation. Instead of specifying the mask length, the actual mask is specified in a separate column. For example, 255.0.0.0 represents an IPv4 CIDR mask length of 8, and 255.255.255.255 represents a CIDR mask length of 32.

These fields do not apply to local records.

Specifies the authentication method to use when a connection matches this record. The possible choices are summarized here; details are in Section 21.3. All the options are lower case and treated case sensitively, so even acronyms like ldap must be specified as lower case.

Reject the connection unconditionally. This is useful for “ filtering out ” certain hosts from a group, for example a reject line could block a specific host from connecting, while a later line allows the remaining hosts in a specific network to connect.

Perform SCRAM-SHA-256 authentication to verify the user’s password. See Section 21.5 for details.

Perform SCRAM-SHA-256 or MD5 authentication to verify the user’s password. See Section 21.5 for details.

Require the client to supply an unencrypted password for authentication. Since the password is sent in clear text over the network, this should not be used on untrusted networks. See Section 21.5 for details.

Use GSSAPI to authenticate the user. This is only available for TCP/IP connections. See Section 21.6 for details. It can be used in conjunction with GSSAPI encryption.

Use SSPI to authenticate the user. This is only available on Windows. See Section 21.7 for details.

Obtain the operating system user name of the client by contacting the ident server on the client and check if it matches the requested database user name. Ident authentication can only be used on TCP/IP connections. When specified for local connections, peer authentication will be used instead. See Section 21.8 for details.

Obtain the client’s operating system user name from the operating system and check if it matches the requested database user name. This is only available for local connections. See Section 21.9 for details.

Authenticate using an LDAP server. See Section 21.10 for details.

Authenticate using a RADIUS server. See Section 21.11 for details.

Authenticate using SSL client certificates. See Section 21.12 for details.

Authenticate using the Pluggable Authentication Modules (PAM) service provided by the operating system. See Section 21.13 for details.

Authenticate using the BSD Authentication service provided by the operating system. See Section 21.14 for details.

After the auth-method field, there can be field(s) of the form name = value that specify options for the authentication method. Details about which options are available for which authentication methods appear below.

Since the pg_hba.conf records are examined sequentially for each connection attempt, the order of the records is significant. Typically, earlier records will have tight connection match parameters and weaker authentication methods, while later records will have looser match parameters and stronger authentication methods. For example, one might wish to use trust authentication for local TCP/IP connections but require a password for remote TCP/IP connections. In this case a record specifying trust authentication for connections from 127.0.0.1 would appear before a record specifying password authentication for a wider range of allowed client IP addresses.

The preceding statement is not true on Microsoft Windows: there, any changes in the pg_hba.conf file are immediately applied by subsequent new connections.

The system view pg_hba_file_rules can be helpful for pre-testing changes to the pg_hba.conf file, or for diagnosing problems if loading of the file did not have the desired effects. Rows in the view with non-null error fields indicate problems in the corresponding lines of the file.

To connect to a particular database, a user must not only pass the pg_hba.conf checks, but must have the CONNECT privilege for the database. If you wish to restrict which users can connect to which databases, it’s usually easier to control this by granting/revoking CONNECT privilege than to put the rules in pg_hba.conf entries.

Some examples of pg_hba.conf entries are shown in Example 21.1. See the next section for details on the different authentication methods.

Example 21.1. Example pg_hba.conf Entries

Prev	Up	Next
Chapter 21. Client Authentication	Home	21.2. User Name Maps

Submit correction

no pg_hba.conf entry for host when using the App platform

IвЂ™ve started to use the Beta of the App platform.

My service is a Spring Boot application declared through a Docker image, and it connects to a Postgres database declared through the App platform.

IвЂ™ve declared the connection parameters at service level using the following environment variables:

where ontrack-db is the name of the database component.

However, at startup, the service cannot connect to the database because of the following error:

So I wonder how I can make my Postgres component in the App understand that itвЂ™s OK to accept connections from the main service in the same App.

Thanks for any help, IвЂ™m looking forward to start hosting some apps on the App platform, Damien Coraboeuf

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Homestead PostgreSQL cant connect out the box from remote/host machine #11339

Comments

JFossey commented Dec 14, 2015

Problem

On a new setup of Homestead you get an error connecting remotely to VM via GUi Tools like pgAdmin3 and the Latest HeidiSQL (experimental).

Connecting VIA localhost in a Shell works.

Error:

homestead@postgres FATAL: no pg_hba.conf entry for host «192.168.10.1», user «homestead», database «postgres», SSL on
homestead@postgres FATAL: no pg_hba.conf entry for host «192.168.10.1», user «homestead», database «postgres», SSL off

Workaround:

Add the following to after.sh, based on code found in settler.

Suggested Fix

Add «host all all 0.0.0.0/0 md5» to pg_hba.conf out the box on new setups providing remote access to PostgreSQL databases.

The text was updated successfully, but these errors were encountered:

GrahamCampbell commented Dec 19, 2015

We’re open to PRs. 😉

andrey-helldar commented Jan 5, 2017 •

In vagrant 1.9.1 and homestead 4.0.3 (1.0.1 box version):

PS: Connect to MySQL: OK

andrey-helldar commented Jan 5, 2017

mikebronner commented Mar 4, 2017 •

This worked for me:

lukeholder commented Dec 11, 2019

Should we need to add something to after.sh to get this to work?

Should we need to edit the after.sh directly to get this to work?

mikebronner commented Dec 11, 2019

@lukeholder This might be a good issue to raise in Settler or Homestead repos, as the change would have to be made there.

browner12 commented Dec 11, 2019

@lukeholder if you’re having issues visit us over in the laravel/homestead directory or in the Slack homestead-dev channel

lukeholder commented Dec 11, 2019

Thanks @mikebronner and @browner12 didn’t realize I wasn’t in the right repo.

dqfan2012 commented Jan 12, 2021

I configured my homestead to run at 192.168.5.10 (because it’s within my VMWare virtual network setup). I got my remote connection to postgresql to work as follows:

In the pg_hba.conf file, I added a line for the gateway because you’ll be connecting to postgresql through the gateway. For me that looked like this:

I dislike the solution above using 0.0.0.0/0. I think configuring the proper IP address and telling postgresql to trust connections from that IP is better.

Источники:

No pg hba conf entry for host

Heroku Postgres: «psql: FATAL: no pg_hba.conf entry for host»

11 Answers 11

Trending sort

how to fix no pg_hba.conf entry for host «::1»

2 Answers 2

Trending sort

org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host

6 Answers 6

Trending sort

connect to PostgreSQL server: FATAL: no pg_hba.conf entry for host

12 Answers 12

Edit pga_hba.conf File

Append To pga_hba.conf File

Restart Service

Not the answer you’re looking for? Browse other questions tagged postgresql php pg-hba.conf or ask your own question.

Linked

Related

Hot Network Questions

Subscribe to RSS

no pg_hba.conf entry for host

16 Answers 16

Trending sort

Resolve «FATAL:no pg_hba.conf entry for host» Error when you Connect from PGAdmin4

Available Languages

Download Options

Bias-Free Language

Contents

Introduction

Prerequisites

Requirements

Components Used

Problem

Solution

FATAL: no pg_hba.conf entry for host «fe80::1%lo0»

6 Answers 6

Trending sort

docker-compose install gets «no pg_hba.conf entry» #4736

Comments

javexed commented Sep 13, 2019

ISSUE TYPE

SUMMARY

ENVIRONMENT

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS

ADDITIONAL INFORMATION

ryanpetrello commented Sep 13, 2019

javexed commented Sep 14, 2019

javexed commented Sep 14, 2019

treyd commented Oct 24, 2019

rooftopcellist commented Oct 25, 2019

treyd commented Oct 25, 2019

treyd commented Oct 25, 2019

rooftopcellist commented Oct 25, 2019

treyd commented Oct 25, 2019 •

rooftopcellist commented Oct 25, 2019

javexed commented Oct 30, 2019

treyd commented Oct 31, 2019

gtie commented Nov 6, 2019 •

gtie commented Nov 6, 2019

treyd commented Nov 6, 2019

gtie commented Nov 7, 2019

javexed commented Nov 18, 2019

fgierlinger commented Apr 13, 2020

w7089 commented Apr 30, 2020

ArjonBu commented May 28, 2020

ptran32 commented Jun 15, 2020

neutralrockets commented Jun 25, 2020

nevotheless commented Jul 3, 2020

iloominaty commented Jul 15, 2020

joefodor commented Jul 15, 2020 •

Psycopg2 reporting pg_hba.conf error

2 Answers 2

Trending sort

2 Answers 2

Trending sort

FATAL: no pg_hba.conf entry for host «fe80::1%lo0»

6 Answers 6

Trending sort