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? [image] 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 numerous times with ./launcher rebuild web_only Questions. What is supposed to be running on 127.0.0.1:3000? How to restart that service? Cheers and thanks!

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

[image] 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. I’d like to know how to manually start the unicorn server.

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

Why would discourse want to connect to port 3000

Product Support

Stephen (Stephen) September 22, 2020, 12:51am 2

Is this related to your previous topic?

Topic		Replies	Views
Discourse failing to connect to port 3000 Product Support	8	1436	September 23, 2020
Port 3000 - Not reachable Product Support	0	469	April 30, 2022
Change unicorn port from 3000 in development Development	11	6989	February 26, 2021
Install Discourse for Development using Docker is Failed Development	5	1093	July 23, 2019
Can not visit forum.abc.com again after port change to container/app/yml Self-hosting	3	1219	May 14, 2020

Why would discourse want to connect to port 3000

Related topics