TLS connection aborted in WebRTC

[Xavier Marjou]

Context : a basic WebRTC communication in which one of the 2 browsers can only send/receive WebRTC flows with TLS/TCP. I'm thus trying to use TURN/TLS/TCP to transport WebRTC flows between an rfc5766-turn-server relay and a 30 beta-m Chrome browser. 

Right after the TLS handshake, Chrome closes the connection with a TCP FIN ACK message (no data has been sent yet on the connection), and I can not figure out why. 

Any idea how to solve it?

Thanks,

Xavier

PS: here are the messages that I observe with Wireshark on the browser's side :

chrome      turn-server

--> TCP SYN

<-- TCP SYN, ACK

--> ACK

--> TLSv1.2 Client Hello

<-- TLS v1.2 Server Hello, Certificate, Hello Done

--> TLS v1.2 Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message

<-- TLS v1.2 New Session Ticket, Change Cipher Spec, Encrypted Handshake Message

--> TCP FIN ACK

<-- TCP FIN ACK

[Oleg Moskalenko]

I have no immediate idea.

I am somewhat surprised that Chrome wants to use TLS 1.2, but that's fine.

One thing that comes to mind is that Chrome may be awaiting for a certain type of certificate - and the chrome does not like the certificate that you provided. Try to browse through the chrome logs and try to play with the certificate.

Another thing is that you can try to limit TLS connection to TLS 1.1 or 1.0 (by changing the cipher suite in the settings) and see whether it helps.

Oleg

[Xavier Marjou]

That was indeed a problem of certificate validity in Chrome. I fixed it ;

now I have "my" WebRTC flows being successfully transported with TURN/TLS.

By the way, TLSv1.2 worked fine in this case.

Thanks

[Oleg Moskalenko]

Great. Thanks for the feedback and for testing that.

Oleg

[gourab biswas]

How did u fix it?? currently i am also facing the same prob that u have mentioned..

[Basar Daldal]

Hi,

How is this fixed? We see the same issue.

Thanks,

Basar

[Raghavendra Uppalapati]

Hi Xavier,

We are also facing the same problem?  Chrome immediatley closes the connection.

Can you please tell us how to fix this?

--

Thanks

Raghavendra