An error has occurred during a TLS handshake. (wss)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Server: Node + ws (npm)
Client: Unity3D (4.6) + websocket-sharp
Usually the connection is good. But sometimes (5-10%) you receive this message.
(An error has occurred during a TLS handshake. )
When receive this message, handshake is hanged for 3 minutes.
I found the code.
WebSocket.cs
private void setClientStream() { ... sslStream.AuthenticateAsClient(...) <== hang ... }
It Is Secured WebSocket has this chronic problem? (.net's bug??... unity3d's old framework)
(https://www.google.co.jp/webhp?sourceid=chrome-instant&ion=1&espv=2&es_th=1&ie=UTF-8#q=AuthenticateAsClient+hang)
Or, the server's the problem?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in WebSocket.cs at setClientStream and the sslStream.AuthenticateAsClient call. Reproduce the intermittent secured-WebSocket failure with the listed Unity3D client and Node + ws server, then trace whether the three-minute hang is caused by the client or server. Done means the cause is identified and a focused fix or documented limitation is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100