Skip to main content

PostgreSQL error: no pg_hba.conf entry for host

I’m currently integrating SonarQube in our Build pipeline. During the process I stumbled over some issues. One issue I got was related to PostgreSQL that we were using as our database for SonarQube.

Everything worked nicely from the SonarQube web portal, but when I tried to execute the SonarQube Runner on our build server, it failed with the following PostgreSQL error:

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

I’m not an expert in PostgreSQL, so with the help of a google search I discovered that the pg_hba.conf file is used to configure the security of your PostgreSQL database. By default only local connections are allowed. So it is not possible to connect to the PostgreSQL database from outside the server it is running on. As I had SonarQube running on the same server as my database, it worked for the SonarQube web portal. However my build server was a different machine(even in a different datacenter) and couldn’t reach the PostgreSQL database.

To fix it, you have to update the pg_hba.conf file in your PostgreSQL installation directory. I added the following line to the file just below the # TYPE DATABASE USER CIDR-ADDRESS METHOD header:

host all all 0.0.0.0/0 md5

Warning: Note that this line will give everyone(with a correct username and password) access to your PostgreSQL instance. It is recommended to limit the attack surface by specifying a more restrictive set of allowed IP addresses.

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more