blocks|key|4366212|text|最终起作用的是降级到pgadminIII-v.1.22|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4366213|entityMap|0|LINK|mutability|MUTABLE|url|https://ftp.postgresql.org/pub/pgadmin/pgadmin3/v1.22.2/win32/pgadmin3-1.22.2.zip^0|A|H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

What finally worked was downgrading to <a href="https://ftp.postgresql.org/pub/pgadmin/pgadmin3/v1.22.2/win32/pgadmin3-1.22.2.zip" rel="noreferrer">pgadminIII-v.1.22</a>:

blocks|key|4366769|text|如果您使用的是Mac，这里有一个修复:打开终端并运行以下命令|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4366770|pg_ctl+-D+/usr/local/var/postgres+-l+/usr/local/var/postgres/server.log+restart|code-block|syntax|javascript|4366771|而对于其他操作系统，只需重新启动Postgresql服务器即可解决|4366772|然后启动pgAdmin4，它将照常启动|4366773|如果保存了某人，则共享或评论|4366774|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

if you are using Mac OS X here is a fix:
Open terminal and run this command 

<pre><code>pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log restart
</code></pre>

and for other OS just restart your Postgresql server, it will solve

Then start pgAdmin4, it will start as normal

Share or comment if saved someone

blocks|key|4366360|text|我在升级到pgAdmin+4+(v1.6)时发现了同样的问题。在Windows上，我发现清除C:\Users\%25USERNAME%25\AppData\Roaming\pgAdmin\sessions文件夹中的内容为我解决了这个问题。我认为它试图使用以前版本中的会话，但失败了。我知道这个问题被标记为已回答，但降级可能并不总是一个选项。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4366361|注意:+AppData\Roaming\pgAdmin是一个隐藏文件夹。|4366362|entityMap^0|1A|1G|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

I found the same issue when upgrading to pgAdmin 4 (v1.6). On Windows I found that clearing out the content inside <code>C:\Users\%USERNAME%\AppData\Roaming\pgAdmin\sessions</code> folder fixed the issue for me. I believe it was attempting to use the sessions from the prior version and was failing. I know the question was marked as answered, but downgrading may not always be an option.
Note: AppData\Roaming\pgAdmin is a hidden folder.

blocks|key|4366395|text|我在windows上也遇到了同样的问题。我安装了v1.6和v2.0。卸载1.6版允许我登录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4366396|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had same issue on windows. I had v1.6 installed as well as v2.0. Uninstalling v1.6 allowed me to login.

blocks|key|4366436|text|我们也有同样的问题。因此，文件中没有任何更改。但是使用管理员启动pgAdmin+4。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4366437|下面的步骤。1.右击pgAdmin+4图标2.选择“以管理员身份运行”|4366438|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

We got the same issue. so no any change in the file.
but start pgAdmin 4 using administrator.

The following step.
1. right click pgAdmin 4 icon
2. select "Run As Administrator"

blocks|key|4366922|text|在我将PostgreSQL+9.4升级到9.6之后遇到了这个问题。9.4二进制包有PgAdmin+3，而9.6有PgAdmin+4。我在全新安装(我完全卸载并重新安装)+PostgreSQL后解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4366923|但是，在不同的情况下，您可以尝试以管理员身份运行pgAdmin+4应用程序。这应该可以修复错误。|4366924|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Got this issue after I upgraded PostgreSQL 9.4 to 9.6. The 9.4 binary package had PgAdmin 3 while 9.6 came with PgAdmin 4. I resolved it after a clean installation (I completely uninstalled and reinstalled) of PostgreSQL. 

However, under different circumstances, you could try running the pgAdmin 4 application as an Administrator. This should fix the error.

blocks|key|4366488|text|我在macosx上也遇到了同样的问题，我重新命名了.pgadmin+(in+/users/costa)+to+.pgadminx，并且能够启动pgAdmin4。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4366489|entityMap^0|2|6|P|13|1Z|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

I had the same issue on the <code>macosx</code> and I renamed <code>.pgadmin (in /users/costa) to .pgadminx</code> and I was able to start <code>pgAdmin4</code>.

