Connection refused on localhost

Question

I am trying to work on my nodejs and reactjs app at school but everytime I run the server, I get an error with localhost:PORT/net::ERR_CONNECTION_REFUSED

Is the wifi refusing the connection on localhost?

PS: The react side renders correctly

Are you sure that your application is running? and in the port, you're setting in the URL ? — Rebai Ahmed, Nov 19 '19 at 08:10

score 16 · Accepted Answer · answered Nov 19 '19 at 08:06

16

Try changing the url from localhost to 127.0.0.1 . If it works, then it means your environment is not resolving localhost to 127.0.0.1

Or Try with changing the PORT Number

answered Nov 19 '19 at 08:06

Maulik Sakhida

471
4
15

5

If you are on a mac, the issue could be you have two entries in the `/etc/hosts` file for localhost. When I encountered this issue, I had `127.0.0.1 localhost` and `::1 localhost` in my `/etc/hosts` file. Remove the `::1 localhost` line resolved the issue. – Alexander Aavang Oct 20 '22 at 13:28
1

@AlexanderAavang You just saved me big time! This totally escaped me for hours. Here I am swimming around in old commits trying to catch a ghost. – Kalnode Mar 07 '23 at 04:03
Does anybody know why Node isn't able to resolve the DNS name? Secondly, would this happen on the actual environment (dev on Azure)? Thank you for saving the day. – Rikki Aug 16 '23 at 05:31

score 15 · Answer 2 · answered Jul 26 '21 at 12:43

15

If you're using WSL (linux on windows), restart its service LxssManager Servie (run services.msc) and try again.

answered Jul 26 '21 at 12:43

Olavo André Parno

197
1
7

1

- Open your powershell with admin permissions; ```wsl --shutdown``` - Run wsl again to turn on: ```wsl``` – Thiago Tibau Jan 02 '22 at 13:07

score 6 · Answer 3 · answered Mar 29 '21 at 15:47

6

For those of you that the approved solution didn't work for (changing localhost to 127.0.0.1) I was able to fix this just by restarting my computer. Not sure what caused the issue but the day before today my app was working fine and then today I got hit with this error. Restarting fixed the issue.

answered Mar 29 '21 at 15:47

AJRohrer

925
9
9

1

Yep I second this. I am using a window 10 devices and running npm through WSL and the code was working fine earlier in the day. When I came back, it say localhost refused to connect. A restart would definately help. – hoan duc Jun 04 '21 at 01:28

score 2 · Answer 4 · edited Oct 20 '22 at 18:04

2

I was also facing this problem on mac m1 from last 2 days, so finally i ended fixing the issue by :-

Run 'npm start' from default shell(/bin/bash) on vs code.
You can also try to update the node version.
You may need to change the port for application only if some other application is running on default port(3000)

edited Oct 20 '22 at 18:04

Ryan M

18,333
31
67
74

answered Mar 11 '21 at 11:21

Wasit Shafi

854
1
9
15

Lucky_hunter · Answer 5 · 2022-03-16T10:35:19.477

2

In my case I have an error with require in setupProxy.js

edited Mar 16 '22 at 10:35

answered Mar 16 '22 at 10:11

Lucky_hunter

486
1
5
10

How did you diagnose the issue? – huzi8t9 Jun 09 '22 at 13:58
1

@huzi8t9 I remove `'http-proxy-middleware'` from `setupProxy.js` and it works. Then I realized that I need to use `require` instead of `import`. – Lucky_hunter Jun 11 '22 at 13:38

score 1 · Answer 6 · edited Dec 23 '21 at 08:29

1

In my case, deleting the node_modules and then reinstalling using npm install worked.

edited Dec 23 '21 at 08:29

Mohit Kushwaha

1,003
1
10
15

answered Dec 22 '21 at 05:03

Adnan GM

11
2

score 1 · Answer 7 · answered Jan 23 '22 at 03:46

1

In my case, I resolved the issue using "npm start" command again in terminal of vs code and it works.

answered Jan 23 '22 at 03:46

Subhash Karthik

11
1

score 0 · Answer 8 · answered Dec 09 '22 at 14:32

In my case I had made changes to the setupProxy.js that caused the problem. Try reverting back to something that is working, such as:

const { createProxyMiddleware } = require('http-proxy-middleware');

module.exports = function(app) {
  app.use(
    '/api',
    createProxyMiddleware({
      target: 'http://localhost:5000',
      changeOrigin: true,
    })
  );
};

score -2 · Answer 9 · answered Feb 16 '22 at 05:31

-2

Rebooting the system (linux) worked for me. Consider rebooting first.

answered Feb 16 '22 at 05:31

sai_varshittha

193
1
12

daljeet singh harsh · Answer 10 · 2020-05-09T06:10:49.633

-6

the problem of "localhost refused to connect." is occur because of command prompt that you closed so you must keep open your command prompt after hit "npm start" command till you work in "App.JS" file.

i'm sure this will work 100%.

edited May 09 '20 at 06:10

answered May 09 '20 at 06:00

daljeet singh harsh

1
3

Connection refused on localhost

10 Answers10

Linked