Address already in use during setup

[Devano_on_Crack]

Hello there,

so I got this error

Error response from daemon: driver failed programming external connectivity on endpoint app (2cf9494e875c2910beaf80edc21a16c997aba51b23504f26bd58e381b167f45f): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
Error: failed to start containers: app

Does anyone know how to fix this?

[Falco]

Are you trying to install Discourse in a server which is already used for other apps?

Discourse binds to default web ports, so I recommend using a brand new server for Discourse.

[Devano_on_Crack]

What do you mean with brand new server?

[Remah (Just another happy Discourse user)]

You could search for that error which is that the port is already being used.

So you’re not following the official install method discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub

And you probably need this topic:

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 …

[Devano_on_Crack]

I did follow the official instal method

[Devano_on_Crack]

Is there anyway to change the ports? If so, how and to what should I change it?

[Devano_on_Crack]

@Remah

And you probably need this topic:

It sais the page is invalid or private

[Remah (Just another happy Discourse user)]

I grabbed this link from google: running other websites on the same machine as discourse:

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 …

[Devano_on_Crack]

I also get this arror

nginx: [emerg] BIO_new_file(“/var/discourse/shared/standalone/ssl/ssl.crt”) fail ed (SSL: error:02001002:system library:fopen:No such file or directory:fopen(‘/v ar/discourse/shared/standalone/ssl/ssl.crt’,‘r’) error:2006D080:BIO routines:BIO _new_file:no such file)
nginx: configuration file /etc/nginx/nginx.conf test failed

[Devano_on_Crack]

@Devano_on_Crack

I also get this arror

I noticed the whole ssl folder is empty, how can I fix that?

[Devano_on_Crack]

Also something else came with it

nginx: [warn] the “ssl” directive is deprecated, use the “listen … ssl” directive instead in /etc/nginx/sites-enabled/discourse.conf:12

[Falco]

If your server has the ports blocked it will not be able to create certificates too.

Is this a Digital Ocean droplet? I recommend creating a new one running Ubuntu 18.04.

[Devano_on_Crack]

I don’t have Digital Ocean installed

[pfaffman (Jay Pfaffman)]

Where is this server?

The recommendation is to wipe the os with a clean installation and make sure that you have no web servers (apache or nginx) installed.

[danb35 (Dan)]

@Devano_on_Crack

I did follow the official instal method

If you had followed that method, you wouldn’t have gotten that error. Where is your server (or VPS), and which OS (and version) do you have installed? What else have you installed on that server?