and how do I stop it or if it’s necessary how do I enable it? I’ve got our staging server back up and running with the latest production data. I’ve moved the images and the data from staging into production. Staging works yet production is failing trying to connect to port 127.0.0.1 3000

The Unicorn server runs on port 3000.

Is this related to your previous topic? [imagen] Discourse failing to connect to port 3000 support After upgrading from 2.4.2 to 2.6.x discourse is no longer working for us. The issue is discourse is trying to connect to port 3000 on 127.0.0.1. I have rebuilt web_only n…

[imagen] Falco: The Unicorn server How do you manually restart the unicorn server?

[imagen] Stephen: Is this related In some ways - yes. This topic is different for me since I had rolled back to 2.4 - expecting discourse to work as before. I got discourse to work again by rolling back to 2.4 then updating the data container twice then updating the web_only container twice…

[imagen] csmu: I’d like to know how to manually start the unicorn server. While inside the container sv start unicorn.

¿Por qué querría discourse conectarse al puerto 3000?

Soporte

Stephen (Stephen) 22 Septiembre, 2020 00:51 2

¿Esto está relacionado con tu tema anterior?

Tema		Respuestas	Vistas
Discourse failing to connect to port 3000 Support	8	1282	23 Septiembre 2020
Port 3000 - Not reachable Support	0	430	30 Abril 2022
Change unicorn port from 3000 in development Development	11	6773	26 Febrero 2021
Install Discourse for Development using Docker is Failed Development	5	1019	23 Julio 2019
Can not visit forum.abc.com again after port change to container/app/yml Self-hosting	3	1136	14 Mayo 2020

¿Por qué querría discourse conectarse al puerto 3000?

Temas relacionados