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 publi…

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.

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

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

Поддержка

Falco (Falco) 24.Май.2021 14:45:52 2

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

Тема		Ответов	Просм.
How to Connect to discourse db from public ip inside docker container Self-hosting	1	554	26.10.2020
Running Discourse with pg_bouncer and a separate DB Self-hosting	2	882	20.09.2020
Linking containers Self-hosting hosting	5	1503	31.03.2014
Discourse docker runs successfully, cannot access discourse host name Self-hosting	5	81	02.10.2025
Can't access site after installation Self-hosting	10	4130	14.04.2016

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

Связанные темы