Software Mansion•3mo ago

WebRTC TURN TCP/TLS configuration issue

Hey! I'm loving the framework - using it in production with great success. We've got some users who (I think) are having trouble making the TURN connection to our server using UDP - typically these users are on restrictive corporate VPNs. My thought is that setting up our TCP/TLS TURN properly might help. I've set it up similar to this: https://github.com/fishjam-dev/membrane_rtc_engine/blob/eb8f97d254f5925139cdc1e76df0ecd0ac4977e9/examples/webrtc_to_hls/lib/webrtc_to_hls/stream.ex#L150 However, it doesn't seem to be working out. On Chrome, I see WebRTC debug errors like this:

icecandidateerror
url: turn:IP-REDACTED:3478?transport=tcp
address: 192.168.0.x
port: 61317
host_candidate: 192.168.0.x:61317
error_text: Address not associated with the desired network interface.
error_code: 600

icecandidateerror
url: turn:IP-REDACTED:3478?transport=tcp
address: 192.168.0.x
port: 61317
host_candidate: 192.168.0.x:61317
error_text: Address not associated with the desired network interface.
error_code: 600

And on Firefox I get an error

stun error code 401

stun error code 401

Do you know what I might be doing wrong in my configuration?

3 Replies

mat_hek•3mo ago

cc @Jellyfish/WebRTC

Michał Śledź•3mo ago

Hi @BrainTrain3000 ! Are there any logs on the server side?

DJMAKEITBRAINOP•3mo ago

Sorry for the long delay - getting a ton of logs on the server side, but I'm not sure what to look for. I'm not seeing anything pertinent

Gaming

Programming

WebRTC TURN TCP/TLS configuration issue