[Bug] Anthropic API Error: Internal Server Error (500)
Status Fixed / completed
Maintainer reply ✓ Yes — ashwin-ant
Activity 9 comments · opened Nov 24, 2025 · closed Nov 24, 2025
💡 Likely answer: A maintainer (ashwin-ant, collaborator)
responded on this thread — see the highlighted reply below.
Bug Description
API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server
error"},"request_id":"req_011CVSzzd5u4VkQ94vmx5X6u"}
Environment Info
- Platform: darwin
- Terminal: Apple_Terminal
- Version: 2.0.50
- Feedback ID: 061e8ae5-0fb7-403d-90c3-8a3304735f8f
Errors
[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/singyu/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-24T03:52:41.099Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/singyu/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (unknown)\n at async Ex (unknown)\n at unknown\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-24T03:52:53.968Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/singyu/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-24T03:53:24.980Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/singyu/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-24T03:54:04.870Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/singyu/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-24T04:24:05.257Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/singyu/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-24T04:54:05.368Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/singyu/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-24T05:24:05.279Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/singyu/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-24T05:54:05.214Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/singyu/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-24T06:24:05.165Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/singyu/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/r
Note: Error logs were truncated.
9 Comments
me too
+1
edit:
tried running on resuming the context and on the fresh session, no luck:
<img width="744" height="46" alt="Image" src="https://github.com/user-attachments/assets/28de2e6d-2a0b-499c-8b9b-450fe541418c" />
platform: Mac 26.1
terminal: iTerm 3.6.6
claude code version: 2.0.50 (latest)
Same, for me and team. It's now completely down.
<img width="1581" height="667" alt="Image" src="https://github.com/user-attachments/assets/a95e86a1-c1c7-4517-8821-4f1f6e8a5ea8" />
+1 it is down, platform independent
$ claude update
Current version: 2.0.50
Checking for updates...
Claude Code is up to date (2.0.50)
<img width="925" height="138" alt="Image" src="https://github.com/user-attachments/assets/ed031ea8-4c14-46ee-b45a-3b5fb91ed727" />
It's working for me now! 🎉
<img width="571" height="779" alt="Image" src="https://github.com/user-attachments/assets/120ff1ec-d073-47c0-9cf9-e172a53bed1f" />
Can others confirm that the issue is resolved for them? We believe we've resolved the issue, but want to confirm.
It's now back online for me.
It's back again, please fix this. I'm paying 200 USD per month...
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.