Discourse failing to connect to port 3000

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

I have rebuilt web_only numerous times with ./launcher rebuild web_only


  1. What is supposed to be running on
  2. How to restart that service?

Cheers and thanks!

as far as i know, that is the ruby install running on 3000

maybe do a full reboot

reboot or sudo reboot

1 Like

P.s please tell me you did a backup before you upgraded.

Yes. Auto backup. The data container is up and running.

It’s on a production server. Other services are running on that server.

You need to rebuild your data container and then rebuild web_only. There are some hints in PostgreSQL 12 update.


I’ve run ./launcher rebuild data more than 5 times with no error messages.

I’m grateful this is happening our server and not on a clients :slight_smile:

seems like the upgrade to postgres 12 failed somehow.

Pups::ExecError: /root/upgrade_postgres failed with return #<Process::Status: pid 47 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params "/root/upgrade_postgres"
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
1 Like

In this case the tables for the discourse database were all dropped somehow.
I decided to roll back to 2.4 and restore the discourse database.

1 Like