Santiago Bernhardt

do not forget that ws is by default tcp only and turn needs both ws tcp and standard udp not ws over udp port (while there are hacks around this...

your router has to do 3478 》signaling host:port not 3478 》reverse proxy 》signaling I can assure it works I have 3478 》signal1:3478 3479 》signal2:3478 3480》signal3:3478 3481 4 signal servers on...

it is literally here https://github.com/nextcloud-snap/nextcloud-snap/wiki/How-to-configure-talk-HPB-with-Docker#prepare-routerfirewall--reverse-proxy I still think you might be missing something.

can you remove the extra environment variables that you have on you compose and stick only to the variables that we have in the documentation and try again.

``` environment: - NC_DOMAIN=example.com - TALK_HOST=signaling.example.com - TALK_MODE=external - PUBLIC_WSS_URL=wss://signaling.example.com/spreed - NEXTCLOUD_VERIFY_TLS=false - INTERNAL_SECRET=$SUPERSECRETPASSWORD - SIGNALING_SECRET=$SUPERSECRETPASSWORD - TURN_SECRET=$SUPERSECRETPASSWORD - TZ=America/Chicago - RATE_LIMIT_DISABLE=true - TALK_PORT=3478 - SKIP_INTERNAL_CHECK=true - TRUSTED_PROXIES=127.0.0.1 ::1 ```...

Ill say that since I update aio-talk to the latest version is broken on my side as well. It works fine up to spreed 2.0.2 after that I have not...

https://github.com/strukturag/nextcloud-spreed-signaling/releases https://github.com/nextcloud/all-in-one/blob/main/Containers/talk/Dockerfile#L4

the easier approach on this is using lxc containers cc @scubamuc

3 things 1: ports allocation (we can change 9001 port and 443) 2: multi deployments (thats snapd) 3: multi deployments support cia lxd as solution I might have not understood...

fair point