ConnectionRefused when `fetch()` is localhost #1425

Electroid · 2022-10-30T01:21:39Z

What version of Bun is running?

0.2.2

What platform is your computer?

Darwin 21.5.0 Darwin Kernel Version 21.5.0: Tue Apr 26 20:57:23 PDT 2022; root:xnu-8020.121.3~2/RELEASE_ARM64_T8110 arm64 arm

What steps can reproduce the bug?

export default {
  port: 4281,
  fetch(request) {
    return new Response("Ok");
  }
}

console.log(await fetch("http://localhost:4281/hello"))

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

No response

What do you see instead?

The above code fails with the error:

ConnectionRefused: fetch() failed
 path: "http://localhost:4281/hello"

Additional information

No response

Jarred-Sumner · 2022-10-30T01:22:55Z

I used to hardcode localhost to 127.0.0.1 as a workaround, but it's not great since technically the OS could have rewritten localhost to anything else

@uNetworking do you have any ideas?

Jarred-Sumner · 2023-07-31T13:24:07Z

Fixed in Bun v0.7.1

rubenfiszel · 2023-08-09T08:25:53Z

Still have this issue on 0.7.3 for localhost:8000

Voldemat · 2023-09-09T08:33:08Z

On 1.0.0 same error

Carter-Apas · 2023-09-11T01:22:35Z

I have the same error on 1.0.0

masnormen · 2023-09-12T02:41:55Z

Could this be related with my Next.js dev with bun run --bun next dev? It says there's something regarding sockets, which could be used by Next for HMR, followed by a ConnectionRefused.

dyld[35100]: missing symbol called
ConnectionClosed: The socket connection was closed unexpectedly. For more information, pass `verbose: true` in the second argument to fetch()
 path: "http://localhost:51789/"

ConnectionRefused: Unable to connect. Is the computer able to access the url?
 path: "http://localhost:51789/"

BobDenar1212 · 2023-09-12T12:46:20Z

I have the same issue with the following:
wsl2 Ubuntu-22.04 LTS bun-1.0.0
Create nextjs app with :
bunx create-next-app test --ts --tailwind --eslint --app --src-dir --use-bun --import-alias "@/*"
Run nextjs app with:
bun next dev

Gives the output:

$ bun next dev
- ready started server on localhost:3000, url: http://localhost:3000
- event compiled client and server successfully in 209 ms (20 modules)
- wait compiling...
- event compiled client and server successfully in 38 ms (20 modules)
- wait compiling /page (client and server)...
- event compiled client and server successfully in 2.2s (426 modules)
- wait compiling...
- event compiled successfully in 174 ms (235 modules)
ConnectionClosed: The socket connection was closed unexpectedly. For more information, pass `verbose: true` in the second argument to fetch()
 path: "http://localhost:43275/"

- wait compiling /_error (client and server)...
ConnectionRefused: Unable to connect. Is the computer able to access the url?
 path: "http://localhost:43275/favicon.ico"

EDIT 2023-10-09
I gave a try to latest bun version 1.0.4, and it is working fine

markstos · 2023-09-22T01:42:07Z

Using 127.0.0.1 works as a workaround.

paperdave · 2023-09-27T11:15:30Z

Edit: this is incorrect, the server will begin on the tick after it has started

the code snippet in the issue is technically wrong.

export default {
  port: 4281,
  fetch(request) {
    return new Response("Ok");
  }
}

console.log(await fetch("http://localhost:4281/hello"))

when you use export default to start a server, it will only start after the module is finished evaluating, so you cannot top-level-await a fetch here.

Bun.serve({
  port: 4281,
  fetch(request) {
    return new Response("Ok");
  },
});

console.log(await fetch("http://localhost:4281"));

This works for me on Linux and MacOS. Can someone test this on WSL?

markstos · 2023-09-27T20:16:58Z

I wonder if the issue is that Bun is defaulting to an IPv6 connection for localhost, but there's no entry for localhost for IPv6 in /etc/hosts.

You could try adding this to /etc/hosts if there's not something like it there:

::1             localhost

kszpakowski · 2023-09-27T21:07:11Z

@markstos I already have /etc/hosts entry for IPv6 localhost and unfortunately it still does not work.

nCrafts · 2023-10-05T06:39:22Z

Having the same issue and can’t really use Bun on any of my projects because of this. Is there something I can do to help debug this?

masnormen · 2023-10-05T06:57:14Z

I think this has been solved with 1.0.4, at least for me. Give it a try

nCrafts · 2023-10-05T07:47:37Z

Unfortunately not for me. It says, ConnectionRefused: Unable to connect. Is the computer able to access the url?

markstos · 2023-10-06T14:19:42Z

@nCrafts You can checkout the Bun project and review the related test coverage and then add a new failing test which triggers this failure:

