Re: Accessing Postgres Server and database from other Machine

On 12/4/20 10:26 PM, Muthukumar.GK wrote:
> Hi Nicklas,
> 
>    I have added a line "host  all  all 0.0.0.0/0 <http://0.0.0.0/0> 
> md5" in Pg_hba_conf.sample file and restarted postgres server. 

Again, changing lines in the *.sample file will not be of any use. The 
actual pg_hba.conf file is in the same location as I posted previously 
for the postgresql.conf file.

> porstgres port has been added in windows firewall (Windows10)as well.  
> But my colleague is still facing the below error when connecting my 
> postgres server from .net appplication.
> 
> Error is - no connection could be made because the target machine 
> actively refused it.
> 
> Regards
> Muthu
> 
> On Sat, Dec 5, 2020 at 1:36 AM Nicklas Avén <nicklas.aven@jordogskog.no 
> <mailto:nicklas.aven@jordogskog.no>> wrote:
> 
> 
> 
>     On 4 December 2020 17:17:48 CET, Adrian Klaver
>     <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
>      >On 12/4/20 8:03 AM, Paul Förster wrote:
>      >> Hi Adrian,
>      >>
>      >>> On 04. Dec, 2020, at 16:13, Adrian Klaver
>      ><adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
>      >>> That is the wrong file, the *.sample is the giveaway.
>      >>
>      >> hmmm, I'd rather call it essential reference documentation or
>      >template for automation. It's perfectly well suited to automatically
>      >strip all comments and then diff the result to ones real world
>      >postgresql.conf or some other version postgresql.conf file to find
>      >parameters that have been removed or changed with a new PostgreSQL
>      >version. This is highly useful for planning migrations and have a
>     quick
>      >reference what to check for before actually migrating. So for me this
>      >is much more than just a giveaway.
>      >>
>      >
>      >Yes, but for changing the behavior of a running instance it is the
>      >wrong
>      >file and it's extension is a clue.
> 
> 
>     You will prabably also need to change in tge pg_hba.conf file. At
>     least in linux there is no entry for connections from the outside
>     there. You will need a "host" entry accepting any ip address or
>     specify what ip your collegue is connecting from if possible. I have
>     missed this step a few times and banged my head.
> 
>     /Nicklas
> 
> 
> On Sat, Dec 5, 2020 at 1:36 AM Nicklas Avén <nicklas.aven@jordogskog.no 
> <mailto:nicklas.aven@jordogskog.no>> wrote:
> 
> 
> 
>     On 4 December 2020 17:17:48 CET, Adrian Klaver
>     <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
>      >On 12/4/20 8:03 AM, Paul Förster wrote:
>      >> Hi Adrian,
>      >>
>      >>> On 04. Dec, 2020, at 16:13, Adrian Klaver
>      ><adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
>      >>> That is the wrong file, the *.sample is the giveaway.
>      >>
>      >> hmmm, I'd rather call it essential reference documentation or
>      >template for automation. It's perfectly well suited to automatically
>      >strip all comments and then diff the result to ones real world
>      >postgresql.conf or some other version postgresql.conf file to find
>      >parameters that have been removed or changed with a new PostgreSQL
>      >version. This is highly useful for planning migrations and have a
>     quick
>      >reference what to check for before actually migrating. So for me this
>      >is much more than just a giveaway.
>      >>
>      >
>      >Yes, but for changing the behavior of a running instance it is the
>      >wrong
>      >file and it's extension is a clue.
> 
> 
>     You will prabably also need to change in tge pg_hba.conf file. At
>     least in linux there is no entry for connections from the outside
>     there. You will need a "host" entry accepting any ip address or
>     specify what ip your collegue is connecting from if possible. I have
>     missed this step a few times and banged my head.
> 
>     /Nicklas
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com