blocks|key|4366519|text|下载pgadmin4+v2.0并安装它没有问题自动柜员机强制安装。试试看。这就是我的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4366520|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

downloaded pgadmin 4 v2.0 and install it no problem atm on force installation. try it. that was solution for me.

blocks|key|4366587|text|我需要在这里添加这一点，因为我对这条消息有几个问题。如果您最近升级到High+Sierra，您会发现最新版本(pgadmin+4.20)将继续显示消息"Application+Server+find‘t+be+Contacted“。在Mac上这实际上意味着python无法在~/.pgadmin中配置您的环境|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4366588|此目录存储您设置和配置的所有内容，甚至是在您的用户副本pgadmin上运行的内容的日志。|4366589|在高塞拉解决这个问题的方法是sqlite3。如果您查看该目录，您将看到所有内容都存储在sqlite3文件中。|4366590|当4.20版本的pgadmin发布时，它是随sqlite3.19之后的版本一起发布的，出现问题的原因是High+Sierra随sqlite3.19一起发布，因此要解决此问题，您需要在打包程序中使用最新版本替换旧版本的sqlite3。|4366591|现在请注意，MacosX%2B都使用sqlite来存储mac上大多数应用程序的详细信息，所以你需要确保不只是擦除旧版本，还必须让两个版本和谐共存，以避免在mac上发生任何重大事件。|4366592|1)下载brew+https://brew.sh/|offset|length|4366593|2)更新brew并升级brew以确保其为最新版本|4366594|3)+brew安装sqlite3|4366595|4)+mv+/usr/bin/sqlite3+/usr/bin/sqlite3.os|4366596|5)+ln+-s+/usr/local/Cellar/sqlite/3.21.0/bin/sqlite3+/usr/bin/sqlite3|4366597|6)+/usr/bin/sqlite3+-version+(检查版本是否高于3.19)|4366598|现在，您可以照常打开pgadmin|4366599|entityMap|0|LINK|mutability|MUTABLE|url|https://brew.sh/^0|0|0|0|0|0|9|G|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|19|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1A|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1B|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1C|8|@]|9|@$L|1D|M|1E|1|1F]]|A|$]]|$1|N|3|O|5|6|7|1G|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1H|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1I|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1J|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1K|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1L|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16]]]]

I need to add this here because I've had several issues with this message. If you have recently upgraded to High Sierra you will find the latest (pgadmin 4.20) will keep appearing with the message "Application Server Could Not be Contacted". What this actually means on Macs is that python was unable to configure your environment in ~/.pgadmin

This directory stores all the things you setup and configure and even logs of what was ran on your user copy usage of pgadmin.

The way to fix this issue on High Sierra is down to sqlite3. If you look in that directory you'll see everything is stored in sqlite3 files.

When version 4.20 of pgadmin was released it was shipped with a version later than sqlite3.19 and the problem arises because High Sierra is shipped with sqlite3.19, so to fix this issue, you need to replace the old version of sqlite3 with the latest on your packager.

Now be aware, MacosX+ all use sqlite to store details for the majority of apps on your mac, so you'll need to make sure you do not just wipe the old version but you'll have to have both versions co-existing together in harmony to avoid anything major occurring on your mac.

1) download brew <a href="https://brew.sh/" rel="nofollow noreferrer">https://brew.sh/</a>

2) update brew and upgrade brew to make sure it's up-to-date

3) brew install sqlite3

4) mv /usr/bin/sqlite3 /usr/bin/sqlite3.os

5) ln -s /usr/local/Cellar/sqlite/3.21.0/bin/sqlite3 /usr/bin/sqlite3

6) /usr/bin/sqlite3 -version (check version is later than 3.19)

You can now proceed to open up pgadmin as normal

