Re: PgAdmin4 stopped working: "The application server could not be contacted."

On Wed, Sep 12, 2018 at 8:18 AM, Johann Spies <jspies(at)sun(dot)ac(dot)za> wrote:

> Apologies for the rant.
>
> When will we have a pgadmin that just works?
>
> I am on Debian Sid with a pgdg-installation (desktop) of pgadmin4.
>
> Today I cannot use it: "The application server could not be contacted."
>
> I have used it in the past with some frustration but it was usable.
>
> Version: 3.3-1.pgdg100+1 - the latest available from pgdg.
>
> I do not want to reconfigure everything every now and then.
>
> I have used other tools like pgadmin3 (breaking from time to time,
> but mostly working), omnidb-app which just works and Datagrip
> (which I do not particularly like) which also do the job.
>
> I sometimes just look for functionality available in pgadmin3 and
> pgadmin4 that is not available in the others.
>
> Unless the reliability of pgadmin4 improves a lot, I will probably, for
> my own peace of mind, take a decision to not try it out again.
>

It does "just work" for the vast majority of users - and we'd love to
figure out the cause of this problem for those few that are affected by it.
Unfortunately it's proving quite elusive.

Can you provide logs? You may need to enable logging per
https://www.pgadmin.org/faq/#8.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company