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…

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.

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

Alguma outra localização onde o IP / hostname da conexão do banco de dados é definido além de DISCOURSE_DB_HOST em app.yml?

Suporte

Falco (Falco) 24 Maio , 2021 14:45 2

Certifique-se de seguir Executando o Discourse com um servidor PostgreSQL separado.

Tópico		Respostas	Vistas
How to Connect to discourse db from public ip inside docker container Self-hosting	1	579	26 Outubro , 2020
Running Discourse with pg_bouncer and a separate DB Self-hosting	2	921	20 Setembro , 2020
Linking containers Self-hosting hosting	5	1546	31 Março , 2014
Discourse docker runs successfully, cannot access discourse host name Self-hosting	5	144	2 Outubro , 2025
Can't access site after installation Self-hosting	10	4200	14 Abril , 2016

Alguma outra localização onde o IP / hostname da conexão do banco de dados é definido além de DISCOURSE_DB_HOST em app.yml?

Related topics