alexkirsz/dispatch-proxy

Error trying to dispatch two connections

Open

#44 opened on Apr 9, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)CoffeeScript (3,490 stars) (243 forks)batch import
help wanted

Description

Hi! i have two connections and when i try to use jdownloader or any torrent client throws me this errors: (note: using socks or http option, both of them doesnt work, any ideas?)

C:\Windows\system32>dispatch start SOCKS server started on localhost:1080 Dispatching to addresses 10.0.0.99@1, 10.0.0.6@1 events.js:85 throw er; // Unhandled 'error' event ^ Error: read ECONNRESET at exports._errnoException (util.js:746:11) at TCP.onread (net.js:559:26)

C:\Windows\system32>dispatch start --http HTTP server started on localhost:8080 Dispatching to addresses 10.0.0.99@1, 10.0.0.6@1 ^C¿Desea terminar el trabajo por lotes (S/N)? s

C:\Windows\system32>dispatch start SOCKS server started on localhost:1080 Dispatching to addresses 10.0.0.99@1, 10.0.0.6@1 events.js:85 throw er; // Unhandled 'error' event ^ Error: read ECONNRESET at exports._errnoException (util.js:746:11) at TCP.onread (net.js:559:26)

C:\Windows\system32>dispatch start --http HTTP server started on localhost:8080 Dispatching to addresses 10.0.0.99@1, 10.0.0.6@1 ^C¿Desea terminar el trabajo por lotes (S/N)? s

C:\Windows\system32>dispatch start SOCKS server started on localhost:1080 Dispatching to addresses 10.0.0.99@1, 10.0.0.6@1 C:\Users\Server\AppData\Roaming\npm\node_modules\dispatch-proxy\node_modules\soc ks-handler\lib\socks4\index.js:23 return request.call(this, chunk); ^ TypeError: undefined is not a function at Stream. (C:\Users\Server\AppData\Roaming\npm\node_modules\disp atch-proxy\node_modules\socks-handler\lib\socks4\index.js:23:24) at Stream.stream.write (C:\Users\Server\AppData\Roaming\npm\node_modules\dis patch-proxy\node_modules\socks-handler\node_modules\through\index.js:26:11) at Socket.ondata (_stream_readable.js:540:20) at Socket.emit (events.js:129:20) at readableAddChunk (_stream_readable.js:163:16) at Socket.Readable.push (_stream_readable.js:126:10) at TCP.onread (net.js:538:20)

Ty for your time!

Contributor guide

Tech stack
javascriptnodejs
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Node.jsbasic networking
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue involves an ECONNRESET error and a TypeError in socks handler's socks4/index.js. Start by examining the socks handler library, especially the socks4/index.js line 23 where the TypeError occurs. Then, review how dispatch proxy handles multiple connections to reproduce the error. Check if there are any existing fixes or discussions in related issues or pull requests.