在我得到一些小知识之前，我知道有很多类似的文章，但是我已经阅读并使用它们来说明这一点，但是我认为它们并不能回答我的问题。
我正在尝试将测试人员的heroku网站[编辑：已删除]连接到我的PostgreSQL数据库。我以前尝试过MS Server，但我在Windows上使用，而Heroku不喜欢pyodbc。
我敢肯定我的PostgreSQL设置正确，但是试图确定我是否具有PostgreSQL URL的正确主机名，以及是否需要做更多事情来允许通过Windows防火墙的访问。
PostgreSQL
在接受How to Allow Remote Access to PostgreSQL database之后，我的postgresql.conf具有listen_addresses = '*'和端口5432。我又增加了一行
host all all 0.0.0.0/0 md5
在pg_hba.conf上获得以下内容
# TYPE DATABASE USER ADDRESS METHOD
# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
host replication all 127.0.0.1/32 md5
host replication all ::1/128 md5
host all all 0.0.0.0/0 md5
现在我可以在命令行上完成
C:\etc> psql -U postgres -h 192.XXX.XX.XXX -d ProductionData
192.XXX.XX.XXX是我的IPv4地址（可从“开始”>“更改以太网设置”> MyCompany.local找到），一切正常。我知道，因为如果我撤消pg_hba.conf上的行，我会得到
(venv) C:\etc> psql -U postgres -h 192.XXX.XX.XXX -d ProductionData
psql: FATAL: no pg_hba.conf entry for host "192.XXX.XX.XXX", user "postgres", database "ProductionData", SSL off
Heroku
我了解postgres需要以下形式的URL
postgresql://username:password@hostname/database
或
postgresql://username:password@hostname:port/database
除了IP地址是IP地址之外，我实际上并不了解其他主机名。我尝试了localhost，并使用了与以上192.XXX.XX.XXX和192.XXX.XX.XXX:5432相同的IPv4地址。
下面的“日志”部分具有netstat，heroku配置设置，针对在git bash中进行的每种尝试重新启动postgresql的操作，但是我得到了以下两个192.XXX.XX.XXX作为超时的信息。
Is the server running on host "localhost" (127.0.0.1) and accepting
TCP/IP connections on port 5432?
Is the server running on host "192.XXX.XX.XXX" and accepting
TCP/IP connections on port 5432?
Windows防火墙
我已经创建了允许访问的入站规则...
协议类型-TCP
本地端口-5432
远程端口-所有端口
程序-该程序-％ProgramFiles％\ PostgreSQL \ 11 \ bin \ postgres.exe
尝试＃1-本地主机，结果错误
$ pg_ctl -D "C:\Program Files\PostgreSQL\11\data" restart
waiting for server to shut down.... done
server stopped
waiting for server to start....2019-02-19 10:09:04.423 GMT [11952] LOG: listening on IPv6 address "::", port 5432
2019-02-19 10:09:04.423 GMT [11952] LOG: listening on IPv4 address "0.0.0.0", port 5432
2019-02-19 10:09:04.460 GMT [11952] LOG: redirecting log output to logging collector process
2019-02-19 10:09:04.460 GMT [11952] HINT: Future log output will appear in directory "log".
done
server started
$ netstat -ant | findstr 5432
TCP 0.0.0.0:5432 0.0.0.0:0 LISTENING InHost
TCP [::]:5432 [::]:0 LISTENING InHost
$ heroku restart -a pgtester
Restarting dynos on ? pgtester... done
$ heroku logs -t -a pgtester
...lots of stack errors...
2019-02-19T09:52:25.731597+00:00 app[web.1]: File "/app/.heroku/python/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 437, in connect
2019-02-19T09:52:25.731599+00:00 app[web.1]: return self.dbapi.connect(*cargs, **cparams)
2019-02-19T09:52:25.731600+00:00 app[web.1]: File "/app/.heroku/python/lib/python3.6/site-packages/psycopg2/__init__.py", line 130, in connect
2019-02-19T09:52:25.731602+00:00 app[web.1]: conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
2019-02-19T09:52:25.731604+00:00 app[web.1]: sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not connect to server: Connection refused
2019-02-19T09:52:25.731606+00:00 app[web.1]: Is the server running on host "localhost" (127.0.0.1) and accepting
2019-02-19T09:52:25.731607+00:00 app[web.1]: TCP/IP connections on port 5432?
2019-02-19T09:52:25.731646+00:00 app[web.1]: (Background on this error at: http://sqlalche.me/e/e3q8)
尝试＃2-192.XXX.XX.XXX，结果超时
$ heroku config:set DEV_DATABASE_URL=postgresql://postgres:mysecretpassword@192.XXX.XX.XXX/ProductionData
Setting DEV_DATABASE_URL and restarting ? pgtester... done, v47
DEV_DATABASE_URL: postgresql://postgres:mysecretpassword@192.XXX.XX.XXX/ProductionData
$ heroku restart -a pgtester
Restarting dynos on ? pgtester... done
$ netstat -ant | findstr 5432
TCP 0.0.0.0:5432 0.0.0.0:0 LISTENING InHost
TCP [::]:5432 [::]:0 LISTENING InHost
$ heroku logs -t -a pgtester
...lots of stack errors...
2019-02-19T10:00:57.273592+00:00 app[api]: Set DEV_DATABASE_URL config vars by user email@example.com
2019-02-19T10:00:57.273592+00:00 app[api]: Release v47 created by user email@example.com
2019-02-19T10:01:05.401378+00:00 heroku[web.1]: Starting process with command `waitress-serve --port=44666 flasky:app`
2019-02-19T10:01:05.672789+00:00 heroku[web.1]: Restarting
2019-02-19T10:01:08.193167+00:00 app[web.1]: [heroku-exec] Starting
2019-02-19T10:01:10.388293+00:00 app[web.1]: postgresql://postgres:mysecretpassword@192.XXX.XX.XXX/ProductionData
2019-02-19T10:01:10.897113+00:00 app[web.1]: Serving on http://0.0.0.0:44666
2019-02-19T10:01:12.089984+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2019-02-19T10:01:12.196052+00:00 heroku[web.1]: Process exited with status 143
2019-02-19T10:01:12.358184+00:00 heroku[web.1]: Starting process with command `waitress-serve --port=18540 flasky:app`
2019-02-19T10:01:16.133191+00:00 app[web.1]: [heroku-exec] Starting
2019-02-19T10:01:18.520615+00:00 app[web.1]: postgresql://postgres:mysecretpassword@192.XXX.XX.XXX/ProductionData
2019-02-19T10:01:19.161158+00:00 app[web.1]: Serving on http://0.0.0.0:18540
2019-02-19T10:01:19.687131+00:00 heroku[web.1]: State changed from starting to up
2019-02-19T10:01:33.125392+00:00 heroku[router]: at=info method=GET path="/" host=pgtester.herokuapp.com request_id=7e65dc99-b99f-4b81-8bbe-a4b98adebd91 fwd="185.16.227.58" dyno=web.1 connect=1ms service=231ms status=200 bytes=2077 protocol=https
2019-02-19T10:02:11.389923+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=POST path="/" host=pgtester.herokuapp.com request_id=6837dbb0-b2e4-44ee-a67c-2f79a1c7c1b6 fwd="185.16.227.58" dyno=web.1 connect=1ms service=30000ms status=503 bytes=0 protocol=https
尝试＃3-192.XXX.XX.XXX:5432，结果超时
$ pg_ctl -D "C:\Program Files\PostgreSQL\11\data" restart
waiting for server to shut down.... done
server stopped
waiting for server to start....2019-02-19 10:09:04.423 GMT [11952] LOG: listening on IPv6 address "::", port 5432
2019-02-19 10:09:04.423 GMT [11952] LOG: listening on IPv4 address "0.0.0.0", port 5432
2019-02-19 10:09:04.460 GMT [11952] LOG: redirecting log output to logging collector process
2019-02-19 10:09:04.460 GMT [11952] HINT: Future log output will appear in directory "log".
done
server started
$ netstat -ant | findstr 5432
TCP 0.0.0.0:5432 0.0.0.0:0 LISTENING InHost
TCP [::]:5432 [::]:0 LISTENING InHost
$ heroku config:set DEV_DATABASE_URL=postgresql://postgres:mysecretpassword@192.XXX.XX.XXX:5432/ProductionData
Setting DEV_DATABASE_URL and restarting ? pgtester... done, v48
DEV_DATABASE_URL: postgresql://postgres:mysecretpassword@192.XXX.XX.XXX:5432/ProductionData
$ netstat -ant | findstr 5432
TCP 0.0.0.0:5432 0.0.0.0:0 LISTENING InHost
TCP [::]:5432 [::]:0 LISTENING InHost
$ heroku restart -a pgtester
Restarting dynos on ? pgtester... done
$ heroku logs -t -a pgtester
...lots of stack errors...
2019-02-19T10:11:10.352241+00:00 app[api]: Release v48 created by user email@example.com
2019-02-19T10:11:10.352241+00:00 app[api]: Set DEV_DATABASE_URL config vars by user email@example.com
2019-02-19T10:11:17.316331+00:00 heroku[web.1]: Starting process with command `waitress-serve --port=56616 flasky:app`
2019-02-19T10:11:20.998316+00:00 app[web.1]: [heroku-exec] Starting
2019-02-19T10:11:21.724624+00:00 heroku[web.1]: Restarting
2019-02-19T10:11:25.043993+00:00 app[web.1]: postgresql://postgres:mysecretpassword@192.XXX.XX.XXX:5432/ProductionData
2019-02-19T10:11:25.797589+00:00 app[web.1]: Serving on http://0.0.0.0:56616
2019-02-19T10:11:26.872124+00:00 heroku[web.1]: Starting process with command `waitress-serve --port=51247 flasky:app`
2019-02-19T10:11:27.101119+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2019-02-19T10:11:27.211928+00:00 heroku[web.1]: Process exited with status 143
2019-02-19T10:11:29.033774+00:00 app[web.1]: [heroku-exec] Starting
2019-02-19T10:11:30.261042+00:00 app[web.1]: postgresql://postgres:mysecretpassword@192.XXX.XX.XXX:5432/ProductionData
2019-02-19T10:11:30.570976+00:00 app[web.1]: Serving on http://0.0.0.0:51247
2019-02-19T10:11:31.054334+00:00 heroku[web.1]: State changed from starting to up
2019-02-19T10:11:34.448659+00:00 heroku[router]: at=info method=GET path="/" host=pgtester.herokuapp.com request_id=7498e3a1-5a09-419b-8038-fc4bf3ddd642 fwd="185.16.227.58" dyno=web.1 connect=1ms service=170ms status=200 bytes=2077 protocol=https
...lots of stack errors...
2019-02-19T10:16:14.079101+00:00 app[web.1]: sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not connect to server: Connection timed out
2019-02-19T10:16:14.079102+00:00 app[web.1]: Is the server running on host "192.168.10.162" and accepting
2019-02-19T10:16:14.079104+00:00 app[web.1]: TCP/IP connections on port 5432?
2019-02-19T10:16:14.079144+00:00 app[web.1]: (Background on this error at: http://sqlalche.me/e/e3q8)
答案 0 :(得分：1)
网络是一个很大的话题，但总的来说
192开头，我敢打赌下一个八位字节是168，这意味着它是private network，因此无法从Internet访问（例如，有很多机器的地址为192.168.1.10，这可以存在于任何专用网络上）192.168.1.10的内容，则必须做一些额外的工作²以下是一些选择：
192.168.x.y地址连接到数据库我不会建议将Web应用程序保留在网络外部，将数据库保留在网络内部，并将数据库暴露给Internet。这样做的价值很小，尤其是自Heroku's IP addresses change regularly以来，因此您无法轻松地将访问锁定到您的应用程序。最好的情况是，您将拥有一个只能通过SSL（必须由Heroku和其他提供商提供的）访问的可公开访问的数据库，而您必须自己对此进行管理。
传出连接相对容易，例如如果您想将本地网络上运行的Web服务连接到云中的数据库，但我认为这对您没有帮助。
¹这是一件好事，因为它提供了一层保护，防止您的个人设备受到直接攻击。每次等待几天在Windows上安装更新时，如果您的计算机遭到黑客入侵，那会不会很糟糕？
²一个示例是在网络的公共IP地址（例如123.123.123.123上设置端口转发，以便将对123.123.123.123:1234的请求路由到内部网络上的特定IP地址和端口，以用于例如192.168.1.10:5432。