On Wed, 2023-11-22 at 23:33 +0530, Atul Kumar wrote:
> Please can you share any command for due diligence whether ip is resolved to
> ipv6 ?.
Not a lot of diligence is due to figure out that you can use
ping localhost
Yours,
Laurenz Albe
On 11/22/23 10:01 AM, Adrian Klaver wrote:
On 11/22/23 9:55 AM, Andreas Kretschmer wrote:
Am 22.11.23 um 18:44 schrieb Atul Kumar:
I am giving this command
psql -d postgres -U postgres -p 5432 -h localhost
Then only I get that error.
so localhost resolved to an IPv6 - address ...
Yeah
On 11/22/23 10:03 AM, Atul Kumar wrote:
Please can you share any command for due diligence whether ip is
resolved to ipv6 ?.
This:
psql -d postgres -U postgres -p 5432 -h localhost
where pretty sure
/etc/hosts
is resolving localhost --> ::1
On Wed, Nov 22, 2023 at 11:25 PM Andreas Kre
Please can you share any command for due diligence whether ip is resolved
to ipv6 ?.
On Wed, Nov 22, 2023 at 11:25 PM Andreas Kretschmer
wrote:
>
>
> Am 22.11.23 um 18:44 schrieb Atul Kumar:
> > I am giving this command
> > psql -d postgres -U postgres -p 5432 -h localhost
> > Then only I get t
On 11/22/23 9:55 AM, Andreas Kretschmer wrote:
Am 22.11.23 um 18:44 schrieb Atul Kumar:
I am giving this command
psql -d postgres -U postgres -p 5432 -h localhost
Then only I get that error.
so localhost resolved to an IPv6 - address ...
Yeah, you should take a look at:
/etc/hosts
In
Am 22.11.23 um 18:44 schrieb Atul Kumar:
I am giving this command
psql -d postgres -U postgres -p 5432 -h localhost
Then only I get that error.
so localhost resolved to an IPv6 - address ...
but when I pass ip or hostname of the local server then I don't get
such error message
1. psql
I am giving this command
psql -d postgres -U postgres -p 5432 -h localhost
Then only I get that error.
but when I pass ip or hostname of the local server then I don't get such
error message
1. psql -d postgres -U postgres -p 5432 -h
2. psql -d postgres -U postgres -p 5432 -h
I don;t get that
On 11/22/23 09:03, Atul Kumar wrote:
The entries that I changed were to replace the md5 with scram-sha-256
and remove unnecessary remote IPs.
FYI from:
https://www.postgresql.org/docs/current/auth-password.html
md5
The method md5 uses a custom less secure challenge-response
mechanism. I
The error message is EXPLICIT, and DOES NOT LIE. Either someone removed
the ::1 entry, or you're now using IPv6.
On Wed, Nov 22, 2023 at 12:03 PM Atul Kumar wrote:
> The entries that I changed were to replace the md5 with scram-sha-256 and
> remove unnecessary remote IPs.
>
> But it has nothing
The entries that I changed were to replace the md5 with scram-sha-256 and
remove unnecessary remote IPs.
But it has nothing to do with connecting the server locally with "psql -d
postgres -U postgres -h localhost"
But when I try to connect it locally I get this error. So it is related to
local co
On Wed, Nov 22, 2023 at 11:22 AM Atul Kumar wrote:
> Hi,
>
> I have postgres 12 running in centos 7, recently I changed the
> authentication of entries of pg_hba.conf to scram-sh-256 for localhost.
>
>
I think you changed something else, at the same time.
> Since then I have started getting the
On 11/22/23 08:21, Atul Kumar wrote:
Hi,
I have postgres 12 running in centos 7, recently I changed the
authentication of entries of pg_hba.conf to scram-sh-256 for localhost.
Since then I have started getting the below error:
no pg_hba.conf entry for host "::1", user "postgres", database "p
Am 22.11.23 um 17:21 schrieb Atul Kumar:
Since then I have started getting the below error:
no pg_hba.conf entry for host "::1", user "postgres", database "postgres
What I am missing here, please suggest.
that's sounds like an issue with IPv6. Do you use it? Disable it or add
an en
Hi,
I have postgres 12 running in centos 7, recently I changed the
authentication of entries of pg_hba.conf to scram-sh-256 for localhost.
Since then I have started getting the below error:
no pg_hba.conf entry for host "::1", user "postgres", database "postgres
The entry of pg_hba.conf is l
14 matches
Mail list logo
