No votes yet
Hi,
I'm running a PostgreSQL service on EasyPanel with port 5400 exposed externally (mapped to internal port 5432). I have opened port 5400 on the firewall and configured the service to expose it, but external connections are still being rejected.
Error received when trying to connect:
FATAL: no pg_hba.conf entry for host "X.X.X.X", user "postgres", database "crm", no encryption What I've already tried:
Opened port 5400 on the firewall ✅ Exposed port 5400 in the EasyPanel service configuration ✅ Ran ALTER SYSTEM SET ssl = off; followed by SELECT pg_reload_conf(); inside psql — but the setting requires a full server restart to take effect, and after restarting via EasyPanel, the postgresql.auto.conf change appears to be lost (likely because the container is recreated from a fresh image on restart) Modified pg_hba.conf to replace hostssl rules with host — but this also does not persist across container restarts Root cause: The pg_hba.conf and postgresql.conf files inside the container do not persist changes across restarts. The container appears to reinitialize configuration on every restart.
Is there an environment variable or a custom config mount I can use to make these settings persist?
Feel free to open it up again, if you would have any further questions. Thanks!
Yeah you are correct as with EasyPanel’s managed PostgreSQL service, configuration changes inside the container (like editing pg_hba.conf or using ALTER SYSTEM) do not persist because custom config mounts aren’t supported for managed services. If you need persistent control over pg_hba.conf or postgresql.conf, we recommend running PostgreSQL as an App service instead. That will allow you to use postgres with custom configuration files so changes survive restarts. Let us know if you’d like help setting that up.