blocks|key|4366664|text|对于我在Windows10forPostgreSQL10版本中的例子，它的工作原理是将web文件夹中的config_distro.py中的SERVER_MODE改为False，按照以下配置设置：https://www.pgadmin.org/docs/pgadmin4/dev/desktop_deployment.html。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4366665|在这个答案(https://superuser.com/a/1131964)中提到了关于python的其他设置，但我刚刚更改了SERVER_MODE，它起作用了。|4366666|entityMap|0|LINK|mutability|MUTABLE|url|https://www.pgadmin.org/docs/pgadmin4/dev/desktop_deployment.html|1|https://superuser.com/a/1131964^0|1F|G|1X|B|2A|5|2P|1T|0|0|1R|B|6|V|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|F|3|G|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@$9|14|A|15|1|16]]|E|$]]|$1|H|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]]]

For my case in Windows 10 for postgresql 10 version, it worked by changing <code>SERVER_MODE</code> to <code>False</code> in <code>config_distro.py</code> placed in web folder, as per these configuration settings: <a href="https://www.pgadmin.org/docs/pgadmin4/dev/desktop_deployment.html" rel="nofollow noreferrer">https://www.pgadmin.org/docs/pgadmin4/dev/desktop_deployment.html</a>.

There are other settings mentioned in this answer (<a href="https://superuser.com/a/1131964">https://superuser.com/a/1131964</a>) regarding python but I just changed <code>SERVER_MODE</code> and it worked.

blocks|key|4366699|text|请在Windows任务管理器中终止它，然后重试。当从不同的应用程序访问服务器时，似乎存在某种问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4366700|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Kill it in Windows Task Manager and then try again. It seems that there is some sort of a problem when accessing the server from different applications.

blocks|key|4367248|text|您最近是否安装了新版本的pgAdmin？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4367249|这个问题(以及误导性消息)只是由于旧版本的pgAdmin无法读取由新版本的pgAdmin保存的设置！|4367250|确保您启动的是正确的pgAdmin版本(您的快捷方式可能指向旧版本!)和/或卸载旧版本:升级向导不会为您执行此操作！|4367251|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Have you recently installed a new version of pgAdmin ?

This issue (and the misleading message) is simply due to the fact that old versions of pgAdmin are unable to read the settings saved by a newer version of pgAdmin !

Make sure you're starting the right version of pgAdmin (your shortcuts are likely to point to the old version !) and/or uninstall the old version: the upgrade wizard doesn't do it for you !

blocks|key|4366876|text|我也有同样的问题，但是以管理员的身份运行它是可行的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4366877|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem, but running it as an admin worked.

blocks|key|4367465|text|对于我来说，在Windows2012r2上，它只有在我重新安装pgAdmin+4到文件夹c:\pgAdmin4之后才开始工作。没有空格和任何特殊字符。所以我在NTFS中给了这个文件夹完全的权限。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4367466|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

As for me on windows 2012r2 it's start to work only after I reinstall pgAdmin 4 to folder c:\pgAdmin4. With out spaces and any special chars.
And all so I give full permission to this folder in NTFS.

blocks|key|4367045|text|在我为pgAdmin+4+v2安装了python2.7之后，它就可以工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4367046|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It worked for me after installing python2.7 for pgAdmin 4 v2

blocks|key|4367557|text|我在装有psql+postgres+postgres的Windows10上使用命令提示符。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4367558|然后我启动pgAdmin4，它就能工作了。|4367559|entityMap^0|4|M|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

I use the cmd prompt on Windows 10 with <code>psql postgres postgres</code>. 

Then I launch pgAdmin4 and it works.

blocks|key|4367606|text|我在Windows10上也遇到了同样的问题，安装了新的PostgreSQL+10。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4367607|我通过将路径C:\PostgreSQL\10\bin+({您的postgresql路径}\bin)包含到系统环境变量来解决它。|4367608|要访问环境变量:控制面板>系统和安全>系统或右键单击PC，然后>高级系统设置>环境变量>系统变量>路径>编辑。|4367609|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I had the same issue on Windows 10, with a new installation of PostgreSQL 10.

I solved it by including the path C:\PostgreSQL\10\bin ({your path to postgresql}\bin) to system environment variables.

To access environment variables: Control Panel > System and security > System or right click on PC, then > Advance system settings > Environment variables > System variables > Path > Edit.

blocks|key|4367643|text|我在linux+fedora27上使用pgadmin4+v2.1时遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4367644|通过安装缺少的依赖项解决:+python3-flask-babelex|4367645|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had this problem with pgadmin4 v2.1 on linux fedora 27

Solved by installing a missing dependency: 
python3-flask-babelex

blocks|key|4367557|text|通常在安装了多个版本的pgadmin或尝试升级时发生。甚至我尝试了所有的方法，从终止“在端口5432上运行PID”到“改变服务器模式”。在我的例子中，我卸载postgres，然后在不同的端口上重新安装它(5433)。后来，我通过cmd打开了它(右击cmd并选择"run+cmd+as+an+Administrator")。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4367558|📷|atomic|offset|length|4367559|​|4367560|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/b4eab002d62ab9b4d0a8f41e6e054764.jpeg|imageAlt^0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@$E|T|F|U|1|V]]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P|Q|-4]]]]

