-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let’s Encrypt certificates for TURNS are rejected #2712
Comments
i would like to +1 this. |
May be this helps : I'v used a fullchain certificate instead of a single one, no more socket error ! I'm using the same fullchain certificate on my reverse proxy. Certificate are generate by Let's Encrypt. |
4 tasks
4 tasks
richvdh
changed the title
TURNS (TURN with TLS/DTLS) socket buffer operation error
Let’s Encrypt certificates for TURNS are rejected
Jan 5, 2022
DMRobertson
pushed a commit
to matrix-org/synapse
that referenced
this issue
Jan 17, 2022
* Warn against using Let's Encrypt certs for encrypted TURN This helps to avoid client-side issues: * element-hq/element-android#1533 * element-hq/element-ios#2712 Signed-off-by: Andrew Ferrazzutti <[email protected]>
I think this issue is now resolved. See more details here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TURNS doesn't work.
With
turn_uris: [ "turns:domain.tld:5349?transport=udp", "turns:domain.tld:5349?transport=tcp" ]
or
turn_uris: [ "turns:domain.tld:3478?transport=udp", "turns:domain.tld:3478?transport=tcp" ]
turnserver reports an error:
session closed ... reason: TLS/TCP socket buffer operation error (callback)
riot-web works fine,
testssl.sh domain.tld:5349
andtestssl.sh domain.tld:3478
also shows no errors.The text was updated successfully, but these errors were encountered: