Right - it's not designed to run under the runtime, and then be access via a browser. There's now a security key that is defined by the runtime, that needs to be supplied by any clients that are connecting. That is to prevent other users on multi-user systems from connecting to the pgAdmin server and getting access to your saved connections etc.
If you want to run in a browser, you really need to setup a Python virtual environment and run the server directly. The README in the source tree details how to do that. On Tue, Mar 28, 2017 at 5:22 AM, Neel Patel <neel.pa...@enterprisedb.com> wrote: > Hi Maciek, > > For the security reason, v4 1.3 do not access the same runtime port with > browser. > > Thanks, > Neel Patel > > On Tue, Mar 28, 2017 at 2:00 PM, matshyeq <matsh...@gmail.com> wrote: >> >> Hi, >> >> For v4.1.1 I was able to copy URL (ie. http://localhost:55235/browser/#) >> and access interface through Chrome. >> Now, with v4.1.3, when I'm trying same I get: >> >> The server could not verify that you are authorized to access the URL >> requested. You either supplied the wrong credentials (e.g. a bad password), >> or your browser doesn't understand how to supply the credentials required. >> >> Is there some switch in v4.1.3 (MacOS) to change so I can still use web >> browser UI? >> >> Thank you, >> Kind Regards >> ~Maciek > > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
