Discourse won't start because port 80 is in use

Product Support

AI-generated summary

Aiden12114 is experiencing an issue with running Discourse due to port 80 being in use. The error message suggests that the address is already bound to another process. hawm advises checking host port usage, as the recently installed Nginx may be binding to port 80 by default and needs to be stopped.

jughead notes that the Nginx PPA installed by Aiden12114 is not actively maintained and recommends using the official installation instructions for the latest version.

itsbhanusharma suggests that the issue is due to installing Nginx on the server without configuring Discourse to run behind a reverse proxy, and provides a link to a guide on running other websites on the same machine as Discourse.

1

So, I was trying to run ./launcher start app but then I keep getting this error:

root@Roblox-Development:/var/discourse# ./launcher start app

starting up existing container
+ /usr/bin/docker start app
Error response from daemon: driver failed programming external connectivity on endpoint app (73771b238a3c9cdb51c4976f9548e695f4d1a9b0a4605c33eb3d857a8206cffc): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
Error: failed to start containers: app

Anyway to fix it?

Extra Info:

I also ran these 2 commands ONLY.

sudo add-apt-repository ppa:nginx/stable -y
sudo apt-get update && sudo apt-get install nginx
2

listen tcp 0.0.0.0:80: bind: address already in use

check your host ports usage, the nginx may binding 80 by default that you need to stop nginx.

3

I’d just like to note the launchpad ppa **is not ** actively maintained by nginx. If you really want the latest version take a look at the install instructions.

4

You’ve installed nginx on the server and haven’t tweaked discourse to run behind a reverse proxy.

follow this guide for help