API Error (Internet connection is unreliable)
Status Closed — not planned
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 11 comments · opened Sep 22, 2025 · closed Feb 14, 2026
Bug Description
I am unable to use Claude Code since this morning. Any prompt returns the following error (10 attempts), then aborts the request:
API Error (Internet connection is unreliable)
All other internet services are working correctly from my workstation, including Copilot and the Jetbrains AI assistant.
Environment Info
- Platform: linux
- Terminal: gnome-terminal
- Version: 1.0.120
- Feedback ID:
Errors
[{"error":"AggregateError\n at cp.from (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:713:39831)\n at dK.J1 (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:716:10122)\n at dK.emit (node:events:530:35)\n at dK.emit (node:domain:489:12)\n at Op1.<computed> (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:25:1161)\n at ClientRequest.emit (node:events:518:28)\n at ClientRequest.emit (node:domain:489:12)\n at emitErrorEvent (node:_http_client:103:11)\n at TLSSocket.socketErrorListener (node:_http_client:506:5)\n at TLSSocket.emit (node:events:518:28)\n at OQ1.request (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:718:2088)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async iv4 (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1013:19844)\n at async Z (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1013:1186)\n at async av4 (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1013:20095)\n at async rv4 (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1013:21062)","timestamp":"2025-09-22T22:17:09.419Z"},{"error":"Error: Operation aborted\n at AbortSignal.C (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1919:19544)\n at [nodejs.internal.kHybridDispatch] (node:internal/event_target:816:20)\n at AbortSignal.dispatchEvent (node:internal/event_target:751:26)\n at runAbort (node:internal/abort_controller:410:10)\n at abortSignal (node:internal/abort_controller:396:3)\n at AbortController.abort (node:internal/abort_controller:428:5)\n at pA (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:3421:34870)\n at file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:3419:3200\n at file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:822:1004\n at A.Q.batchedUpdates (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:86:51080)","timestamp":"2025-09-22T22:19:20.035Z"},{"error":"Error: Connection error.\n at IP.makeRequest (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1009:4466)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)","timestamp":"2025-09-22T22:20:14.731Z"},{"error":"Error: Connection error.\n at IP.makeRequest (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1009:4466)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)","timestamp":"2025-09-22T22:21:14.488Z"},{"error":"SyntaxError: Unexpected token 'A', \"API Error:\"... is not valid JSON\n at JSON.parse (<anonymous>)\n at file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:733:9932\n at Q (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:713:13288)\n at N9B (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1710:1805)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)","timestamp":"2025-09-22T22:21:14.496Z"},{"error":"AggregateError\n at cp.from (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:713:39831)\n at dK.J1 (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:716:10122)\n at dK.emit (node:events:518:28)\n at dK.emit (node:domain:489:12)\n at Op1.<computed> (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:25:1161)\n at ClientRequest.emit (node:events:518:28)\n at ClientRequest.emit (node:domain:489:12)\n at emitErrorEvent (node:_http_client:103:11)\n at TLSSocket.socketErrorListener (node:_http_client:506:5)\n at TLSSocket.emit (node:events:518:28)\n at OQ1.request (file:///home/zak/.nvm/versions/node/v22.11.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:718:2088)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n Note: Error logs were truncated.
11 Comments
My experience is that when Claude fixed Claude App and API connectivity errors, certain users are required to re-anthentic their account but the API error didn't prompt that. The workaround is to run
claude /loginclaude /logindid not help in my case. The Web browser page is opened, I seeYou’re all set up for Claude Code.
You can now close this window.
Claude Code though outputs an error:
OAuth error:
Press Enter to retry.
Did you figure this out? I have one user that is getting a similar issue today, but it could be related to our zero-trust client (Zscaler):
I just started experiencing this yesterday. If I was to try a
/login, eventually I'll see:OAuth error: unable to get local issuer certificateWe also use Zscaler.
workaround is Use a VPN (example US servers), then run claude /login and try again. work for me
Normally, it's due to proxy or vpn,.check your environment variables or system internet settings, whether there is a inappropriate proxy.
There is another way to check your internet “ping api.anthropic.com” paste this in the terminal, here is a correct result:
Pinging api.anthropic.com [2607:6bc0::10] with 32 bytes of data: Reply from 2607:6bc0::10: time=67ms Reply from 2607:6bc0::10: time=69ms Reply from 2607:6bc0::10: time=73ms Reply from 2607:6bc0::10: time=69ms Ping statistics for 2607:6bc0::10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 67ms, Maximum = 73ms, Average = 69ms
if not, you need to fix your internet.
I was able to resolve the issue by configuring Node.js to trust the Zscaler certificate authority. This was accomplished by setting the NODE_EXTRA_CA_CERTS environment variable to reference the certificate file:
export NODE_EXTRA_CA_CERTS=~/path/to/cert/ZscalerCertificate.crtWorked for me!
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.