- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have also facing this issue in our production environment. We are using 4.3.1 version media server. From latest chrome (85.0.4183.83) we can't able to publish or subscribe streams.
From webrtc agent we got some DTLS handshaking error logs as given below.
2020-08-27 09:46:55,928 - WARN: DtlsTransport - id: 634795490676200000, message: Handshake failed, transportName:video, openSSLerror: error:1410241A:SSL routines:dtls1_read_bytes:tlsv1 alert decode error
2020-08-27 09:46:55,928 - ERROR: WebRtcConnection - id: 634795490676200000, message: Transport Failed, transportType: video
2020-08-27 09:46:55.929 - WARN: Connection - message: failed the ICE process, code: 502, id: 634795490676200000
2020-08-27 09:46:55.929 - WARN: WrtcConnection - ICE failed, 500 634795490676200000
2020-08-27 09:46:55.940 - WARN: WorkingNode - Exiting on SIGTERM
2020-08-27 09:46:56,239 - WARN: dtls.SSL - failed in unknown state
2020-08-27 09:46:56,240 - ERROR: dtls.DtlsSocket - SSL error 1
2020-08-27 09:46:56,240 - WARN: dtls.DtlsSocketContext - DTLS Handshake Failure error:1410241A:SSL routines:dtls1_read_bytes:tlsv1 alert decode error
2020-08-27 09:46:56,240 - WARN: DtlsTransport - id: 116133080745505220, message: Handshake failed, transportName:video, openSSLerror: error:1410241A:SSL routines:dtls1_read_bytes:tlsv1 alert decode error
2020-08-27 09:46:56,240 - ERROR: WebRtcConnection - id: 116133080745505220, message: Transport Failed, transportType: video
2020-08-27 09:46:56.240 - WARN: Connection - message: failed the ICE process, code: 502, id: 116133080745505220
2020-08-27 09:46:56.241 - WARN: WrtcConnection - ICE failed, 500 116133080745505220
How can we solve this problem?.
Any update would be appreciated.
Thanks.
dtls.SSL - failed in unknown state
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
https://github.com/open-webrtc-toolkit/owt-server/pull/599 solve the problem.
I think the 4.3.2 release will fix the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your quick reply.
Dear team please let us know when will be the new release coming?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 months passed by and still no 4.3.2 with the fix included.
there was a much faster response back in the in 3.x releases, it has become a very disappointing product now. We are migrating away from this framework
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page