https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# helpdesk
s
This message was deleted.
d
Hey Cris, can you send a screen shot of the connection tester results?
b
Thanks for replying @dry-elephant-14928
d
thanks! that looks pretty clean. I wonder if it's because it's sending back private candidates (i.e. the 
10.
) candidates. can you try setting 
rtc.external_ip_only
to false?
b
just thought about a new test to make : which was to use meet.livekit.io and tokens generated by my backend and bloody hell, it works. so must be part of our livekit implementation. Mind you, we're using a rather old version in the front-end, before you added all these goodies. even so, we'd like to get it to work, of course 🙂 I'll try to set that setting to false, let's see
👍 1
d
ah ok, then it sounds like a client-side thing of some sort
b
yeah, certainly looks that way. but we're using the livekit libraries
gonna chat with our front-end guy
could it be an older version of livekit (react) having a bug or something?
d
it's definitely possible
meet.livekit.io is using the latest version of the JS SDK
b
"@aloof-potato-24717/react-components": "^1.1.0",
can;t set it to false, k8s throws an error
😄
invalid spec
d
this needs to be in the livekit config section
i.e.
Copy code
livekit:
  rtc:
    external_ip_only: false
b
yes, that's right
d
this is set as 
values.yaml
with our helm chart?
b
yes
Copy code
rtc:
    port_range_end: 60000
    port_range_start: 50002
    tcp_port: 7881
    use_external_ip: false
it's complaining about non root privileges
PodSecurity etc Would elevating it be enough?
d
I'm not sure...
b
didnt 😄
container "livekit-server" must not set securityContext.privileged=true
let me find an old config that works, I'll try again Been messing about for a while with this, perhaps I made a mistake somewhere
the difference is now we get warnings in yellow
Copy code
WARNING: error with ICE candidate: 600 Address not associated with the desired network interface. turns:.......com:443?transport=tcp
d
hmmmm
networking config is quite tricky
b
yeah, indeed it is. I'm also not running on DO, or aws or any other. Bespoke cluster and all that 😄 It does work rather well. We'll upgrade the react package and see what happens...
👍 1
That's the only issue we have, corporate machines
Open in Slack
PreviousNext
Powered by