Happens mostly when you have multiple versions of pgadmin installed or while trying to upgrade. Even I tried everything from killing the "running PID on port 5432" to "changing the server mode". In my case I uninstall postgres and re-install it again on different port(5433). 
Later, I opened it through cmd(right click on cmd and select "run cmd as an Administrator").<a href="https://i.stack.imgur.com/ZL9NS.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ZL9NS.jpg" alt="enter image description here"></a>

blocks|key|4367599|text|你应该降级到pgadmin3。它在Windows10.1和postrgreSQL+9.6上都能用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4367600|entityMap|0|LINK|mutability|MUTABLE|url|https://ftp.postgresql.org/pub/pgadmin/pgadmin3/v1.22.2/win32/pgadmin3-1.22.2.zip^0|6|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You should downgrade to <a href="https://ftp.postgresql.org/pub/pgadmin/pgadmin3/v1.22.2/win32/pgadmin3-1.22.2.zip" rel="nofollow noreferrer">pgadmin3</a>. It Worked for me on windows 10.1 with postrgreSQL 9.6.

blocks|key|4367821|text|我也遇到了这个问题。我用的是老版本的pgAdmin+4+(1.6)和2.0。我猜现在两个都老了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4367822|在任何情况下，都可以完全卸载这两个版本，然后重新安装2.0。|4367823|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I ran into this issue as well. Windows 10. I had older version of pgAdmin 4 (1.6) and 2.0. I guess both are older now.

In any case a complete uninstall of both versions and a reinstall of 2.0 worked.

blocks|key|4367667|text|我在Windows10中以Run+as+Administrator身份运行pgAdmin+4就解决了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4367668|entityMap^0|D|K|11|9|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I Fixed it in windows 10 just running <code>pgAdmin 4</code> as <code>Run as Administrator</code> .

blocks|key|4367864|text|删除C:\Users\%25USERNAME%25\AppData\Roaming\pgAdmin目录的内容对我来说很有效！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4367865|entityMap^0|2|17|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Deleting the contents of <code>C:\Users\%USERNAME%\AppData\Roaming\pgAdmin</code> directory worked for me!

blocks|key|4367715|text|这通常是防火墙问题。然后，防火墙日志会显示127.0.0.1:和127.0.0.1:之间的丢弃数据包，其中127.0.0.1:是浏览器中显示的端口，无法与其建立连接。这意味着pgAdmin客户端(high_port_1)和pgAdmin服务器(high_port_2)之间的连接被阻止。检查您的防火墙日志，如果您发现如上所述的丢弃数据包，请相应调整您的防火墙设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4367716|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This is often a firewall problem. The firewall log then shows dropped packets between 127.0.0.1: and 127.0.0.1:, where the latter is the port shown in the Browser to get no connection with. This means, that the connection between pgAdmin client (high_port_1) and pgAdmin server (high_port_2) is blocked. Check your firewall log and if you find dropped packets like described, adapt your firewall settings accordingly.

