WebSocket is closed before the connection is established.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 63.2k
- Forks
- 10.3k
- Avg merge
- 11d 20h
- Merged PRs (30d)
- 2
Description
Describe the bug
after a long time of connection websocket does not connect and throws "WebSocket is closed before the connection is established." until you restart the server.
To Reproduce
Keep monitoring socket connection for a long time.
Socket.IO client version: @nestjs/platform-socket.io": "^10.4.6"
Expected behavior
Should not happen.
Platform:
- Device: Ubuntu chrome browser
- OS: Ubuntu
Contributor guide
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
No repository file, test, or entry point is named. Start by reproducing the long-running connection failure with the reported Socket.IO client setup on Ubuntu and inspect the server and client logs around the failed WebSocket upgrade. Done means identifying a reproducible cause and preventing the connection from closing before establishment without requiring a server restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100