Hi guys, I resized my DigitalOcean droplet today, and after that process was completed I haven’t been able to access my Discourse forum (I’m getting ERR_CONNECTION_REFUSED). It looks like something other than Discourse is using port 80… This is what I get when trying to restart the app (I have also…

You probably have Nginx or Apache installed on the server. You should remove them and cd /var/discourse ./discourse-setup to reconfigure Discourse for the amount of RAM you have.

Yup, looks like apache was listening. root@community:~# netstat -plnt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1318/sshd…

[image] tkrunning: I’m not sure if this was necessary, but finally I ran sudo systemctl disable apache2 to make sure apache does not run when my droplet is restarted in the future. Yes, that was a very good idea.

Right. Perhaps a better idea would be apt purge apache2 but that’s assuming that your apache server package is named just that. You can see what all apache stuff is installed like sudo dpkg -l |grep apach You really need to un-install the main server part. The other stuff won’t hurt you and can …

Connection error after resizing DO Droplet

Product Support Self-hosting

schleifer (Andrew Schleifer) January 22, 2018, 12:15am 2

Run netstat -plnt to find what is listening on port 80.

Topic		Replies	Views
Apache took port 80 and caused Discourse not to start Self-hosting	4	1329	March 11, 2018
Port already in use, what to do? Self-hosting	26	19976	March 6, 2020
Discourse doesn't deliver webpages, fresh install on Linode Ubuntu 14.04 Self-hosting docker	5	3998	July 7, 2015
Error response on port 443 Product Support	3	1633	June 11, 2017
Start failed, address already in use Self-hosting	5	1308	March 8, 2016

Connection error after resizing DO Droplet

Related topics