Re: PgAdmin4 stopped working: "The application server could not be contacted." - Mailing list pgadmin-support

From Dave Page
Subject Re: PgAdmin4 stopped working: "The application server could not be contacted."
Date
Msg-id CA+OCxowBjrP0u-+-NDdrK69sopSG7eCR1kKwxFeW4xEBCgNzsQ@mail.gmail.com
Whole thread Raw
In response to Re: PgAdmin4 stopped working: "The application server could not becontacted."  (Johann Spies <jspies@sun.ac.za>)
List pgadmin-support
Hi

On Wed, Sep 12, 2018 at 10:12 AM, Johann Spies <jspies@sun.ac.za> wrote:
On Wed, Sep 12, 2018 at 09:05:37AM +0100, Dave Page wrote:

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

The log is complaining about not being able to contact the server on
port 63334 (I am using a ssh tunnel not defined in pgadmin4).

The last part of the log:
---------------------------------------------------------
2018-09-06 11:05:26,060: ERROR  pgadmin:        Could not connected to server(#2) - 'kbase'.
Error: could not connect to server: Connection refused
        Is the server running on host "localhost" (::1) and accepting
        TCP/IP connections on port 63334?
could not connect to server: Connection refused
        Is the server running on host "localhost" (127.0.0.1) and accepting
        TCP/IP connections on port 63334?
-----------------------------------------------------
but on the commandline I can do:
------------------------------------------------------
js@sitasie ~ 11:05:01> psql -h localhost -p 63334 wos
SET

Welcome, my magistrate

psql (10.5 (Debian 10.5-1.pgdg100+1), server 10.4 (Debian 10.4-2.pgdg90+1))
SSL connection (protocol: TLSv1.2, cipher: ECDHE-RSA-AES256-GCM-SHA384, bits: 256, compression: off)
Type "help" for help.

localhost js@wos=#
------------------------------------------------------

I'm confused. Your first message said the error was that the application server couldn't be contacted, but this seems to imply that pgAdmin is up and running and the failure is when it's trying to connect to a database server.

Do those log messages occur when pgAdmin is actually trying to start (i.e. maybe pgAdmin is trying to restore a connection at startup, then failing, and the timeout of that is also causing the runtime to timeout when connecting to the app server)? 

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

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

pgadmin-support by date:

Previous
From: Johann Spies
Date:
Subject: Re: PgAdmin4 stopped working: "The application server could not becontacted."
Next
From: Vladimir Ryabtsev
Date:
Subject: Re: pgAdmin in Docker: independent users storage