https://github.com/oven-sh/bun/blob/main/test/js/web/fetch/fetch.test.ts

There are already some tests for fetch() with localhost, including some with IPv6, so you'll to figure what specifically is triggering this failure.

danny-avila · 2023-10-10T13:09:50Z

In my case, it seems to happen intermittently when the express res object closes res.on('close', ...)

Schrammel · 2023-11-10T14:32:21Z

Related issue on 1.0.11

on browser it works all time
on bun it works sometimes

  console.log("fetching projects");
  const request = await fetch("https://git.syonet.com/api/v4/projects", {
    headers: {
      "Private-Token": "< my private token >",
    },
  });
  const projects = await request.json();
  console.table(projects);

output:

ConnectionRefused: Unable to connect. Is the computer able to access the url?
 path: "https://git.syonet.com/api/v4/projects"

mathiasrw · 2023-11-26T09:43:45Z

Same problem on mac m1 cpu.

Took me ages to identify that this line works in Node but not in Bun.

prantlf · 2023-12-21T16:57:33Z

I can confirm the problem with bun 0.1.18. But executing the same .js script containing await fetch('http://localhost'... with node works.

VigilioYonatan · 2024-02-18T07:51:36Z

any update?

jameshfisher · 2024-02-19T09:49:07Z

Still broken on 1.0.27.

Example of node connecting just fine:

$ node
Welcome to Node.js v20.10.0.
Type ".help" for more information.
> const response = await fetch("http://localhost:11434/api/chat")
undefined
> await response.text()
'404 page not found'
>

bun repl equivalent fails with ConnectionRefused: Unable to connect:

$ bun repl
Welcome to Bun v1.0.27
Type ".help" for more information.
[!] Please note that the REPL implementation is still experimental!
    Don't consider it to be representative of the stability or behavior of Bun overall.
> const response = await fetch("http://localhost:11434/api/chat")
ConnectionRefused: Unable to connect. Is the computer able to access the url?
 path: "http://localhost:11434/api/chat"

>

$ bun --version
1.0.27

jameshfisher · 2024-02-19T09:52:08Z

Can confirm replacing localhost with 127.0.0.1 works. Although of course this is not a general workaround

Iuriiiii · 2024-02-21T21:17:56Z

Make requests to http://[::1]:3000/ worked for me.

Notes:
I'm using Windows, Bun is executing on WSL.

didier · 2024-03-21T11:47:25Z

Still happening on 1.0.33.

ArthurTimofey · 2024-04-02T17:16:46Z

Still happening 1.1.0 M1 Pro :(

ArthurTimofey · 2024-04-02T17:18:10Z

Still happening 1.1.0 M1 Pro :(

zpix1 · 2024-04-05T16:45:25Z

Same on 1.1.1:

ConnectionRefused: Unable to connect. Is the computer able to access the url?
 path: "http://localhost:11434/api/generate"

Fixed by replacing localhost with 127.0.0.1

iHaiduk · 2024-04-10T17:52:29Z

Same on 1.1.x:

ConnectionRefused: Unable to connect. Is the computer able to access the url?
 path: "http://logs.eu-central-1.amazonaws.com/"

lukewlms · 2024-04-15T09:36:07Z

Oh wow. Connecting to localhost is very common, I spent close to an hour trying to debug this and confused about why I could GET a public URL but not localhost. Seems like this would be a high priority to fix. curl and the browser can connect to localhost, bun should be able to also. (I'm on latest, v1.1.3)

omarpando · 2024-04-20T01:47:10Z

Still happening.

7heMech · 2024-05-10T22:53:23Z

Happens on 127.0.0.1 as well

ilya-tkachov · 2024-05-14T17:16:53Z

Used the latest version 1.1.8 on M3 Pro and got this issue but only when trying to use a proxy in nextjs between two apps. Had to downgrade to 1.0.35 and it worked like a charm.

7heMech · 2024-05-14T17:46:10Z

Used the latest version 1.1.8 on M3 Pro and got this issue but only when trying to use a proxy in nextjs between two apps. Had to downgrade to 1.0.35 and it worked like a charm.

@Jarred-Sumner maybe you can check this out?

schulzf · 2024-05-19T06:02:36Z

is there a temporary workaround for this?

We've been experiencing this issue in production (under v1.1.8), the server randomly fails to resolve url and throws Unable to connect. Is the computer able to access the url?

Jarred-Sumner · 2024-05-19T06:19:29Z

@schulzf if you can use 127.0.0.1 or 0.0.0.0 as the hostname that should workaround this. Or otherwise, if you can disable IPv6. The problem is that localhost often resolves to both IPv6 and IPv4, but the server may only be listening on IPv4.

schulzf · 2024-05-19T06:29:47Z

@Jarred-Sumner in our case is a not localhost but a live url (and it doesn't support ipv6).
By disabling ipv6 the server would become ipv4 only for inbound as well, which wouldn't be the best...

Is there a way to disable ipv6 in bun? (we're running under Cloud Run, we can't access the underlying system configuration)

Edit:

Will try using axios with custom http agent

    import https from 'https';

    const agent = new https.Agent({ family: 4 });

    const client = axios.create({
      ...axios.defaults.transformRequest,
      ...axios.defaults.transformResponse,
      httpAgent: agent,
    });

mathiasrw · 2024-05-22T02:35:17Z

I can confirm that this is now working as expected with bun v1.1.9

Nice work @teamBun

#bunUp

Jarred-Sumner · 2024-05-22T02:56:12Z

Fixed in Bun v1.1.9

rogercbe · 2024-06-10T14:16:07Z

I am still having the same problem on Bun v.1.1.12 using localstack and trying to upload an image to s3

AWS_ENDPOINT=http://localhost:4566

Error:

ConnectionRefused: Unable to connect. Is the computer able to access the url?
 path: "http://my-buckett.localhost:4566/3354167639216915979?uploads="

As comented in the thread, changing it to 0.0.0.0 or 127.0.0.1 makes it work, but not ideal

stewones · 2024-06-22T22:34:19Z

not sure what I'm doing wrong but I can't seem to make bun fetch, neither using 0.0.0.0 or 127.0.0.1. tried everything spoken in this thread so far 🙄

stewones · 2024-06-23T00:15:41Z

holy moly, I figured out my problem. the issue is that I needed to fetch between containers, so nothing worked until I tried host.docker.internal, which did the trick. so yeah, I can confirm fetch on Bun 1.1.15 works 🎉

garraflavatra · 2024-07-22T11:16:36Z

Has this been tested with local TLS (Caddy server) as well? I am able to visit this URL using cURL but not with Bun.

> await fetch('https://test.localhost/api/v2/portal/funnels/1/')
ConnectionRefused: Unable to connect. Is the computer able to access the url?
 path: "https://test.localhost/api/v2/portal/funnels/1/"

garraflavatra · 2024-07-22T11:24:55Z

TLS turns out not to be the issue... instead, localhost subdomains (test.localhost) are not handled correctly.

msamia · 2024-07-28T15:24:08Z

Hello, if for some reason when you try to access a registry file the connection fails, it gives an error of connection refused and not installed. Connection errors will not be recovered. The only way out in this case is to persist. This error is more likely to be detected if the json file that tries to access and fails is different in each attempt, especially if many components are installed at once.

MichaelYuhe · 2024-07-30T06:10:30Z

Still happening at v1.1.21

mathiasrw · 2024-07-31T06:34:05Z

@MichaelYuhe Please fill out a new issue referencing this one and providing information on how to replicate and the versions of bun and OS.

lsyuanyuan · 2024-08-03T02:47:03Z

I cannot determine whether the issue is with the server or with Bun, as I have encountered the same problem when using other URLs. I am using a URL similar to http://oa.xxxx.com, and I am in a production environment.

Error message: ConnectionRefused: Unable to connect. Is the computer able to access the URL?
Path: "http://oa.xxxx.com/"

My service information:

Linux localhost.localdomain 4.18.0-348.7.1.el8_5.x86_64 #1 SMP Wed Dec 22 13:25:12 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

bun -v 1.1.21

7heMech · 2024-08-03T08:38:45Z

I cannot determine whether the issue is with the server or with Bun, as I have encountered the same problem when using other URLs. I am using a URL similar to http://oa.xxxx.com, and I am in a production environment.

Error message: ConnectionRefused: Unable to connect. Is the computer able to access the URL?
Path: "http://oa.xxxx.com/"

My service information:

Linux localhost.localdomain 4.18.0-348.7.1.el8_5.x86_64 #1 SMP Wed Dec 22 13:25:12 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

bun -v 1.1.21

If you don't provide the exact url or another url at which this happens we can't help.

lsyuanyuan · 2024-08-05T02:16:34Z

I cannot determine whether the issue is with the server or with Bun, as I have encountered the same problem when using other URLs. I am using a URL similar to http://oa.xxxx.com,和I am in a production environment.

Error message: ConnectionRefused: Unable to connect. Is the computer able to access the URL?
Path: "http://oa.xxxx.com/"

My service information:

Linux localhost.localdomain 4.18.0-348.7.1.el8_5.x86_64 #1 SMP Wed 12月22日 13:25:12 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

bun -v 1.1.21

If you don't provide the exact url or another url at which this happens we can't help.

I'm sorry, I should have considered that it might be a server issue, because normally there wouldn't be any mistakes. Thank you!

Jarred-Sumner · 2024-08-05T02:18:28Z

If you're continuing to run into an issue like this, please open a new issue with a complete reproduction

Electroid added the bug Something isn't working label Oct 30, 2022

Jarred-Sumner closed this as completed Jul 31, 2023

Electroid reopened this Sep 11, 2023

Electroid mentioned this issue Oct 26, 2023

ConnectionRefused: http://127.0.0.1 on macOS #2802

Closed

Electroid mentioned this issue Nov 4, 2023

Bun does not understand "localhost" in fetch #6885

Closed

Electroid mentioned this issue Nov 16, 2023

Bun TCP Sockets refuse to connect with hostname as "localhost" #7158

Closed

kevincobain2000 mentioned this issue Jan 7, 2024

--compile TypeError: Argument must be a file URL on a new Sveltekit #5178

Closed

Jarred-Sumner mentioned this issue May 16, 2024

2 step plan to fix most DNS-related issues in Bun #10731

Closed

Jarred-Sumner closed this as completed May 22, 2024

oven-sh locked as resolved and limited conversation to collaborators Aug 5, 2024

ConnectionRefused when fetch() is localhost #1425

ConnectionRefused when fetch() is localhost #1425

Comments

Electroid commented Oct 30, 2022

What version of Bun is running?

What platform is your computer?

What steps can reproduce the bug?

How often does it reproduce? Is there a required condition?

What is the expected behavior?

What do you see instead?

Additional information

Jarred-Sumner commented Oct 30, 2022

Jarred-Sumner commented Jul 31, 2023

rubenfiszel commented Aug 9, 2023

Voldemat commented Sep 9, 2023

Carter-Apas commented Sep 11, 2023

masnormen commented Sep 12, 2023

BobDenar1212 commented Sep 12, 2023 • edited Loading

markstos commented Sep 22, 2023

paperdave commented Sep 27, 2023 • edited by Jarred-Sumner Loading

markstos commented Sep 27, 2023

kszpakowski commented Sep 27, 2023

nCrafts commented Oct 5, 2023

masnormen commented Oct 5, 2023

nCrafts commented Oct 5, 2023

markstos commented Oct 6, 2023

danny-avila commented Oct 10, 2023

Schrammel commented Nov 10, 2023 • edited Loading

mathiasrw commented Nov 26, 2023

prantlf commented Dec 21, 2023

VigilioYonatan commented Feb 18, 2024

jameshfisher commented Feb 19, 2024

jameshfisher commented Feb 19, 2024

Iuriiiii commented Feb 21, 2024 • edited Loading

didier commented Mar 21, 2024

ArthurTimofey commented Apr 2, 2024

ArthurTimofey commented Apr 2, 2024

zpix1 commented Apr 5, 2024 • edited Loading

iHaiduk commented Apr 10, 2024

lukewlms commented Apr 15, 2024 • edited Loading

omarpando commented Apr 20, 2024

7heMech commented May 10, 2024

ilya-tkachov commented May 14, 2024 • edited Loading

7heMech commented May 14, 2024

schulzf commented May 19, 2024 • edited Loading

Jarred-Sumner commented May 19, 2024

schulzf commented May 19, 2024 • edited Loading

mathiasrw commented May 22, 2024

Jarred-Sumner commented May 22, 2024

rogercbe commented Jun 10, 2024 • edited Loading

stewones commented Jun 22, 2024

stewones commented Jun 23, 2024

garraflavatra commented Jul 22, 2024

garraflavatra commented Jul 22, 2024

msamia commented Jul 28, 2024

MichaelYuhe commented Jul 30, 2024

mathiasrw commented Jul 31, 2024

lsyuanyuan commented Aug 3, 2024

7heMech commented Aug 3, 2024

lsyuanyuan commented Aug 5, 2024

Jarred-Sumner commented Aug 5, 2024 • edited Loading

ConnectionRefused when `fetch()` is localhost #1425

ConnectionRefused when `fetch()` is localhost #1425

BobDenar1212 commented Sep 12, 2023 •

edited

Loading

paperdave commented Sep 27, 2023 •

edited by Jarred-Sumner

Loading

Schrammel commented Nov 10, 2023 •

edited

Loading

Iuriiiii commented Feb 21, 2024 •

edited

Loading

zpix1 commented Apr 5, 2024 •

edited

Loading

lukewlms commented Apr 15, 2024 •

edited

Loading

ilya-tkachov commented May 14, 2024 •

edited

Loading

schulzf commented May 19, 2024 •

edited

Loading

schulzf commented May 19, 2024 •

edited

Loading

rogercbe commented Jun 10, 2024 •

edited

Loading

Jarred-Sumner commented Aug 5, 2024 •

edited

Loading