Search Issue Tracker
Fixed in 2018.3.X
Votes
1
Found in
2018.2.0a5
2018.2.0b7
Issue ID
1046610
Regression
No
TLS Handshake exception is generated when connecting to mumble server
Steps to reproduce:
1. Download 1046610_repro.zip
2. Open "Example" scene (Assets -> Mumble-Unity)
3. Enter play mode
4. Notice that in Console window exception is printed
Results: Connection wasn't established due to TLS handshake fail
Exception:
System.AggregateException: One or more errors occurred. ---> System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> Mono.Security.Interface.TlsException: Handshake failed - error code: UNITYTLS_INTERNAL_ERROR, verify result: UNITYTLS_X509VERIFY_FATAL_ERROR
Reproduced with: 2018.3.0a1, 2018.2.0b8, 2018.2.a5
Not reproducible with: 2018.1.5f1
Regression introduced in: 2018.2.0a5
Comments (18)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inspector elements are rendered twice when the script component is added via drag-and-drop while the HideFlags.HideInInspector property is set
- Error "Light baking failed with error code 5 (Convergence data not available while rendering lightmaps)" thrown in Console when generating lighting for specific GameObjects
- Copy and Paste options for an Animation Property value are disabled in the Right click contextual menu
- Asset is not found when searching the Label "NewLabel" in Search Window
- "Compute dispatch: missing texture ID..." and "Compute dispatch: missing UAV ID..." warnings are thrown after changing the platform in High Definition 3D template
Yacuzo
Sep 14, 2018 13:30
I still get undefined network errors using UnityWebRequest on https with 2018.2.6 and 2018.3.0b.
ashikns
Sep 01, 2018 19:28
Still happening in Unity 2018.2.5. In which version is this fixed?
Senkh
Aug 16, 2018 15:49
i can confirm this is still happening in the 2018.2.3f1 (64-bit) version. I was trying to open a connection to a simple MySql database (dedicated server).
The workaround was to go back to the 2018.1.5f1 version (works fine), or to downgrade to .Net 3.5 library, both worked. I hope this helps.
Please, NOT solved, enable votes.
MonoNtonic
Aug 09, 2018 18:32
I´m also on 2018.2.2f1 trying to connect to MySQL getting the same error.
chriswadair
Aug 09, 2018 17:45
I'm on 2018.2.2f1 and I'm still getting this when trying to connect to a MySQL server
Yacuzo
Aug 09, 2018 06:26
I'm on 2018.2.2 and this bug is still there. I get this when contacting a Girder site (some python open source website-base).
andrew_unity420
Jul 02, 2018 02:58
I too am up against this. It says its been fixed in 2018.2 but I don't see the fix in 2018.2.0b9.. which release has it?
Zendist
Jun 24, 2018 08:53
I am getting the same issue.
First I got it with UnityWebRequest.Get(...), then I tried with System.Net.WebClient(...) and got the same issue but a much more interesting exception stack trace (which led me to this issue).
The issue only occurs when I target my localhost https server (dev server with localhost https cert from IIS Express), not when I target my production server (which gets an SSL cert from LetsEncrypt).
Mono.Security.Interface.TlsException: Handshake failed - error code: UNITYTLS_INTERNAL_ERROR, verify result: UNITYTLS_X509VERIFY_FATAL_ERROR.
(2018.2.0b9)
This is a regression, I have not usually run into this exception with the exact same environment - only Unity version has changed.