alexkirsz/dispatch-proxy

client request error

Open

#49 opened on May 29, 2015

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

Description

any idea what cause following issue?

dispatch start --http -p 7000 HTTP server started on localhost:7000 Dispatching to addresses 10.3.150.3@1, 192.168.1.3@1 error [068db1] clientRequest Error: connect EADDRNOTAVAIL at exports._errnoException (util.js:746:11) at TCPConnectWrap.afterConnect as oncomplete error [90108d] clientRequest Error: connect EADDRNOTAVAIL at exports._errnoException (util.js:746:11) at TCPConnectWrap.afterConnect as oncomplete

Contributor guide

Tech stack
nodejs
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.
1-3 hours
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
Basic Node.js knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
The error 'EADDRNOTAVAIL' suggests that the network address specified is not available on the local machine. The user should verify that the IP addresses used in the dispatch command (10.3.150.3 and 192.168.1.3) are correct and correspond to active network interfaces. Additionally, check the dispatch proxy documentation for correct address format and any configuration requirements. The issue may be resolved by using a different or valid local address.