ECONNREFUSED error when using localhost with proxy endpoints

[Lukenickerson]

I'm running and testing a local proxy server meant to function as an API gateway. It is built in nodejs express v4.18.2 and http-proxy-middleware v2.0.6, and is currently as simple as possible.

• One path '/hello' returns "Hello" text.
• Another path '/auth' is set up as a proxy with a target URL out on the internet (a server I manage) and changeOrigin set to true.
• Another path '/dog' is also a proxy with a target to this public API: https://dog.ceo/api/breeds/image/random

When hitting the proxied auth endpoint I'm seeing this error:

Error invoking remote method 'send-http-request': Error: connect ECONNREFUSED ::1:443

Related to https://github.com/usebruno/bruno/issues/124 but obviously different.

Details

• Windows 10
• Bruno desktop app v1.6.1

Tests

• ✅✅ When requesting a URL in Bruno that is not proxied, e.g., http://localhost:3201/hello just returns text, I get the response expected. This also works as expected in Postman and the browser (Chrome 120.0.6099.225).
• ❌ When requesting a URL in Bruno that is proxied, e.g., http://localhost:3201/auth I get the error above.
• ✅ When requesting the same '/auth' proxied URL in either Postman or the browser, I get the response I would expect (which in my case is a JSON object from the proxied API saying the authentication didn't work because I'm doing a GET and not sending any data).
• ✅✅ When requesting "http://localhost:3201/dog" in either Bruno, Postman, or the browser, they all work as expected.

Since the "dog" endpoint works, but "auth" does not, I admit there is likely something unusual happening with my target server. But it is disconcerting that Bruno acts different from Postman and the browser.

[martinsefcik]

@Lukenickerson Do you have http_proxy or https_proxy defined as environment variable in Windows?

[Lukenickerson]

@martinsefcik - No, I do not. Are they required by Bruno (but not Postman)?

[clemarc]

Experiencing the same issue here, when running our application locally we have a WebPack server for our react application and proxying

• graphql gateway
• custom identity provider
• Other applications

From our pre-script we are trying to generate an OAuth bearer token from the pre-request script but it fails if we hit the webpack proxy but works if

• http://localhost:4200/idp/token fails
• http://localhost:4300/idp/token works

For now we are bypassing the proxy and overall I don't think it is a big issue for us. The webpack proxy is mostly here to share a session cookie when logging in app (cookies are not shared if the port is different)

Reading the docs I haven't really found a way to try to debug and understand the issue more but let me know if you need anything that can help debug.

Details

macOS Sonoma (14.2.1 Bruno desktop app v1.6.1

[Aarbel]

this may be useful, a lot of people have this ECONNREFUSED error with proxies on mac (even with ngrok)

[gajakannan]

Windows 11, just installed bru cli and have the bruno ui for few months

I am getting same error in cli

Interestingly, the same route works from bruno ui

[gajakannan]

Am I the only one that have the above issue that bruno tests work from gui but fails from cli... Am I missing something?

[jkwold]

On Windows 10 running with Bruno 1.28 and a GET http://localhost:someport/... in bruno itself that works yet as noted cmdline bru 1.26.2

bru run somebru.bru --env "myenv"
Running Request

somebru (connect ECONNREFUSED ::1:8080)

hacking the GET URL so instead of localhost it specifically calls out IPv4 127.0.0.1 then that works both in Bruno and cmdline bru

looks like localhost is interpreted as the fine IPv6 ::1 in bru and not so in Bruno, tho haven't tried a procmon or similar to see if that's really true