Skip to content
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

just a hint for the TURN Configuration #1774

Open
Thomas1K opened this issue Mar 27, 2024 · 1 comment
Open

just a hint for the TURN Configuration #1774

Thomas1K opened this issue Mar 27, 2024 · 1 comment

Comments

@Thomas1K
Copy link

Thomas1K commented Mar 27, 2024

stable-9364, on docker, behind a NAT (Sophos UTM)
external coturn server, listening on 443, with "use-auth-secret" and "static-auth-secret", sucessfully tested with Trickle and icetest.info

.env for jitsi contains

JVB_ADVERTISE_IPS=<docker-ip>,<external-ip>
TURN_HOST=turn.domain.de
TURN_PORT=443
TURN_TRANSPORT=tcp
TURN_CREDENTIAL=<static-auth-secret from coturn>

Edge is telling me this:
[JitsiConference.js] <$h._acceptJvbIncomingCall>: DOMException: Failed to construct 'RTCPeerConnection': Both username and credential are required when the URL scheme is "turn" or "turns".

Firefox is telling me this:
[JitsiConference.js] <972/$h.prototype._acceptJvbIncomingCall>: DOMException: RTCPeerConnection constructor passed invalid RTCConfiguration - missing username: turn:turn.domain.de:443?transport=tcp

and coturn remains silent, no connection is made.

can you please nudge me in the right direction?

@denzs
Copy link
Contributor

denzs commented Apr 3, 2024

It is TURN_CREDENTIALS instead of TURN_CREDENTIAL - see https://github.com/jitsi/docker-jitsi-meet/blob/master/prosody/rootfs/defaults/conf.d/jitsi-meet.cfg.lua#L85

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants