Thread: Fatal Error: The pgAdmin 4 server could not be contacted:

Fatal Error: The pgAdmin 4 server could not be contacted:

From
Yatma SARR
Date:
Dear support, 

I have this issue:

image.png
Could you help, please? 

Best,
Yatma

--
Merci de prendre en considération votre responsabilité environnementale avant d'imprimer ce courriel.
Please consider your environmental responsibility before printing this email.
Attachment

Re: Fatal Error: The pgAdmin 4 server could not be contacted:

From
Aditya Toshniwal
Date:
Hi Yatma,

Can you please share the complete log ?

On Thu, Mar 31, 2022 at 3:12 AM Yatma SARR <yatma27@gmail.com> wrote:
Dear support, 

I have this issue:

image.png
Could you help, please? 

Best,
Yatma

--
Merci de prendre en considération votre responsabilité environnementale avant d'imprimer ce courriel.
Please consider your environmental responsibility before printing this email.


--
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Software Architect | edbpostgres.com
"Don't Complain about Heat, Plant a TREE"
Attachment

Re: Fatal Error: The pgAdmin 4 server could not be contacted:

From
Yatma SARR
Date:
Hello  Aditya, 

Finally it's working, I don't know why. I just reopen PgAdmin 4 v6 to see the complete log and it's working fine. 

Thanks for your support. 

Best,
Yatma

Le jeu. 31 mars 2022 à 07:38, Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> a écrit :
Hi Yatma,

Can you please share the complete log ?

On Thu, Mar 31, 2022 at 3:12 AM Yatma SARR <yatma27@gmail.com> wrote:
Dear support, 

I have this issue:

image.png
Could you help, please? 

Best,
Yatma

--
Merci de prendre en considération votre responsabilité environnementale avant d'imprimer ce courriel.
Please consider your environmental responsibility before printing this email.


--
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Software Architect | edbpostgres.com
"Don't Complain about Heat, Plant a TREE"


--
Merci de prendre en considération votre responsabilité environnementale avant d'imprimer ce courriel.
Please consider your environmental responsibility before printing this email.
Attachment

Re: Fatal Error: The pgAdmin 4 server could not be contacted:

From
David Bear
Date:
The first thing I would check is if the postgresql server is reachable using the psql command line tool. You may have already tried that but if not, that is always my first test. 

On Wed, Mar 30, 2022 at 10:38 PM Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> wrote:
Hi Yatma,

Can you please share the complete log ?

On Thu, Mar 31, 2022 at 3:12 AM Yatma SARR <yatma27@gmail.com> wrote:
Dear support, 

I have this issue:

image.png
Could you help, please? 

Best,
Yatma

--
Merci de prendre en considération votre responsabilité environnementale avant d'imprimer ce courriel.
Please consider your environmental responsibility before printing this email.


--
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Software Architect | edbpostgres.com
"Don't Complain about Heat, Plant a TREE"


--

David Bear

IT Manager

Heritage Academy — an A rated school

p: 480-461-4429

w: www.hamesa.com e: dbear@heritageacademyaz.com

https://www.facebook.com/HeritageAcademyAZ/


Attachment

Re: Fatal Error: The pgAdmin 4 server could not be contacted:

From
Ashesh Vashi
Date:
On Thu, Mar 31, 2022 at 8:37 PM David Bear <dbear@heritageacademyaz.com> wrote:
The first thing I would check is if the postgresql server is reachable using the psql command line tool. You may have already tried that but if not, that is always my first test.
David,

JFYI - you don't have to have the postgres server on the system for pgAdmin 4 to work.
pgAdmin 4 does not connect to the database server at the startup.

Yatma,

Please share the logs, as suggested by Aditya, to analyze the issue.

-- Ashesh

On Wed, Mar 30, 2022 at 10:38 PM Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> wrote:
Hi Yatma,

Can you please share the complete log ?

On Thu, Mar 31, 2022 at 3:12 AM Yatma SARR <yatma27@gmail.com> wrote:
Dear support, 

I have this issue:

image.png
Could you help, please? 

Best,
Yatma

--
Merci de prendre en considération votre responsabilité environnementale avant d'imprimer ce courriel.
Please consider your environmental responsibility before printing this email.


--
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Software Architect | edbpostgres.com
"Don't Complain about Heat, Plant a TREE"


--

David Bear

IT Manager

Heritage Academy — an A rated school

p: 480-461-4429

w: www.hamesa.com e: dbear@heritageacademyaz.com

https://www.facebook.com/HeritageAcademyAZ/


Attachment

Re: Fatal Error: The pgAdmin 4 server could not be contacted:

From
Yatma SARR
Date:
pgAdmin Runtime Environment
--------------------------------------------------------
Python Path: "C:\Program Files\pgAdmin 4\v6\python\python.exe"
Runtime Config File: "C:\Users\Yatma Sarr\AppData\Roaming\pgadmin\runtime_config.json"
pgAdmin Config File: "C:\Program Files\pgAdmin 4\v6\web\config.py"
Webapp Path: "C:\Program Files\pgAdmin 4\v6\web\pgAdmin4.py"
pgAdmin Command: "C:\Program Files\pgAdmin 4\v6\python\python.exe -s C:\Program Files\pgAdmin 4\v6\web\pgAdmin4.py"
Environment:
  - ALLUSERSPROFILE: C:\ProgramData
  - APPDATA: C:\Users\Yatma Sarr\AppData\Roaming
  - ChocolateyInstall: C:\ProgramData\chocolatey
  - ChocolateyLastPathUpdate: 132762714485028111
  - CHROME_CRASHPAD_PIPE_NAME: \\.\pipe\crashpad_14588_QOAGZRWUGLVKKYFC
  - CHROME_RESTART: NW.js|Whoa! NW.js has crashed. Relaunch now?|LEFT_TO_RIGHT
  - CommonProgramFiles: C:\Program Files\Common Files
  - CommonProgramFiles(x86): C:\Program Files (x86)\Common Files
  - CommonProgramW6432: C:\Program Files\Common Files
  - COMPUTERNAME: YATMA
  - ComSpec: C:\WINDOWS\system32\cmd.exe
  - DriverData: C:\Windows\System32\Drivers\DriverData
  - ESET_OPTIONS:                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                
  - FPS_BROWSER_APP_PROFILE_STRING: Internet Explorer
  - FPS_BROWSER_USER_PROFILE_STRING: Default
  - HOMEDRIVE: C:
  - HOMEPATH: \Users\Yatma Sarr
  - LOCALAPPDATA: C:\Users\Yatma Sarr\AppData\Local
  - LOGONSERVER: \\YATMA
  - NUMBER_OF_PROCESSORS: 4
  - OneDrive: C:\Users\Yatma Sarr\OneDrive
  - OS: Windows_NT
  - Path: C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\ImageMagick-7.1.0-Q16-HDRI;C:\ProgramData\Anaconda3;C:\ProgramData\Anaconda3\Library\mingw-w64\bin;C:\ProgramData\Anaconda3\Library\usr\bin;C:\ProgramData\Anaconda3\Library\bin;C:\ProgramData\Anaconda3\Scripts;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Git\cmd;C:\Program Files\nodejs\;C:\ProgramData\chocolatey\bin;C:\Program Files\SASHome\SASFoundation\9.4\core\sasexe;C:\Program Files\SASHome\Secure\ccme4;C:\Program Files\SASHome\SASFoundation\9.4\core\sasext;C:\Users\Yatma Sarr\AppData\Roaming\TinyTeX\bin\win32;C:\Users\Yatma Sarr\AppData\Local\Microsoft\WindowsApps;C:\Users\Yatma Sarr\AppData\Local\Programs\MiKTeX\miktex\bin\x64\;C:\Users\Yatma Sarr\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Yatma Sarr\AppData\Roaming\npm;C:\Program Files (x86)\heroku\bin
  - PATHEXT: .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
  - PGADMIN_INT_KEY: 0b90f1db-7b1c-4549-8bf6-e6b2011a4234
  - PGADMIN_INT_PORT: 62569
  - PGADMIN_SERVER_MODE: OFF
  - PROCESSOR_ARCHITECTURE: AMD64
  - PROCESSOR_IDENTIFIER: Intel64 Family 6 Model 78 Stepping 3, GenuineIntel
  - PROCESSOR_LEVEL: 6
  - PROCESSOR_REVISION: 4e03
  - ProgramData: C:\ProgramData
  - ProgramFiles: C:\Program Files
  - ProgramFiles(x86): C:\Program Files (x86)
  - ProgramW6432: C:\Program Files
  - PSModulePath: C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules
  - PUBLIC: C:\Users\Public
  - RTOOLS40_HOME: C:\RBuildTools\4.0
  - SESSIONNAME: Console
  - SystemDrive: C:
  - SystemRoot: C:\WINDOWS
  - TEMP: C:\Users\YATMAS~1\AppData\Local\Temp
  - TMP: C:\Users\YATMAS~1\AppData\Local\Temp
  - USERDOMAIN: YATMA
  - USERDOMAIN_ROAMINGPROFILE: YATMA
  - USERNAME: Yatma Sarr
  - USERPROFILE: C:\Users\Yatma Sarr
  - VBOX_MSI_INSTALL_PATH: C:\Program Files\Oracle\VirtualBox\
  - windir: C:\WINDOWS
--------------------------------------------------------

Le ven. 1 avr. 2022 à 07:41, Ashesh Vashi <ashesh.vashi@enterprisedb.com> a écrit :
On Thu, Mar 31, 2022 at 8:37 PM David Bear <dbear@heritageacademyaz.com> wrote:
The first thing I would check is if the postgresql server is reachable using the psql command line tool. You may have already tried that but if not, that is always my first test.
David,

JFYI - you don't have to have the postgres server on the system for pgAdmin 4 to work.
pgAdmin 4 does not connect to the database server at the startup.

Yatma,

Please share the logs, as suggested by Aditya, to analyze the issue.

-- Ashesh

On Wed, Mar 30, 2022 at 10:38 PM Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> wrote:
Hi Yatma,

Can you please share the complete log ?

On Thu, Mar 31, 2022 at 3:12 AM Yatma SARR <yatma27@gmail.com> wrote:
Dear support, 

I have this issue:

image.png
Could you help, please? 

Best,
Yatma

--
Merci de prendre en considération votre responsabilité environnementale avant d'imprimer ce courriel.
Please consider your environmental responsibility before printing this email.


--
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Software Architect | edbpostgres.com
"Don't Complain about Heat, Plant a TREE"


--

David Bear

IT Manager

Heritage Academy — an A rated school

p: 480-461-4429

w: www.hamesa.com e: dbear@heritageacademyaz.com

https://www.facebook.com/HeritageAcademyAZ/




--
Merci de prendre en considération votre responsabilité environnementale avant d'imprimer ce courriel.
Please consider your environmental responsibility before printing this email.
Attachment