Client process dead unexpectedly on Win10
Open
Nobody has claimed this yet.
need-more-info
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
I set up a chisel server with SSL and connect it from my local end (on Windows 10) via SOCKS5 w/ the parameter "--keepalive 60s". It works but the client process gets terminated unexpectedly at times and has to be restarted. Should I adjust the parameters?
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
No file, test, log, or client entry point is identified in the report. Reproduce the Windows 10 SSL/SOCKS5 case with --keepalive 60s and capture why the client terminates; done means determining whether a parameter change prevents the unexpected exit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100