Cairn

BlueBubbles webhook localhost vs 127.0.0.1 IPv4/IPv6 issue

NousResearch/hermes-agent · cluster 8512 · gateway

Data as of

5 open items. Fix attempted, not merged.

The short answer

2open issues
3open PRs
10items grouped
Known?
Yes. 10 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 5 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 3 PRs.

These issues and PRs concern a problem where webhook URLs using 'localhost' resolve to IPv6 instead of IPv4, breaking BlueBubbles webhook delivery. The work focuses on preserving explicit 127.0.0.1 addresses and adjusting bind behavior to ensure reachability.

Open issues2

  • Issue#8512[Bug]: BlueBubbles webhook fails on macOS due to IPv6 localhost resolution
  • Issue#45308BlueBubbles `_webhook_url` normalizes 127.0.0.1 → localhost, breaking IPv4 webhook delivery (inbound attachments dropped)

Open PRs3

  • PR#8263fix(bluebubbles): use 127.0.0.1 instead of localhost for webhook URL
  • PR#33853fix(bluebubbles): use 127.0.0.1 instead of localhost in webhook URL (fixes #8512)
  • PR#119187fix(bluebubbles): register the IPv4 loopback literal, not "localhost"

5 PRs closed without merging

From the close comments: superseded by another PR 3 · duplicate 1 · other 1

  • #8589 fix(bluebubbles): preserve a reachable local webhook host · superseded by another PR → #8263
  • #45318 fix(bluebubbles): preserve 127.0.0.1 in webhook URL to fix IPv4 delivery · duplicate → #8263
  • #45381 fix(gateway): preserve explicit 127.0.0.1 in BlueBubbles webhook URL (#45308) · superseded by another PR → #8263, #45308
  • #69574 fix(bluebubbles): preserve 127.0.0.1 in webhook URL on macOS · superseded by another PR → #69574, #8263
  • #69593 fix(bluebubbles): use 127.0.0.1 in webhook URL + migrate stale localhost registrations · other
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.21: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Closed issues
0
Attempts
5 PRs closed without merging

For your agent

The same facts, typed.

cluster/8512.json
cluster/8512.md