-
Notifications
You must be signed in to change notification settings - Fork 395
TURNS (TURN with TLS/DTLS) socket buffer operation error #3299
Comments
I had the same problem, I am using a free certificate (letscrypt) |
No problem here. But I am using my own TURN server. |
You'd like to say you're using ssl'ed turn without any issues? |
@root562 yeah, I am also using my own TURN server . When I use non-ssl mode ( turn:yourdomain), it can be used, but ssl mode( turns:yourdomain ) will report an error |
No SSL on my TURN. My Turn server is only accessible by VPN. |
So, what the reason to reply have no problem if you even don't use TURNS? |
I'm also seeing this with coturn 4.5.0.7-1ubuntu2.18.04. This is with riot 0.9.8 on Android 9. I had Can confirm it works flawlessly without TLS and that Nextcloud Talk works with the same coturn server using TLS. |
Exact same issue here: (D)TLS does not work, only unencrypted communication works. I am running coturn 4.5.1.1 from Debian and riot-android 0.9.9 on Android 9 |
Same problem by me. DTLS does not work. Only unencrypted. |
On riot-web I've got the same error but still, the voice is working ... |
I can confirm the same issue on riot android when using coturn with SSL. Unencrypted works fine. Do we know if this is in anyone's radar to fix? |
I had the same problem on a debian buster system … My advice: double check the certificates on the coturn server (are they really valid?) an the paths to the certificates specified in turnserver.conf, make them accessible by the user running coturn. |
same problem here. It works fine through the Linux (riot-web) client. Can any developer shed some light on which certificates store is used on the Android app to trigger the turns connection? |
I've SSL cert from CA authority other than LetsEncrypt's and SSL and TURN server doesn't works properly with iOS and WEB Client. For workaround to work this i'm temporally disabled SSL with parameters at turnserver.conf: no-sslv3 And works perfectly with audio and audio/video one-one via Riot client. |
@djrzulf do you also get an Unknown CA TLS Alert in the packets dump? If so, which CA is your cert signed by? |
Some problem here, using coturn with jitsi. Does it have something to do with the |
same problem heare lifetime=0, cipher=TLS_AES_256_GCM_SHA384, method=UNKNOWN |
Actually, a still open issue. Have the same problems with coturn & BBB on Debian Buster, TLS ON = error, OFF = working. |
I also have the problem, but it also doesn't work for me if I deactivate ssl/tls in my config. The it seems as the webclient connects succesfull, but the android app still fails. |
Able to reproduce. works perfectly with turn:, not working with turns:. |
Very similar to jitsi/jitsi-meet#6383 (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: