Chrome Version       : 57.0.2987.98
OS Version: Debian 9
URLs (if applicable) : https://turn1.whispersystems.org
Other browsers tested:
  Firefox 4.x: OK
         curl: OK
         wget: OK
       httpie: OK
      ssllabs: OK
       WebRTC: FAIL (https://chromium.googlesource.com/external/webrtc)

What steps will reproduce the problem?

1. Try to access to https://turn1.whispersystems.org
2. Chromium can't open the page (ERR_SSL_PROTOCOL_ERROR). The server side sees the client dropping the connection before the TLS handshake is finished.

Works fine with other browser (Firefox, command line tools), but it doesn't work when using Google's WebRTC library. This makes me suspect that the problem could be an incompatibility between BoringSSL the the server.

On the server side the coturn TURN server is running, I reported this issue in their repository too, but I'm starting to believe it's not coturn's fault:

https://github.com/coturn/coturn
https://github.com/coturn/coturn/issues/113


UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36