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

You’ve installed nginx on the server and haven’t tweaked discourse to run behind a reverse proxy. follow this guide for help [image] Run other websites on the same machine as Discourse Self-Hosting 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 need to copy and edit samples/standalone.yml with your favorite tex…

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.

[image] 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.

Discourse won't start because port 80 is in use

Product Support

jughead June 17, 2020, 7:48am 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.

Topic		Replies	Views
Error in installing Self-hosting	2	1927	May 4, 2015
Port already in use, what to do? Self-hosting	26	20042	March 6, 2020
Address already in use during setup Self-hosting	14	3195	February 24, 2020
Apache took port 80 and caused Discourse not to start Self-hosting	4	1338	March 11, 2018
Running Discourse alongside LAMP Self-hosting	3	1106	November 26, 2020

Discourse won't start because port 80 is in use

Related topics