From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Александр Шишенко <alex(at)shishenko(dot)com> |
Cc: | "pgadmin-hackers(at)postgresql(dot)org" <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: pgadmin, docker and ipv6 |
Date: | 2018-05-30 21:47:53 |
Message-ID: | CA+OCxows06oz5B3jTft+4kGMSng-WfwgWiuaziKRnTpan_RrEA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi
On Sun, May 27, 2018 at 7:13 AM, Александр Шишенко <alex(at)shishenko(dot)com>
wrote:
> Hello,
>
> I was running my pgadmin4 v2 on my ipv6-only subnet using docker image.
> After the update, I noticed, that you have changed your webserver from
> Apache to gunicorn, and it is configured to listen only on ipv4 network
> (0.0.0.0), so it is unreachable from my network without using docker-proxy
> (and I can't use that on my configuration).
>
> Please, consider switching to dual-stack networking in your configuration.
> It is just as simple as changing '--bind 0.0.0.0:${PGADMIN_LISTEN_PORT:-
> 443}' to '--bind [::]:${PGADMIN_LISTEN_PORT:-443}' in your
> pkg/docker/entrypoint.sh.
> --
>
>
Can you log this on the tracker please?
https://redmine.postgresql.org/projects/pgadmin4/issues/new
Thanks!
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Александр Шишенко | 2018-05-30 21:53:14 | Re: pgadmin, docker and ipv6 |
Previous Message | Dave Page | 2018-05-30 21:42:55 | Re: Container build hanging |