Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Warn against using Let's Encrypt certs for encrypted TURN #11686

Merged
merged 4 commits into from
Jan 17, 2022
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion changelog.d/11686.doc
Original file line number Diff line number Diff line change
@@ -1 +1 @@
Warn against using a Let's Encrypt certificate for TLS/DTLS TURN server client connections, and suggest using ZeroSSL certificate instead. This bypasses client-side connectivity errors focaused by WebRTC libraries that reject Let's Encrypt certificates. Contibuted by @AndrewFerr.
Warn against using a Let's Encrypt certificate for TLS/DTLS TURN server client connections, and suggest using ZeroSSL certificate instead. This bypasses client-side connectivity errors caused by WebRTC libraries that reject Let's Encrypt certificates. Contibuted by @AndrewFerr.
4 changes: 2 additions & 2 deletions docs/turn-howto.md
Original file line number Diff line number Diff line change
Expand Up @@ -151,8 +151,8 @@ This will install and start a systemd service called `coturn`.

NB: If your TLS certificate was provided by Let's Encrypt, TLS/DTLS will
not work with any Matrix client that uses Chromium's WebRTC library. This
AndrewFerr marked this conversation as resolved.
Show resolved Hide resolved
currently includes Element Android/iOS; see their [respective](https://github.com/vector-im/element-android/issues/1533)
[issues](https://github.com/vector-im/element-ios/issues/2712) for more details.
currently includes Element Android & iOS. For more details, read the underlying
[WebRTC issue](https://bugs.chromium.org/p/webrtc/issues/detail?id=11710).
AndrewFerr marked this conversation as resolved.
Show resolved Hide resolved
Consider using a ZeroSSL certificate for your TURN server as a working alternative.

1. Ensure your firewall allows traffic into the TURN server on the ports
Expand Down