blocks|key|4367918|text|只需单击pgadmin+4图标并以管理员身份运行。允许访问权限。它将在本地启动。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4367919|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Just click on that pgadmin 4 icon and run as administrator. Allow the access permissions. It will start locally.

blocks|key|4367782|text|导致Windows4启动失败的原因有很多。造成我这种情况的原因是我的pgAdmin系统语言与英语或utf-8无关。将系统区域设置更改为英语解决了启动问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4367783|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

A variety of reasons attribute to the failure boot of pgAdmin 4. The reason to my situation is that my Windows system language is not English or utf-8 related. Changing the system locale to English solved the starting issue.

blocks|key|4368009|text|最后一招HKEY_CURRENT_USER\Software\pgadmin\pgadmin4导出/删除在这里您知道要做什么:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4368010|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Last resort HKEY_CURRENT_USER\Software\pgadmin\pgadmin4 export/delete you know what to do here :)

blocks|key|4367847|text|删除这个(C:\Users\YourUsernameOrAdmin\AppData\Roaming\pgAdmin)文件夹中的所有内容可以帮助我再次启动pgAdmin4服务器|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4367848|我现在运行的是pgAdmin4+v4.27。在我升级到pgAdmin4+v4.28之后，问题开始了，即服务器没有启动。我尝试了许多方法，包括将.js的内容类型从text/plain更改为test/javascript，但都不起作用。最后，删除C:\Users\YourUsernameOrAdmin\AppData\Roaming\pgAdmin中的所有内容对我有帮助|4367849|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Deleting everything from this (C:\Users\YourUsernameOrAdmin\AppData\Roaming\pgAdmin) folder helped me launching pgAdmin4 server again
I am running pgAdmin4 v4.27 now.
After I upgraded to pgAdmin4 v4.28 the problem started i.e. the server was not starting. I tried many ways including changing the content type of .js to test/javascript from text/plain, it did not work.
Finally deleting all contents from C:\Users\YourUsernameOrAdmin\AppData\Roaming\pgAdmin helped me

blocks|key|4368340|text|删除文件夹C:\Users\User_Name\AppData\Roaming\pgAdmin\sessions的内容对我很有帮助，我可以启动并加载pgAdmin服务器|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4368341|entityMap^0|5|1F|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Deleting contents of folder <code>C:\Users\User_Name\AppData\Roaming\pgAdmin\sessions</code> helped me, I was able to start and load the pgAdmin server

blocks|key|4368366|text|尝尝这个|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4368367|我遇到了同样的问题，并激活了安装文件，它创建了一个数据库，然后再次重新启动|4368368|sudo+/usr/pgadmin4/bin/setup-web.sh|code-block|syntax|javascript|4368369|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

<h2>try this</h2>
I encountered the same problem and activated the setup file,
it created a database, and was restarting again
<pre><code>sudo /usr/pgadmin4/bin/setup-web.sh
</code></pre>

I have installed PostgreSQL 9.6.2 on my Windows 8.1. But the pgadmin4 is not able to contact the local server. I have tried several solutions suggested here in stackoverflow, tried to uninstall and reinstall PostgreSQL 9.6.2 , tried to modify the config.py, config_distro.py, and delete the files in Roaming folder,i tried standalone pgadmin4 installation, but no success.However, in my local machine i am able to access the server using psql.exe and log as as superuser (postgres user). Can you please suggest any possible solutions to starting/running pgadmin4 ? Thank you.

pgadmin4 : postgresql application server could not be contacted.

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在Windows8.1上安装了PostgreSQL 9.6.2。但是pgadmin4无法联系本地服务器。我已经尝试了在stackoverflow中建议的几个解决方案，尝试卸载并重新安装PostgreSQL 9.6.2，尝试修改config.py，config_distro.py，并删除漫游文件夹中的文件，我尝试独立安...

问pgadmin4 :无法联系postgresql应用程序服务器。
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问pgadmin4 :无法联系postgresql应用程序服务器。EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问pgadmin4 :无法联系postgresql应用程序服务器。
EN