On 21 Mar 2018 20:02, "Dave Page" <dp...@pgadmin.org> wrote:
On Wed, Mar 21, 2018 at 2:29 PM, Murtuza Zabuawala <murtuza.zabuawala@ enterprisedb.com> wrote: > Yes, that's cookie related issue (RM#3197), To fix that I added below in > my config_local.py and it started working again, > > DEFAULT_SERVER = '0.0.0.0' > COOKIE_DEFAULT_DOMAIN = SESSION_COOKIE_DOMAIN = DEFAULT_SERVER > I haven't had to do that - and the 3.0 packages I just built for Windows and Mac worked fine on fresh VMs without anything like that being needed. These changes required when you change DEFAULT_SERVER in config_local.py -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
