Discourse won't start because port 80 is in use

[Aiden12114 (Aiden)]

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

[hawm]

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.

[jughead]

@Aiden12114

I also ran these 2 commands ONLY.

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

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.

[itsbhanusharma (Bhanu Sharma)]

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

follow this guide for help

Run other websites on the same machine as Discourse

@pfaffman edited this heavily 2022.02.24. Blame me if it’s broken. If you want to run other websites on the same machine as Discourse, you need to set up an extra NGINX or HAProxy proxy in front of the Docker container. NOTE: This is for advanced admins This guide assumes you already have Discourse working - if you don’t, it may be hard to tell whether or not the configuration is working. You cannot use ./discourse-setup to set up Discourse if another server is using port 80 or 443. You will …