https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# helpdesk
s
This message was deleted.
m
Hi @careful-kitchen-74863, could you please thread your messages? It makes it difficult for others to follow the conversation and help with your reported issue(s). ðŸ™ðŸ―
c
ah yes of course, sorry 😉
d
How did you deploy the server?
c
docker run --rm -it -v$PWD:/output livekit/generate
i have same behavior with both configuration: mine with nginx and caddy's automatically generated; this my netstat output "tcp 0 0 0.0.0.0:5349 0.0.0.0:* LISTEN 6494/livekit-server" so turn is listening
d
we do not handle nginx based deploys. It should work assuming TLS termination is configured correctly
c
ok then let's talk about caddy
i have same behavior with caddy that has been configured automatically....
when i call my livekit webpage i see "OK", if i call turn's webpage what should i see?
d
TURN/TLS wouldn't serve anything to your browser
c
Ok, how i can investigate more?
firewall ports are open, livekit is listening on port 5349, caddy is listening on port 443.... what could be the problem?
No idea? 😭
ok guys nobody wants to help me; i tried absolutely everything, i don't know how to fix, i tried in every way but i failed. livekit does not have a discord server, no tutorials, no resources; the only one is livekit.io and you (here) so I have no other solutions. Thanks for your help. See you.
m
@careful-kitchen-74863 first off, this (Slack) is the equivalent of a Discord server. Second, our docs on deployment has worked for many. We try our best to help everyone that has questions or needs advice, but it does require some patience, we usually catch up on community messages in the evenings and weekends.
c
I asked you for help because I read ALL your guides and documentation on deployment. I spent hours trying. It's a strange situation, I'm not new to Linux, I know how it works but I can't solve this problem so I need someone who knows the livekit application. I'll wait for someone to help me
d
as Russ mentioned, this is a community channel where it's not guaranteed someone will know how to solve your specific problem. we are making LiveKit open for all to use, but there isn't enough time in a day to help everyone deploy it. What I can say on this is folks rarely report issues using the generated deployment on a simple provider like Digital Ocean. I would suggest trying the above combination first
c
https://pastebin.com/05Vbm2qB This my livekit-server verbose log. I don't see any errors but your test keeps giving me error on the turn connection.
turn and caddy are listening.. Some idea?
The only suspect string ithat i can see is: 1. 
2022-09-29T15:57:40.860+0200    INFO    livekit rtc*/*participant.go:640  try close participant   *{*"room": "stark-tower", "roomID": "RM_8VdJUKwkgs5m", "participant": "tony_stark", "pID": "PA_NyjMABaaTV8m", "remote": *false*, "sendLeave": *true*, "reason": "DUPLICATE_IDENTITY"*}*
maybe turn-server is ok and there is a token problem?
d
yeah, I think you are right. I've just confirmed that with a fresh setup, the TURN test isn't passing, but I believe it's a test issue. TURN/TLS should be working correctly.
ok, confirmed TURN/TLS is working properly even though test is indicating otherwise. we'll look into improving the test itself, but your setup seems to be working just fine
c
😭ðŸĨ°
I was going crazy...
ðŸĪŠ 1
m
Thanks for pushing on this @careful-kitchen-74863. ðŸ™ðŸ―
c
ðŸĪ
please let me know (ping me) when the tester will ok 😉
hi guys, I'm back with the same problem.... livekit tester can't verify my turn, is it still the old problem or is it my problem this time?
@dry-elephant-14928 @magnificent-art-43333 maybe livekit-tester has been fixed and now works fine in detecting turns?
Livekit (and Turn) server started without problems, TLS endpoint is in another PC that run as a proxy server, so unencrypted traffic is redirected to livekit/turn server PC on port 5349
???
Please help
d
your TURN server isn't setup correctly. likely due to how TLS is configured. Note that you have 
external_tls
set to true
c
this is correct, my certificates are in another server, a reverse proxy with nginx, so turn incoming traffic is unencrypted on port 5349, for this scenario my conf still uncorrect?
d
the config is fine in that case, but it's most likely your nginx server is configured incorrectly.
c
I don't know what to try anymore, could you please tell me which ports nginx should listen to and on which ports of the PC with livekit it should proxy?
Currently, the router is forwarding incoming TCP port 5349 to the Nginx server, which decrypts the data and forwards the traffic to TCP port 5349 on the machine with the livekit server, using the configuration I have already sent you.
d
given the complexity of deployment environments.. we really aren't in a position of troubleshooting each install with users. what I can say is most folks have no problems following the automatic Caddy setup that we've provided here.
2 Views
Open in Slack
PreviousNext
Powered by