Request failed to proxy: ECONNREFUSED about local-ssl-proxy

[coffenbacher]

NODE_OPTIONS=--dns-result-order=ipv4first npx local-ssl-proxy -s 9000 -t 3000

is working for me 🎉 Those of you mentioning Node 17 reminded me of that breaking change to the network stack in that version, I have no idea why it would be an issue in this package but I was able to repro over and over on my machine at least.

[adxy]

For me downgrading to Node v14.18.2 from Node 17 solved this issue

[dawidjaniga]

Hi, I'm having error "Request failed to proxy: ECONNREFUSED" on Node 17.3
It works fine on 16.13.1

[cameronhunter]

I've released v2.0.1, which I've tested works on all LTS versions of node – I hope this resolves the issue.

[Legym]

Just wanted to make a quick update, but make sure you're running the commands for the source and target. I ran into where the source (local-ssl-proxy) was running, but the target (dev server on localhost) was not. I am using nextjs and just needed to run npm run dev along side local-ssl-proxy --source 3010 --target 3000 --cert localhost.pem --key localhost-key.pem

Im using node 16

[mpereira]

I ran into this and the cause was that I didn't specify a --hostname in the local-ssl-proxy command, since I wasn't using localhost.

[Toumash]

How do you get the error? What happens when you browse to this address using Google chrome? It should give you the "not safe" screen warning.
What is the platorm you are using? Any details on that? Im running windows

[mrlasers]

I am also having this issue running Node 17.8.0. Downgrading to 16.13.0 resolved it.

[leonardoResendeLima]

+1. Same problem here.

[avielmenter]

Can confirm, unfortunately. I am having the same issue.

[doerme]

+1

[francisrod01]

Sorry for my late reply. My notebook was in maintenance.

Sorry, I don't use Windows.

I tried again with a React app, and I got this output on Google Chrome.

[fcisio]

Hi, has anyone figured out the source of this issue?
It was working for me yesterday but now fails today (so I doubt that changing the version of node is the solution).

Upon restarting my computer, it now works.

So my guess is that it's an issue with the proxy not being killed properly at some point.
I'll need to test this theory next time I face this issue, but this command should technically work.

lsof -n -i4TCP:{YOUR_PORT}

[azhararmar]

I am having the same issue, when I try accessing the URL I get the error Request failed to proxy: ECONNREFUSED I have Node verion 17.2.0

[tayloraucoin]

This still happens to me on all the node versions listed so far.

[sebmellen]

Just a note for myself and anyone else who may be having this error, in my case I needed to explicitly set the PORT that my target app was running at.

[bel7aG]

Make sure that your application server is running on the target port.

eg. (local-ssl-proxy --source 3001 --target 3000) & next dev --port 3000