WhatBrokeToday
GTA 6FAQ
Bun

node:net: `server.listen(port)` with no host fails ("Failed to listen at ::") when IPv6 is unavailable; Node falls back to 0.0.0.0

medium

Is it fixed? Not yet.

Ongoing since Nov 19, 17:02 UTC. First reported Nov 19, 17:02 UTC.

What happened

In Bun versions 1.4.4 and later, `server.listen(port)` with no host fails with a "Failed to listen at ::" error on Linux environments where IPv6 is unavailable or disabled via kernel parameters or seccomp profiles, whereas Node.js successfully falls back to 0.0.0.0.

What caused it?

Under active investigation. No report has identified a root cause yet.

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on GitHub issue

    node:net: `server.listen(port)` with no host fails ("Failed to listen at ::") when IPv6 is unavailable; Node falls back to 0.0.0.0

    Source

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    node:net: `server.listen(port)` with no host fails ("Failed to listen at ::") when IPv6 is unavailable; Node falls back to 0.0.0.0(opens GitHub issue in a new tab)

    What version of Bun is running? 1.4.4+38afee6c8 (also 1.4.6-canary.1+ca7729d01) What platform is your computer? Linux 7.2.7-200.fc44.x86_64 x86_64 (in a Podman container, oven/bun:1.4.4 and oven/bun:canary) What steps can reproduce the bug? On a Linux where IPv6 sockets can't be made: booted with ipv6.disable=1, a kernel without IPv6, or, as here, a seccomp profile that makes socket(AF_INET6, ...) fail with EAFNOSUPPORT, as such a kernel does: no-ipv6.json: { "defaultAction": "SCMP_ACT_ALLOW",…

    by aalstes 0upvotes 1comments

FAQ

What happened in the Bun outage?

In Bun versions 1.4.4 and later, `server.listen(port)` with no host fails with a "Failed to listen at ::" error on Linux environments where IPv6 is unavailable or disabled via kernel parameters or seccomp profiles, whereas Node.js successfully falls back to 0.0.0.0.

What is affected by the Bun outage?

Bun (versions: 1.4.4+). Also affected at the same time: Linux.

When did the Bun outage start and end?

It started Nov 19, 17:02 UTC and is still ongoing (3 h 32 min so far). This page updates as it develops.

How do I get alerts for Bun?

Subscribe to the Bun RSS feed for every new Bun incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Bun is down. Bun feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.