-
Notifications
You must be signed in to change notification settings - Fork 82
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
SSLHandshakeException: Connection closed by peer #463
Comments
Thanks for the details. Looking at the changelog, the only change made in the last version is adding an option to enforce TLS 1.2 from this library. This shouldn't affect you client side since the default behavior for TLS hasn't been changed and still depends on the android version running the app. However, another change introduced on that auth0.android version is disabling HTTP2 protocol, which only means "stick to the good old known protocols" that remain enabled for the client, and that the servers still accept. We required to change this because of a protocol version negotiation error. The OkHttp library being used is 2.7.5 (no longer maintained) and it has the HTTP2 protocol wrongly implemented and fails to negotiate the protocol version with the other peer. Anyway, this shouldn't be affecting you since like I said, old TLS & HTTP versions are still accepted by the server. If you find any clue or know where we can start digging to debug this, feel free to add it. |
Thanks for your response. I'm also getting this trace instead of
|
Is this still an issue? |
Hi @lbalmaceda , I cannot tell you if it's still happening because we're not using auth0 anymore, sorry. Best regards, |
Exception : javax.net.ssl.SSLHandshakeException Connection closed by peer |
I'm getting this exception from time to time after updating Lock.Android from
2.8.2
to2.8.3
:com.auth0.android:lock:2.8.3
gradle-4.6-all
3.1.1-3.1.2
27.0.3
19-27
Any idea? Thanks for your help.
The text was updated successfully, but these errors were encountered: