Node.js Error: connect ECONNREFUSED
Javascriptnode.jsJavascript Problem Overview
I am new to node and running into this error on a simple tutorial.
I am on the OS X 10.8.2 trying this from CodeRunner and the Terminal.
I have also tried putting my module in the node_modules folder.
I can tell this is some kind of connection problem but I have no idea why?
events.js:71
throw arguments[1]; // Unhandled 'error' event
^
Error: connect ECONNREFUSED
at errnoException (net.js:770:11)
at Object.afterConnect [as oncomplete] (net.js:761:19)
app.js:
var makeRequest = require('./make_request');
makeRequest("Here's looking at you, kid");
makeRequest("Hello, this is dog");
make_request.js:
var http = require('http');
var makeRequest = function(message) {
//var message = "Here's looking at you, kid.";
var options = {
host: 'localhost', port: 8080, path:'/', method: 'POST'
}
var request = http.request(options, function(response) {
response.on('data', function(data) {
console.log(data);
});
});
request.write(message);
request.end();
};
module.exports = makeRequest;
Javascript Solutions
Solution 1 - Javascript
Chances are you are struggling with the node.js dying whenever the server you are calling refuses to connect. Try this:
process.on('uncaughtException', function (err) {
console.log(err);
});
This keeps your server running and also give you a place to attach the debugger and look for a deeper problem.
Solution 2 - Javascript
You're trying to connect to localhost:8080 ... is any service running on your localhost and on this port? If not, the connection is refused which cause this error. I would suggest to check if there is anything running on localhost:8080 first.
Solution 3 - Javascript
I was having the same issue with ghost and heroku.
heroku config:set NODE_ENV=production
solved it!
Check your config and env that the server is running on.
Solution 4 - Javascript
You need to have a server running on port 8080 when you run the code above that simply returns the request back through the response. Copy the code below to a separate file (say 'server.js') and start this server using the node command (node server.js). You can then separately run your code above (node app.js) from a separate command line.
var http = require('http');
http.createServer(function(request, response){
//The following code will print out the incoming request text
request.pipe(response);
}).listen(8080, '127.0.0.1');
console.log('Listening on port 8080...');
Solution 5 - Javascript
Sometimes it may occur, if there is any database connection in your code but you did not start the database server yet.
Im my case i have some piece of code to connect with mongodb
mongoose.connect("mongodb://localhost:27017/demoDb");
after i started the mongodb server with the command mongod this error is gone
Solution 6 - Javascript
If you are on MEAN (Mongo-Express-AngularJS-Node) stack, run mongod first, and this error message will go away.
Solution 7 - Javascript
ECONNREFUSED error means that connection could not be made with the target service (in your case localhost:8080). Check your service running on port 8080.
To know more about node.js errors, refer this doc.
Solution 8 - Javascript
People run into this error when the Node.js process is still running and they are attempting to start the server again. Try this:
ps aux | grep node
This will print something along the lines of:
user 7668 4.3 1.0 42060 10708 pts/1 Sl+ 20:36 0:00 node server
user 7749 0.0 0.0 4384 832 pts/8 S+ 20:37 0:00 grep --color=auto node
In this case, the process will be the one with the pid 7668. To kill it and restart the server, run kill -9 7668.
Solution 9 - Javascript
Check with starting mysql in terminal. Use below command
mysql-ctl start
In my case its worked
Solution 10 - Javascript
Run server.js from a different command line and client.js from a different command line
Solution 11 - Javascript
For me it was a problem in library node-agent-base v4.x which was requested by https-proxy-agent which in it's side was requested by newrelic v5.x library.
The problem was that node-agent-base v4.x for some marvellous idea decided to patch core https.get request (You can see this in the file patch-core.js in the repo). And when I used library which use https.get, it was failed because node-agent-base v4.x have changed function signature, which gave me request to 127.0.0.1 as initial url was lost...
I've fixed this by updating to the next version of newrelic 6.x, where node-agent-base v4.x doesn't has such 'patches'.
This is just crazy...hope my response will save you some time, I've spent several days to debug this.
Solution 12 - Javascript
The Unhandled 'error' event is referring not providing a function to the request to pass errors. Without this event the node process ends with the error instead of failing gracefully and providing actual feedback. You can set the event just before the request.write line to catch any issues:
request.on('error', function(err)
{
console.log(err);
});
More examples below:
https://nodejs.org/api/http.html#http_http_request_options_callback
Solution 13 - Javascript
Had a similar issue, it turned out the listening port printed was different from what it actually was. Typos in the request string or listening function might make the target server appear to not exist.
Solution 14 - Javascript
I was having the same issue in my dev env with Postman when checking the API. I searched literally all the answers came from google, but no avail.
SOLUTION: I have just moved to "insomnia" (an alternative to Postman) and it works just fine. Hope this workaround may help.