public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: Marcelo Marloch <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Can't Remote connection by IpV6
Date: Thu, 6 Jun 2024 12:02:00 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAM+GY4+UyePxEhcs-xJHYUFhCAm8o7VKP_AOtPiS8ZrQiYyFPg@mail.gmail.com>
References: <CAM+GY4JgCYPwfCP25_TchAyD7V_X4m1haW6MM+HEiaYL3i_Qpw@mail.gmail.com>
<[email protected]>
<CAM+GY4+UyePxEhcs-xJHYUFhCAm8o7VKP_AOtPiS8ZrQiYyFPg@mail.gmail.com>
On 6/6/24 10:37, Marcelo Marloch wrote:
Reply to list also.
Ccing list
> Hi Adrian thanks for your help, Server is running on windows and I set
> open 5432 port on windows firewall, I did not see any options regarding
> if ipv4 or v6. client also uses windows and connects through odbc
> driver. over ipv4 it connects flawlessly if it got a public ipv4 but
> when I set odbc driver server field to an Ipv6 it shows message:
> connection to server at (ipv6 ip), port 5432 failed: Connection time
> out(0x0000274C/10060) is the server running on that host and accepting
> TCP/IP connections? the same message is shown if provider sets to me a
> not public ipv4
To be clear the Postgres server is running on a Windows instance that is
itself running on a cloud(?) provider. Seems to me this still points at
a firewall, namely one the provider has set up in front of your Windows
instance. The hint would be the public IPv4 address working vs the
private IPv4 address not working. There is also the issue of whether the
IP addresses that are not on the public side of the internet are being
drawn from IP private network ranges(see
https://en.wikipedia.org/wiki/IP_address) that are not publishable to
the public internet. You may need to talk with the provider and see how
they suggest you punch a hole through to your Postgres server.
>
> thank you very much!
>
> Em qui., 6 de jun. de 2024 às 12:03, Adrian Klaver
> <[email protected] <mailto:[email protected]>> escreveu:
>
> On 6/6/24 07:46, Marcelo Marloch wrote:
> > Hi everyone, is it possible to remote connect through IpV6? IpV4
> works
> > fine but I cant connect through V6
> >
> > postgresql.conf is to listen all address and pg_hba.conf is set with
> > host all all :: md5 i've tried ::/0 and ::0/0 but had no success
>
> Is the firewall open for IPv6 connections to the Postgres port?
>
> Did you reload the server after making the configuration changes?
>
> Define in more detail what 'no success' means.
>
> >
> > my provider is out of ipv4 and they're sending ips by cgnat if I
> want a
> > public ipv4 I have to sign a very expensive service fee
> >
> > thanks a lot
>
> --
> Adrian Klaver
> [email protected] <mailto:[email protected]>
>
--
Adrian Klaver
[email protected]
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Can't Remote connection by IpV6
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox