[ERROR]An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 15.2k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
[env]
windows 11
client-version newest
[how to recurrent]
run the client with command like brook_windows_amd64.exe" client --link="brook://wssserver?password=xxxx&tlsfingerprint=chrome&wssserver=wss://xxxx.com:443" --socks5 0.0.0.0:1080 --http 0.0.0.0:1081
use http proxy in one day.
you will see the CMD out 2025/01/25 12:52:02 socks connect tcp 0.0.0.0:1080->api2.cursor.sh:443: dial tcp 0.0.0.0:1080: bind: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
and proxy is broken.
how to solve this problem?
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
Start by reproducing the reported command on Windows 11 with the newest client, using the SOCKS5 and HTTP proxy settings shown. Investigate the socket bind failure and determine whether it is caused by the client or the Windows environment; done means the cause and a verified resolution or documented limitation are established.
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
- 30/100