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 …

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?

Well to me it seems it’s not, according to these; [imagem] [imagem] Could it be because Apache is already listening to it?

So I managed to make nginx listen to port 80 [imagem] Apache listens to port 8080 and is redirected by nginx to mydomain.com Still, discourse doesn’t appear on forum.mydomain.com Here are some of the config files: App.yml https://gist.github.com/Exuraz/a9fc1f151b67837fc9ca nginx main site htt…

$ curl http://forum.noodlepowered.com curl: (6) Could not resolve host: forum.noodlepowered.com You don’t have DNS set up.

Ah okay thanks, I suppose theres instructions on that somewhere too so wil figure that out. Atleast Nginx runs properly now, thanks for the help :slight_smile:

You’ll want to go to your DNS provider and Cloudflare (which might be the same thing) and set up forum. to point to the same IP address. Make sure to disable content optimizations in CloudFlare - they mess up the Discourse JS.

Alright not sure if we have cloudflare but will see if I can get things to work. Thankou very much for the help :slight_smile:

Port already in use, what to do?

Product Support Self-hosting

codinghorror (Jeff Atwood) Maio 29, 2017, 6:33pm 21

This (port conflict) was handled in the script a while ago. Needing to proxy is a whole other deal there are howto topics on that.

Tópico		Respostas	Visualizações
Address already in use during setup Self-hosting	14	3128	24 de Fevereiro de 2020
Discourse won't start because port 80 is in use Product Support	3	2245	17 de Junho de 2020
Running Discourse alongside LAMP Self-hosting	3	1079	26 de Novembro de 2020
How to install discourse on hosting? Self-hosting	11	5032	30 de Janeiro de 2018
Install on vps problem? Self-hosting	2	1355	19 de Abril de 2018

Port already in use, what to do?

Tópicos relacionados