claude-code - 💡(How to fix) Fix [BUG] coworkd_upstream_failed connection_refused - persistent across 2 days on Mac [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45175Fetched 2026-04-09 08:11:32
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×4commented ×2

Error Message

API Error: 587 {"error":"coworkd_upstream_failed","category":"connection_refused","detail":"proxyconnect tcp: dial tcp 172.16.10.254:9096: connect: connection refused"} You can restart the conversation from an earlier message.

Code Example

API Error: 587 {"error":"coworkd_upstream_failed","category":"connection_refused","detail":"proxyconnect tcp: dial tcp 172.16.10.254:9096: connect: connection refused"}
You can restart the conversation from an earlier message.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Platform: macOS Claude Desktop Version: 1.1062.0 (b81bcd) 2026-04-06 Plan: Pro

Issue: Every Cowork task fails with the following error, consistently for 2 days:

API Error: 587 {"error":"coworkd_upstream_failed","category":"connection_refused","detail":"proxyconnect tcp: dial tcp 172.16.10.254:XXXX: connect: connection refused"}

The port number changes each time (9160, 9162, 9173, 9189, etc.) but the error is consistent.

Steps taken with no resolution:

  • Fully quit and restarted Claude Desktop multiple times
  • Logged out and logged back in
  • No VPN in use
  • Local IP is 192.168.1.x — no subnet conflict with 172.16.x.x range
  • Cleared Cowork cache via Terminal
  • Checked firewall — Claude Desktop not blocked
  • Latest version confirmed

Tasks will run for a short period then consistently hit this error mid-task. Regular Claude chat works fine. Only Cowork is affected.

This has been ongoing since April 7, 2026 and is completely blocking my workflow.

What Should Happen?

Tasks should be completed as prompted as per previous days of completed tasks

Error Messages/Logs

API Error: 587 {"error":"coworkd_upstream_failed","category":"connection_refused","detail":"proxyconnect tcp: dial tcp 172.16.10.254:9096: connect: connection refused"}
You can restart the conversation from an earlier message.

Steps to Reproduce

It is a task I have claude cowork doing

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Claude 1.1062.0 (b81bcd) 2026-04-06T21:20:28.000Z

Claude Code Version

Claude 1.1062.0 (b81bcd) 2026-04-06T21:20:28.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Happening for 2 days now

extent analysis

TL;DR

The issue can likely be mitigated by investigating and resolving the connection refusal to the 172.16.10.254 IP address on various ports, potentially related to a networking or proxy configuration issue.

Guidance

  • Investigate the network configuration and firewall settings to ensure that outgoing connections to 172.16.10.254 on various ports are allowed.
  • Check if there are any proxy settings configured in the system or application that might be causing the connection refusal.
  • Verify if the IP address 172.16.10.254 is reachable from the system running Claude Desktop using tools like ping or telnet.
  • Consider checking the system's DNS resolution and routing tables to ensure there are no issues with resolving the IP address.

Example

No specific code snippet can be provided without more context on the application's configuration and networking setup. However, a simple test using telnet could be:

telnet 172.16.10.254 9096

This can help verify if the connection to the specific IP and port is possible.

Notes

The issue seems to be related to a regression introduced in the latest version of Claude Desktop, as it worked previously. The fact that regular Claude chat works fine but Cowork tasks fail suggests a specific issue with the Cowork functionality or its networking requirements.

Recommendation

Apply workaround: Given the regression and the specific error related to connection refusal, it's reasonable to suspect a networking or configuration issue rather than a code problem within Claude Desktop itself. Therefore, applying a workaround related to networking configuration or proxy settings might resolve the issue until a fixed version is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING