Hoping to find a solution for this as it has been on ongoing issue.
The nextcloud AIO is behind a reverse proxy, but the nextcloud server cannot have ports exposed directly to internet. I have a server that sits in front of the AIO with nginx as the reverse proxy 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 facing ip even though the upstream turnserver is listed and coinfigured in the Talk Admin panel.
I had it working with the solution from #6434…this was just hacking the AIO talk-container janus.jcfg file to use the specified turnserver
"#!/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 that docker has moved away from the ability to edit the files via overlay with their new storage approach. AND the containers are all read only from nextcloud-aio.
Is there any means to pass these values to the underlying aio-nextcloud-talk container to configure janus.jcfg to also use the specified turn and stun server from the Talk admin. These are just 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”