From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Mike Surcouf <mikes(at)surcouf(dot)co(dot)uk> |
Cc: | "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: pgAdmin 1.4 on Windows 7 x64 |
Date: | 2017-05-10 08:30:38 |
Message-ID: | CA+OCxoz=WC2i7i5wLaNO4EQdkHAUogOyc08ZSyH1cKC9CtBm7A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Tue, May 9, 2017 at 9:42 PM, Mike Surcouf <mikes(at)surcouf(dot)co(dot)uk> wrote:
> Is pgadmin server component listening on IPv6 as well or only IPv4.
> Windows will always return IPv6 look back address for localhost if both are
> available apparently.
>
That was sounding like a real possibility when I read it before going to
bed last night. Unfortunately, when I tested this morning I found it's not
the cause, at least for me. My Windows 7 box does have v6 enabled (and does
return ::1 for localhost) but pgAdmin still worked fine. I even tried
completely disabling v4, but it still worked.
I think the next step is to try disabling the proxy. If that works, we then
need to figure out a real solution, but at least it'll point us in the
right direction.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Surcouf | 2017-05-10 08:32:00 | Re: pgAdmin 1.4 on Windows 7 x64 |
Previous Message | giovafr | 2017-05-10 07:08:59 | Re: pgAdmin 1.4 on Windows 7 x64 |