node.js Error: connect ECONNREFUSED; response from server

I have a problem with this little program:

var http = require("http");
var request = http.request({ hostname: "localhost", port: 8000, path: "/", method: "GET"
}, function(response) { var statusCode = response.statusCode; var headers = response.headers; var statusLine = "HTTP/" + response.httpVersion + " " +statusCode + " " + http.STATUS_CODES[statusCode]; console.log(statusLine); for (header in headers) { console.log(header + ": " + headers[header]); } console.log(); response.setEncoding("utf8"); response.on("data", function(data) { process.stdout.write(data); }); response.on("end", function() { console.log(); });
});

The result in console is this:

events.js:141 throw er; // Unhandled 'error' event ^
Error: connect ECONNREFUSED 127.0.0.1:8000 at Object.exports._errnoException (util.js:870:11) at exports._exceptionWithHostPort (util.js:893:20) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1063:14)

I do not understand why this happens.

9

11 Answers

From your code, It looks like your file contains code that makes get request to localhost (127.0.0.1:8000).

The problem might be you have not created server on your local machine which listens to port 8000.

For that you have to set up server on localhost which can serve your request.

  1. Create server.js

    var express = require('express');
    var app = express();
    app.get('/', function (req, res) { res.send('Hello World!'); // This will serve your request to '/'.
    });
    app.listen(8000, function () { console.log('Example app listening on port 8000!'); });
  2. Run server.js : node server.js

  3. Run file that contains code to make request.

2

Please use [::1] instead of localhost, and make sure that the port is correct, and put the port inside the link.

const request = require('request'); let json = { "id": id, "filename": filename }; let options = { uri: "" + constants.PATH_TO_API, // port:443, method: 'POST', json: json }; request(options, function (error, response, body) { if (error) { console.error("httpRequests : error " + error); } if (response) { let statusCode = response.status_code; if (callback) { callback(body); } } });
3

I had the same problem on my mac, but in my case, the problem was that I did not run the database (sudo mongod) before; the problem was solved when I first ran the mondo sudod on the console and, once it was done, on another console, the connection to the server ...

i solve this problem with redis-server, you can install that like this! sudo apt-get install redis-server after that see the port and change it!

Just run the following command in the node project:

npm install

Its worked for me.

i ran the local mysql database, but not in administrator mode, which threw this error

If you have stopped the mongod.exe service from the task manager, you need to restart the service. In my case I stopped the service from task manager and on restart it doesn't automatically started.

I got this error because my AdonisJS server was not running before I ran the test. Running the server first fixed it.

just run the following command in the node project

npm install its worked for me

1

This is very slight error. When I was implementing Event server between my processes on nodejs.

Just check for the package you're using to run your server like Axios.

Maybe you might have relocated the files or disconnected some cache data on the browsers.

It's simple ,In your relevant directory run the following command

I was using axios so I used

npm i axios

Restart the server

npm start

This will work.

use a proxy property in your code it should work just fine

const https = require('https');
const request = require('request');
request({ 'url':' 'proxy':' }, function (error, response, body) { if (!error && response.statusCode == 200) { var data = body; console.log(data); } }
);

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

You Might Also Like