Yes. I restarted (Run->Services.msc->Postgresql13->Restart) after config file.
I can able to connect my postgres server using .net application with help of below connection string.
NpgsqlConnectionconn =newNpgsqlConnection("Server=127.0.0.1;User Id=postgres; "+
"Password=Postgresql@1;Database=Training;");
but my colleague is facing restriction issue when trying to connect my postgres server using my Ip Address,
NpgsqlConnectionconn =newNpgsqlConnection("Server=192.1xx.xx.50;User Id=postgres; "+
"Password=Postgresql@1;Database=Training;");
Regards
Muthu
On Sat, Dec 5, 2020 at 12:21 PM Hemil Ruparel <hemilruparel2002@xxxxxxxxx> wrote:
Did you restart postgres after changing pg_hba.conf?On Sat, Dec 5, 2020 at 11:56 AM Muthukumar.GK <muthankumar@xxxxxxxxx> wrote:Hi Nicklas,I have added a line "host all all 0.0.0.0/0 md5" in Pg_hba_conf.sample file and restarted postgres server. 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.RegardsMuthuOn Sat, Dec 5, 2020 at 1:36 AM Nicklas Avén <nicklas.aven@xxxxxxxxxxxxx> wrote:
On 4 December 2020 17:17:48 CET, Adrian Klaver <adrian.klaver@xxxxxxxxxxx> 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@xxxxxxxxxxx> 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@xxxxxxxxxxxxx> wrote:
On 4 December 2020 17:17:48 CET, Adrian Klaver <adrian.klaver@xxxxxxxxxxx> 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@xxxxxxxxxxx> 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
