Hi, everybody! I’m trying to install discourse on a subdomain. My main domain is running wordpress, which was built using docker-compose. The subdomain and the domain are using the same VPS server. For the installation I followed this guide: https://meta.discourse.org/t/run-other-websites-on-the…

[Bild] Daniel Jurnik: bind() to 0.0.0.0:80 failed Is there a different webserver on that machine that is hogging port 80?

Did you change the ports in the app.yml so that Discourse isn’t trying to use the ports that NGINX wants? [Bild] Daniel Jurnik: Sorry, I’m a beginner with Linux / NGINX / Docker things. Any advice would be appreciated. Thank you. This is an advanced setup that requires understanding of DNS, …

As I mentioned, wordpress is running on the main domain. If I understood correctly, the other NGIX works in the container together with wordpress. I followed this tutorial: How To Install WordPress With Docker Compose | DigitalOcean If I run the netstat -tulnp command, this is what I get: Active…

The instructions suggest commenting them, so I did: ## which TCP/IP ports should this container expose? ## If you want Discourse to share a port with another webserver like Apache or nginx, ## see https://meta.discourse.org/t/17247 for details expose: # - "80:80" # http # - "443:443" # https …

[Bild] Daniel Jurnik: As I mentioned, wordpress is running on the main domain. Before you started this, was it behind a working NGINX reverse proxy that you’re adding Discourse to? Or if Apache/WordPress was running before, that’s what’s got port 80? Oh, it looks like docker-proxy has port …

As I stated, I believe the other NGIX (the one for wordpress) works in a container together with MySQL, and Wordpress. This is what I get by running docker ps command: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS …

That would be why the external nginx cannot boot, as the ports are taken by the internal one. You probably need to shut that container down and transfer it’s config for Wordpress to the outer nginx layer. Also, those are separate containers, the nginx is separate from MySQL and WordPress.

I shut down the webserver (NGIX container) and tried to start the external NGIX. Still not working. [Bild] Firepup Sixfifty: Also, those are separate containers, the nginx is separate from MySQL and WordPress. You’re right. It’s my fault. I thought all the apps mentioned were in one containe…

[Bild] Daniel Jurnik: tried to start the external NGIX. Still not working. What’s docker ps and netstat -tulnp look like now?

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 6ca4cbec2c88 local_discourse/app "/sbin/boot" 3 hours ago Up 2 hours app 42c4211a2fb6 wordpress:5.1.1-fpm-alpine "docker-en…

NGINX kann nicht gestartet werden

Unterstützung Installation

Firepup650 (Firepup Sixfifty) 8. März 2024 um 15:51 2

Gibt es einen anderen Webserver auf dieser Maschine, der Port 80 belegt?

Thema		Antworten	Aufrufe
Discourse working with jwilder /nginx proxy & acme-companion Self-hosting	6	5684	9. Februar 2022
Getting 'welcome to nginx' with no access to internet Self-hosting	12	2864	26. April 2025
Run other websites on the same machine as Discourse Self-Hosting how-to , advanced-setup	66	139863	30. Juni 2026
Installation on v-server as a subfolder with other services in subfolders using apache Self-hosting	39	8469	6. Juli 2016
Nginx / letsencrypt / docker -- Ubuntu 16.04 Self-hosting	5	2855	13. Januar 2018

NGINX kann nicht gestartet werden

Verwandte Themen