I’m still not sure what happened, but basically after updating today, I found my server went down. staff_user action subject created_at details context mofosyne custom_staff 2018-03-08 23:12:34 UTC “from_version: b040e11 \n repository: /var/www/discourse” mofosyne custom_staff 2018-03-…

[image] mofosyne: , but it would be good to hear if anyone else had the same issue today. Not likely. You should remove or disable Apache. Something like apt purge apache2

From the error messages you posted, it looks like something on your server (Apache) ganked port 80, nothing weird here.

[image] mofosyne: Solution is to shutdown apache2 then run ./launcher start app. This is weird as this server is only hosting this single website. Not sure why apache2 is getting in the way. Apache runs on Port 80 so does your Discourse install, they conflict.

That sounds about right. I must have accidentally installed Apache while I was trying to work out how to follow the install instructions. Ah well, at least this post would give people some idea how to deal with similar issues in the future.

Apache took port 80 and caused Discourse not to start

Product Support Self-hosting

pfaffman (Jay Pfaffman) March 9, 2018, 8:57pm 3

Not likely.

You should remove or disable Apache. Something like

apt purge apache2

Topic		Replies	Views
Port already in use, what to do? Self-hosting	26	19975	March 6, 2020
Running Discourse alongside LAMP Self-hosting	3	1084	November 26, 2020
Can't make Discourse accessible through Apache Self-hosting	7	3281	March 26, 2015
Port busy and app.yml not found Self-hosting	1	795	November 20, 2020
Discourse won't start because port 80 is in use Product Support	3	2250	June 17, 2020

Apache took port 80 and caused Discourse not to start

Related topics