- Newest
- Most votes
- Most comments
I just found out the problem. To make PostgreSQL available to an external IP there are two items to configure: postgresql.conf and pg_hba.conf. Some sort of script or whatever is commenting out the line with the Public IP address in the postgresql.conf. When I restart the PostgreSQL service, I can connect from my local PGAdmin4, but if I reboot the instance, "something" is commenting the line with the Public IP address. Now I have to find the guilty "something", I think I can figure it out.
In addition to the two files you already mentioned, have you also taken a look at whether your settings are being overridden by config in postgresql.auto.conf? Settings in postgresql.auto.conf will override those in postgresql.conf (more docs about that config file here: https://www.postgresql.org/docs/13/config-setting.html#CONFIG-SETTING-CONFIGURATION-FILE).
A cursory Google search also turns this up, if this helps: https://dba.stackexchange.com/questions/180177/postgres-seems-to-ignore-listen-addresses-setting
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 12 days ago
- AWS OFFICIALUpdated 8 months ago