This message was deleted.
# helpdesk
s
This message was deleted.
w
@dry-elephant-14928 any thought on that? If more details are needed or clarify I’m more than happy to share 😄
d
Hey @wonderful-helmet-42260 I'm not sure about your setup. We don't officially support private IP via TURN setup because it's quite complicated to get right.
TBH there are a lot of nuances/bugs in browser behavior too, that sometimes it makes my brain hurt 😅 .
w
Let me share a top level diagram of our deployment
And it works very well by putting all the users in “relay” policy, then the SFU don’t need a public IP address
all the traffic goes from the users to the assigned TURN instance and that can comunicate via private network with the SFU
d
I see. that's great if this works for you
w
oks, I think I found the problem, next is a screenshot of the candidates generated in firefox that doesn’t work
The problem comes from the
host
candidates, that are not a IPv4 address but the livekit candidate is an IPv4 and Firefox has a mismatch and disables relay
the fix is select the checkbox
Acquire microphone/camera permissions
but then it needs to be done by the
client-sdk-js
this ICE candidates are generated in some local networks where is enabled
mDNS
, I found a reference here https://bloggeek.me/psa-mdns-and-local-ice-candidates-are-coming/
d
hmm I'm not sure if I understand why checking that box would impact the type of ICE candidates that are generated.. but those permissions are given when you make a call to
getUserMedia
. If that's needed isn't that something you could call directly?