Are there any other database connection definition locations other than the DISCOURSE_DB_HOST in /var/discourse/containers/app.yml? I have my PostgreSQL server running separately from my Discourse docker server and recently I changed the database connection hostname from the database server’s public hostname/IP to a private LAN IP. I’m seeing some connections on this private LAN IP now, but I’m still seeing most of the traffic go through the public IP / interface instead. I’ve tried to check the filesystem across the server and within the Docker Discourse image, but I’m not finding the old hostname or the old IP in any of these locations, but something is still accessing the public network interface from this Discourse installation. Any thoughts on how to isolate why Discourse would still be trying to talk to the wrong IP now?

Make sure you follow Running Discourse with a separate PostgreSQL server.

Yes, that is exactly what was followed. Cannot for my life understand why it’s using the public IP though after this change. Especially if that’s the only place to change the IP.

Any other locations where database connection IP / hostname set other than DISCOURSE_DB_HOST in app.yml?

Product Support

pfaffman (Jay Pfaffman) May 27, 2021, 12:26pm 4

Can you block access to the public port? Maybe something else is accessing it. Or you’ve left an old container running?

Topic		Replies	Views
How to Connect to discourse db from public ip inside docker container Self-hosting	1	608	October 26, 2020
Running Discourse with pg_bouncer and a separate DB Self-hosting	2	970	September 20, 2020
Linking containers Self-hosting hosting	5	1628	March 31, 2014
Discourse docker runs successfully, cannot access discourse host name Self-hosting	5	231	October 2, 2025
Can't access site after installation Self-hosting	10	4280	April 14, 2016

Any other locations where database connection IP / hostname set other than DISCOURSE_DB_HOST in app.yml?

Related topics