search

jitsi / docker-jitsi-meet

Jitsi Meet on Docker
https://hub.docker.com/u/jitsi/
Apache License 2.0
3.09k stars 1.37k forks source link

Undocumented installation steps for using STUN/TURN with shared secrets #330

Open almereyda opened 4 years ago

almereyda commented 4 years ago

When using this Docker setup with a STUN/TURN server that has a shared secret defined, connections in Firefox will break unadvertedly.

Following https://meetrix.io/blog/webrtc/jitsi/setting-up-a-turn-server-for-jitsi-meet.html led me to do this

wget https://raw.githubusercontent.com/otalk/mod_turncredentials/master/mod_turncredentials.lua -O .jitsi-meet-cfg/mod_turncredentials.lua

to add the shared secret and the correct host in

vim mod_turncredentials.lua

to add "turncredentials"; to modules_enabled in

vim .jitsi-meet-cfg/prosody/conf.d/jitsi-meet.cfg.lua

and to bind-mount this file into the prosody container with a volumes: declaration in docker-compose.yml like

            - ${CONFIG}/mod_turncredentials.lua:/usr/lib/prosody/modules/mod_turncredentials.lua

It would be nice if it would be possible to merely indicate the shared secret via an environment variable (PROSODY_STUN_SECRET?) and have this file and configuration deployed auto-magically into the jitsi/prosody container.

Or does it appear to be a better approach to keep this file manually downloaded, mounted and activated through the XMPP_MODULES=turncredentials key in .env, instead of manually editing jitsi-meet.cfg.lua?

saghul commented 4 years ago

Our TURN support is not fully ccomplete yet. This will be adddressed once https://github.com/jitsi/docker-jitsi-meet/pull/163

pavestru commented 4 years ago

Thank you! Is it going to be able to use an existing external coturn instance?

almereyda commented 4 years ago

That's what we are doing with injecting the secret key into Prosody.

On Mon, 6 Apr 2020 at 23:07, Pavel Struhar notifications@github.com wrote:

Thank you! Is it going to be able to use an existing external coturn instance?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

mtyurt commented 4 years ago

For anyone who visits this issue, if you have followed the guide in meetrix.io and failed in prosody, here is the solution: https://github.com/jitsi/jitsi-meet/issues/6210