Error: ECONNREFUSED, Connection refused #1125

Closed
harishv opened this Issue May 4, 2012 · 4 comments

2 participants

@harishv

Hi Friends,

I'm getting the following error's very frequently from the time I moved my code-set from a local system to a Cloud Server.

Please help me out in fixing this.

Error #1:

node.js:134
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: ECONNREFUSED, Connection refused
at Socket._onConnect (net.js:601:18)
at IOWatcher.onWritable as callback

Error #2:

node.js:134
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: ECONNREFUSED, Connection refused
at Client._onConnect (net.js:601:18)
at IOWatcher.onWritable as callback

Thanks in advance.

@tj
expressjs member
tj commented May 4, 2012

that just means there's something that already 'claimed' that address via bind()

@harishv

TJ,

Can you please suggest some ideas to fix this.?

@tj
expressjs member
tj commented May 4, 2012

my guess is that the server(s) were left running, so when you try to publish to the "cloud" it isn't shutting those down

@tj
expressjs member
tj commented May 4, 2012

I'll have to close though since this is just a general tcp server thing. Might be worth checking with your provider if you can't make sure they're shut down

@tj tj closed this May 4, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment