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-…

[图片] 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.

[图片] 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 占用了端口 80，导致 Discourse 无法启动

产品支持安装

Vaping_Community 2018 年3 月 9 日 21:48 4

Apache runs on Port 80 so does your Discourse install, they conflict.

话题		回复	浏览量
Port already in use, what to do? Self-hosting	26	19982	2020 年3 月 6 日
Running Discourse alongside LAMP Self-hosting	3	1087	2020 年11 月 26 日
Can't make Discourse accessible through Apache Self-hosting	7	3284	2015 年3 月 26 日
Port busy and app.yml not found Self-hosting	1	796	2020 年11 月 20 日
Discourse won't start because port 80 is in use Product Support	3	2252	2020 年6 月 17 日

Apache 占用了端口 80，导致 Discourse 无法启动

相关话题