-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find new way to integrate TURN server #73
Comments
It would be possible... remapping ports. |
@lonesomewalker I'm not sure what you mean? :) |
I remember someone from Jitsi suggested to use nginx's preread and coturn ALPN to forward traffic from nginx to coturn and have both services behind port 443 on a reverse proxy. |
They seem to have tried and deprecated that approach. Instead they now seem to be multiplexing 443 connections based on DNS/host names @alangecker Could this approach be applied to this docker setup?
|
I really like that idea! maybe one could even avoid the need of two domains by detecting the protocol?
Difficult is, that this must be part of the nginx config, which also does the auto certificate retrieval (currently I don't now whether I will find time during the next weeks, but I would be really happy to see anyone working on that :) |
#126 brings back turn support :) |
In some restrictive networks UDP is blocked, why we need a TURN server. Because sometimes also most TCP ports except them HTTP and Mailing are blocked as well.
To traverse these firewalls we used so far the TLS mail port
465
, but firefox and chromium started blocking almost all TCP ports below 1024 for TURN Server, which basically means there is only port 443 for TURN left, but already in use by HTTPS.Currently I see no way to automatically integrate coturn without an second IP.
Important
Existing bbb-docker instances with enabled coturn on our default port
465
will gradually throw more and more1006
errors with recent browser updates become more spread.Best option: get a cheap VM and setup a TURN server there on port 443. This guide is helpful:
https://docs.bigbluebutton.org/2.2/setup-turn-server.html
Minimal step: disable the TURN server with commenting out
TURN_SERVER
in.env
References
https://bugzilla.mozilla.org/show_bug.cgi?id=1699175
https://webrtc.googlesource.com/src/+/master/p2p/base/turn_port.cc#947
https://searchfox.org/mozilla-central/source/netwerk/base/nsIOService.cpp#98
The text was updated successfully, but these errors were encountered: