The discussion revolves around Discourse attempting to connect to port 3000. csmu initially inquires about the necessity of this connection and how to enable or stop it, as their production server is failing to connect to port 127.0.0.1 3000.
Falco reveals that the Unicorn server runs on port 3000. csmu then asks how to manually restart the Unicorn server, and Falco responds that the command sv start unicorn should be executed while inside the container.
csmu also mentions that this issue is somewhat related to a previous topic, but distinct due to a rollback to version 2.4 in an attempt to resolve the issue.
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
Is this related to your previous topic?
The Unicorn server runs on port 3000.
How do you manually restart the unicorn server?
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.
I’d like to know how to manually start the unicorn server.
While inside the container sv start unicorn.