This message was deleted.
# helpdesks
steep-balloon-41261
12/12/2023, 3:00 PMThis message was deleted.
a
adventurous-twilight-28575
12/12/2023, 3:40 PMDisregard please. I had a minor configuration issue. Even with this stream magic the TURN server is responsible for terminating TLS.
Worx
adventurous-twilight-28575
12/12/2023, 3:50 PMJust one thing: This technique introduces a problem to LK, expressed in this log. Not sure, how severe this is. Most likely
Copy code
2023-12-12T15:47:18.371Z ERROR livekit.pion.turn pionlogger/logadapter.go:95 Failed to close conn: tls: failed to send closeNotify alert (but connection was closed anyway): write tcp4 127.0.0.1:5349->127.0.0.1:57446: write: broken pipe
<http://github.com/livekit/protocol/logger/pionlogger.(*logAdapter).Errorf|github.com/livekit/protocol/logger/pionlogger.(*logAdapter).Errorf>
/home/runner/go/pkg/mod/github.com/livekit/protocol@v1.9.1-0.20231107185101-e230ee2d840e/logger/pionlogger/logadapter.go:95
<http://github.com/pion/turn/v2.(*Server).readListener.func1|github.com/pion/turn/v2.(*Server).readListener.func1>
/home/runner/go/pkg/mod/github.com/pion/turn/v2@v2.1.4/server.go:153d
dry-elephant-14928
12/13/2023, 7:54 AMI'm not sure if that's an issue.. maybe related to how the connection is torn down.
do sessions work over TURN?
a
adventurous-twilight-28575
12/13/2023, 8:26 AMAt least TURN works and spits relay candidates. I’m currently not having a client making use of it. I‘m seeing this from time to time while using the trickle ICE test page linked above and refreshing the browser. I could imagine that the pc client in the browser goes w/o saying Goodbye and causing this disruption then
adventurous-twilight-28575
12/13/2023, 8:29 AMSeeing that connection tester in your answer on another thread. Will give it a try
adventurous-twilight-28575
12/13/2023, 8:35 AMYes, it says "Can connect via TURN". Is the source code of the connection tester available? For educational purposes?
PS: The a.m. trace did not appear while operating the test several times
PS2: I should have checked better. It appears there too:
Copy code
2023-12-13T08:35:07.959Z ERROR livekit.pion.turn pionlogger/logadapter.go:95 Failed to close conn: tls: failed to send closeNotify alert (but connection was closed anyway): write tcp4 127.0.0.1:5349->127.0.0.1:52706: write: broken pipe
github.com/livekit/protocol/logger/pionlogger.(*logAdapter).Errorf
/home/runner/go/pkg/mod/github.com/livekit/protocol@v1.9.1-0.20231107185101-e230ee2d840e/logger/pionlogger/logadapter.go:95
github.com/pion/turn/v2.(*Server).readListener.func1
/home/runner/go/pkg/mod/github.com/pion/turn/v2@v2.1.4/server.go:153d
dry-elephant-14928
12/13/2023, 10:32 PMit's here
a
adventurous-twilight-28575
12/14/2023, 1:30 AM👍
adventurous-twilight-28575
12/14/2023, 8:28 AMHmm. The TURN check is kind of poor or am I too blind?
d
dry-elephant-14928
12/15/2023, 6:23 AMwould you like to share any specifics? always welcome constructive feedback
a
adventurous-twilight-28575
12/15/2023, 6:39 AMAt the first glance it looks like as if “Can connect via TURN” is just based on the existence of TURNS or TURN in some URL prefixes. I was not able to see if the media connection finally really went over TURN. But I didn’t investigate much. Wireshark could probably answer.