The WebSocket connection has already been closed (While SSL)

Open
#285 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
networking

Research direction

Start by reproducing the failure against wss://echo.websocket.org and the reporter's Node.js server, comparing it with the working ws:// endpoint. Trace the WebSocket client's SSL connection path; done means secure WebSocket connections complete successfully without the closed-connection error.

Written by the indexing model from the issue text.

Description

I receive "The WebSocket connection has already been closed" when i'm trying to connect at wss://echo.websocket.org or my node-js server.
This error appeared in when im trying to connet with sequre connection.
ws://echo.websockets.org works fine.

Dominant language
C#
Stars
6.1k
Forks
1.7k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sta/websocket-sharp

All issues in sta/websocket-sharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.