Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.

Postponed

Votes

0

Found in

2017.2.0p4

Issue ID

1043859

Regression

No

Authentication error and failed connection through wss using WebSocketSharp

Networking

-

Reproduction steps:
1. Open the attached project.
2. Play the WSTest Scene.
3. Check the Console.

Actual behavior:
- The connection will fail.
- "WebSocket.onError An exception has occurred while connecting"
- "WebSocket.onClose code 1006, reason = An exception has occurred while connecting., wasClean = False"

WebSocket library generated log:
|Fatal|WebSocket.acceptException|System.IO.IOException: The authentication or decryption has failed. ---> Mono.Security.Protocol.Tls.TlsException: The server stopped the handshake.
at Mono.Security.Protocol.Tls.SslClientStream.SafeReceiveRecord (System.IO.Stream s) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.SslClientStream.OnNegotiateHandshakeCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
|Trace|WebSocket.close|Start closing handshake.
|Debug|WebSocket.closeHandshake|Was clean?: False
sent: False received: True
|Trace|WebSocket.close|End closing handshake.

Reproduced with:
5.6.6f2, 2017.1.4p1, 2017.2.3p1, 2017.4.5f1, 2018.1.4f1, 2018.2.0b7, 2018.3.0a1
Log in to vote on this issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues