NextCloud AiO Multiple Istances + NGINX Proxy Manager = problems with Talk app

[DrPleb]

Hi, I'm trying to deploy multiple istances of NextCloud AiO and as the GitHub post says "The normal way is creating multiple VMs, installing AIO in reverse proxy mode in each of them and having one reverse proxy in front of them that points to each VM (you also need to use a different TALK_PORT for each of them). So, i'm using VMware to deploy multiple VM of NextCloud AiO, nc01.domain.com, nc02.domain.com, ecc...in reverse proxy mode and another VM for NGINX Proxy Manager. Everything works except Talk app, it keeps restarting the call when you are doing it, and in the settings it says there is a problem with STUN/TURN serverI have two theories:- in NGINX Proxy Manager, I used Streams on 1002 port (I change the default TALK_PORT to this one), so i'm forwarding requests that arrives on the proxy manager, that is hosting my domain nc01.domain.com, to the ip address of my nc01 istance, TCP and UDP...and maybe for some reason isn't working (?)- I'm not understanding what is the meaning of "multiple VM with one reverse proxy in front of them"...maybe I have to install NGINX Proxy Manager on the same machine that is hosting NextCloud? But if I do this, what is the purpose of the reverse proxy? Having it or not having it is the same thing, it is all in the same vm and also I have to reserve a public IP address for each nextcloud aio istance...

Here is my NGINX Proxy Manager docker-compose.yml:

version: '3.8'

services:

app:

image: 'jc21/nginx-proxy-manager:latest'

restart: unless-stopped

ports:

# These ports are in format <host-port>:<container-port>

- '80:80' # Public HTTP Port

- '443:443' # Public HTTPS Port

- '81:81' # Admin Web Port

- '1002:1002/tcp' #NextCloud talk port

- '1002:1002/udp' #NextCloud talk port

environment:

# Mysql/Maria connection parameters:

DB_MYSQL_HOST: "db"

DB_MYSQL_PORT: 3306

DB_MYSQL_USER: "npm"

DB_MYSQL_PASSWORD: "npm"

DB_MYSQL_NAME: "npm"

# Uncomment this if IPv6 is not enabled on your host

DISABLE_IPV6: 'true'

volumes:

- ./data:/data

- ./letsencrypt:/etc/letsencrypt

depends_on:

- db



db:

image: 'jc21/mariadb-aria:latest'

restart: unless-stopped

environment:

MYSQL_ROOT_PASSWORD: 'npm'

MYSQL_DATABASE: 'npm'

MYSQL_USER: 'npm'

MYSQL_PASSWORD: 'npm'

volumes:

- ./mysql:/var/lib/mysql

Here is my docker-run command:

sudo docker run \

--sig-proxy=false \

--name nextcloud-aio-mastercontainer \

--restart always \

--publish 8080:8080 \

--env APACHE_PORT=1001 \

--env TALK_PORT=1002 \

--env APACHE_IP_BINDING=[0.0.0.0](https://0.0.0.0/) \

--env NEXTCLOUD_DATADIR="/nc_data" \

--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \

--volume /var/run/docker.sock:/var/run/docker.sock:ro \

nextcloud/all-in-one:latest

Can you help me understand this? Thank you guys <3

[szaimen]

Hi, in general things look correct but the Talk port is not allowed to be proxied. It must be directly forwarded to each VM that is why you need to choose a different talk port for each VM and open that in your router udp and tcp. You can check this also in the talk admin settings for each instance.

Edit: apparently a port over 1024 was required.

[szaimen]

So 1002 is correctly opened.

Is port 1002 also added here?

[DrPleb]

If I re-run the docker command with port 3478 and change it on the firewall it works...if I choose any other port it doesn't work...

[szaimen]

Can you try out a higher port thatn 1024 for a test? Like e.g. 3479

[DrPleb]

No way...it works! Is there any technical reason for this?
Thank you so much!

[szaimen]

I don't know honestly. Possibly some infrastructure in between is blocking ports below 1024...