The discussion revolves around burningman’s Discourse forum going offline after removing HTTPS. burningman checked the server and everything seems fine, but the forum is still offline.
itsbhanusharma and cpradio suggested checking what’s occupying port 80 on the server. burningman found that apache2 is taking over port 80. cpradio advised removing apache2, but burningman reported that the issue persists.
cpradio suggested rebooting the server, but burningman reported that the issue remains. notriddle noticed that the forum is actually online, but burningman disagreed.
notriddle discovered that the issue is related to HTTPS, and burningman confirmed that using HTTP instead of HTTPS resolves the issue. burningman realized that removing LETSENCRYPT was the cause of the problem and is reinstalling it.
frold suggested running the setup wizard again, but burningman had already tried that. notriddle explained that comments in YML files start with the # sign and need to be uncommented to enable the web.ssl template.
Finally, cpradio confirmed that everything is operational again, and burningman thanked cpradio for the help.
One of my forum goes offline. I checked on sever but everything is working fine on server side.
Another forum is working fine but one goes offline.
Is anyone here facing this issue.
It will be great if anyone here will share how and when forum comes back online.
Thanks
Hey Discourse Team,
Kindly help me in this matter.
This is my forum link - https://forum.buzzbasement.com
I rebuild app two time still nothing happened.
What should I do for this.
What is occupying the port 80 on your server?
means, sorry I haven’t understand what you really want to ask
Run this command, to identify what is taking up port 80 (and then provide us the output)
sudo lsof -t -i tcp:80 -s tcp:listen
Sorry, I copied and pasted it with an extra parameter, can you run it once more, using this (note: the missing -t argument)
sudo lsof -i tcp:80 -s tcp:listen
Perfect, so you have apache2 installed which is taking over port 80. Are you running other sites on this server (other than Discourse)?
Nope, only this one.
I am using Digital Ocean.
I have one more Discourse but that is on another server and that is working fine.
Only this one is affecting
okay, try running sudo apt-get remove apache2
If that doesn’t solve the issue, run dpkg -l | grep apache2 and remove each remaining component
I tried both but problem still exists
Run the sudo lsof -i tcp:80 -s tcp:listen command again, is anything listening on port 80 anymore? From what I can tell, that is simply implying that apache2-bin apache2-data apache2-utils can be manually removed as well.
sudo apt-get remove apache2-bin apache2-data apache2-utils
The rc in front of apache2 means it was removed, but still has configuration files sitting on the system.
now,. nothing happens this time..
It is not listening on port 80 anymore
If discourse was already installed, a reboot should be sufficient for starting it back up, or you can run
cd /var/discourse
./launcher rebuild app
Thanks, I will do that.
Hey @cpradio, I just rebuild but still same problem 
Anything taking up port 80 again? Are you sure it is the same error?