ECONNREFUSED: connection refused — page 2

Nothing was listening at the address Claude Code dialled.

214 issues · 8 open · 206 resolved (96%) · first seen Mar 25, 2025

First response · network

What to do now

Most likely: A DNS, proxy, TLS or socket layer interrupted the connection.

  1. Check whether the same request works without the current VPN or corporate proxy.
  2. Verify DNS and certificate trust without disabling TLS verification.
  3. Capture the hostname and exact socket code before escalating.

These are conservative triage steps, not an official Anthropic fix. Use the issue and workaround evidence below before making a destructive configuration change.

Is this getting better or worse?

This class of problem is converging. 13 new reports in the last 90 days vs 75 in the 90 before — -83%. The open backlog peaked at 43 in 2026-04 and sits at 8 today.

0 11 22 32 43 2025-032025-092026-042026-10
2025-03 — First reports2026-04 — Peak backlog (43 open)

Derived by counting each matching issue from its creation date until it closed. First-party computation over the anthropics/claude-code tracker — the trend is not published anywhere upstream.

Which builds report this

188 of these reports name the Claude Code build they were running, spanning 83 releases. Heaviest reporters:

Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.

Do these get fixed?

Median time to close is 8 days across 206 closures. Of the 206 closures with a recorded reason, 11% were closed as completed and 184 as not-planned or duplicate. The most recent completed fix landed in 2026-10.

Workarounds reported by the community

18 of these issues post a workaround someone says worked. The highest-engagement ones:

[Bug] 1M context incorrectly requires extra usage on Max plan
…or charges. Actual Behavior Error is thrown blocking usage. Workaround of running is required, which also incorrectly labels the feature as "Billed as extra usage." Environment - Plan: Max - Model: claude-opus-4-6[1m] -…
Found in the description of #45390 · still open
OAuth token expired immediately after fresh login - cannot use Claude Code (blocking)
…to succeed, first prompt still returns 401 "token expired" Workaround attempted (unsuccessful): Exit Claude Code rm -rf ~/.claude (clear all credentials) Run claude Run /login Same failure occurs Claude Model Opus Is th…
Found in the description of #19078 · resolved
[Bug] Weekly usage reset time displayed incorrectly for Pro plan users
…gent: While our Support team is unable to manually reset or work around usage limits, you can learn about best practices here ( If you’ve hit a message limit, you’ll need to wait until the reset time, or you can consider…
Found in the thread of #51222 · resolved
[BUG] Connection-level errors (ECONNRESET, EPIPE, ETIMEDOUT) are never retried — immediate failure with zero recovery
…+ partial retry reimplementation is the core issue. Partial workaround: PostToolUseFailure hook to auto-retry You can't retry API calls from a hook, but you can detect connection-related failures and alert: Better workar…
Found in the thread of #37077 · resolved
[BUG] http hooks with json don't work.
…?" — with HTTP hooks failing to reach their endpoint. Their workaround was the same as yours: fall back to command hooks. HookLab works — but it runs on localhost. The HookLab project (a Phoenix LiveView dashboard) recei…
Found in the description of #30613 · resolved

Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.

Matching issues 101–200

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. ECONNRESET: socket hang up

    251 issues
  2. Self-signed certificate in certificate chain

    43 issues
  3. ETIMEDOUT: request timed out

    33 issues
  4. getaddrinfo ENOTFOUND (DNS lookup failed)

    59 issues
  5. EADDRINUSE: address already in use

    31 issues
  6. API Error 400 (invalid_request_error)

    2,649 issues