Nextcloud Talk - Configuring Turnserver - Janus

[ucfdustin]

Hoping to find a solution for this...

The nextcloud AIO is behind a reverse proxy, but the nextcloud host cannot have ports exposed directly to internet. I have a server that sits in front of the AIO with a wireguard connections between the two. Everything works find, except TALK video calls. Seems the Janus needs to be configured in the janus.jcfg file to use the turnserver which is running on the public server. When troubleshooting the base installation it looks like the HPB is advertising its docker IP not the public ip even though the upstream turnserver is listed in the Talk Admin panel.

I had it working with the solution from #6434
"#!/bin/bash

set -e
set -u

egrep -q 'stun_server = "SOMESTUNSERVER"' /var/lib/docker/overlay2/*/merged/usr/local/etc/janus/janus.jcfg && exit 0

sed 's/^\s*#stun_server./\tstun_server = "SOMESTUNSERVER"/g' -i /var/lib/docker/overlay2//merged/usr/local/etc/janus/janus.jcfg
docker restart nextcloud-aio-talk"

However, it seems like docker has moved away from the ability to edit the files via overlay with the new storage approach.

Is there any means to pass these values to the underlying aio-nextcloud-talk container to configure janus to also use the specified turn and stun server. These are the actual values already configured in the admin interface page in the AIO.

stun_server = ""
stun_port =
turn_rest_api = "https://nextcloud.domain.com/standalone-signaling/turn/credentials"
turn_rest_api_key = "secret"

[szaimen]

Hi, please post this at https://help.nextcloud.com. There more eyes will see this.