need help understanding the error-message: Error Connecting to database FATAL : no pg_hba.conf entry We're trying to connect to a postgres/postgis installation on a remote server, using QGIS-Application. When accessing from another pc or from the same pc via pgadmin4v4 with the same credential/authentification settings, it works just fine. Therefore I conclude the pg_hba.conf is ok and it's in fact a problem of QGIS. 

In order to better understand the problem and maybe file a bug for QGIS I need help analysing the error message. It sais:

Area: dbname = &lt;databasename&gt;, host &lt;server-ip&gt;, port 5432, user &lt;username&gt;, password &lt;password&gt;, authcfg = &lt;id_of_auth_record&gt;

SSL error: certificate verify failed
FATAL: no pg_hba.conf entry for host &lt;some_other-ip&gt;, user &lt;username&gt;, database &lt;databasename&gt;, SSL off


My main questions:


shouldn't the host-ip addresses be identical? Could it be part of the problem, that the second ip mentioned is not the correct server-ip? As far as I can see, there should be only one host (remote server) and one client involved (pc trying to get access).
why doesn't it say "no pg_hba.conf entry for client ..."
does QGIS think is it is a certificate problem, or a pg_hba.conf problem, or is that both the same


Update: further Details about the installation


Client-PC1: Win10, QGIS 3.4 [error] pgAdmin 4v4 [access ok]
Client-PC2: Win10, QGIS 3.10 [access ok] pgAdmin 4v4 [access ok]
Server: postgres 12
pg_hba.conf:


# Database administrative login by Unix domain socket
local   all             postgres                                peer

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
local   all             all                                     peer
# IPv4 local connections:
host    all             all             0.0.0.0/0               scram-sha-256
# IPv6 local connections:
hostssl all             all             ::0/0                   scram-sha-256
The no pg_hba.conf entry message is a generic message that means that something did not work out with the connection attempt. PostgreSQL uses a generic message, so that an attacker cannot draw conclusions from the kind of message she gets.

The true problem is probably:

SSL error: certificate verify failed


That would mean that client and server attempt to start an encrypted connection, but the client does not recognize the server certificate (because the certificate that was used to sign the server certificate is not a certification authority that the client recognizes).