Hi, just tried to setup Discourse and all went good except for launching it. It gives the following error: starting up existing container + /usr/bin/docker start app Error response from daemon: Cannot start container app: Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already …

[image] Run other websites on the same machine as Discourse Self-Hosting @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 i…

Thanks for the quick reply, I am not sure though if I am capable of doing all of that, I am really a beginner with Linux and the stuff there seems quite tricky, especially since it has to be configured with other webservices as well (Or so it seems according to the last part of the guide, suggestin…

I managed to get it running (the container, that is) but I don’t really understand yet what port it runs on and how I can access it. forum.mydomain.com gives me nothing, probably because I haven’t set up DNS yet? and wouldn’t know where else it should be on. :4001 doesn’t work either but tinkering w…

This error comes up often enough that I think our startup scripts should offer guidance for it. I am getting really sick of reading the “oh no, port 80 is in use” install topics.

Sorry, just not good with Linux to figure all of this out by myself.

Not a problem, just pointing out that this comes up a LOT. And our scripts should offer advice when it does, automatically.

I understand. That’d be very useful. I think I set things up correctly now with @riking ’s way - if that’s the advice you mean - it’s just that it refuses the connection when I try to connect to mydomain:4001 (All ports in that topic mentioned that so I am figuring that is the point it redirects it …

The first post isn’t using port 4001 anymore, but rather a UNIX socket connection to get into the container. It’s supposed to get you to set up a nginx on the host that proxies to either Discourse or your other sites.

I followed everything in your guide except for the firewall part since I thought that was only for security and can be done later when stuff actually works, and because even in the replies there were a couple of issues with it. I set up nginx correctly with atleast Discourse, but I still can’t acce…

Is nginx actually running? on port 80?

Port already in use, what to do?

Support Self-hosting

riking (Kane York) April 25, 2015, 6:02pm 2

Topic		Replies	Views
Address already in use during setup Self-hosting	14	2957	February 24, 2020
Discourse won't start because port 80 is in use Support	3	2170	June 17, 2020
Running Discourse alongside LAMP Self-hosting	3	998	November 26, 2020
How to install discourse on hosting? Self-hosting	11	4873	January 30, 2018
Install on vps problem? Self-hosting	2	1296	April 19, 2018

Port already in use, what to do?

Related topics