[Bug] Claude Code fails with poor internet connection error if im not connected to corporate VPN
Resolved 💬 3 comments Opened Nov 19, 2025 by dejanstrancar Closed Nov 22, 2025
Bug Description
Claude Code does not want to work if im not connected to company VPN. Claude Desktop works fine with/without VPN. Ive tried direct API call on claude code API and works fine without vpn, just claude code client is saying "Unable to connect to API due to pooir internet connection.
Environment Info
- Platform: darwin
- Terminal: Apple_Terminal
- Version: 2.0.46
- Feedback ID:
Errors
[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/dejanstrancar/.local/share/claude/versions/2.0.46 (expected in multi-process scenarios)\n at aq0 (/$bunfs/root/claude:2532:1516)\n at P4A (/$bunfs/root/claude:2532:1194)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-19T08:15:35.159Z"},{"error":"Error: Connection error.\n at makeRequest (/$bunfs/root/claude:732:4547)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-19T08:15:36.458Z"},{"error":"Error: Request was aborted.\n at H (/$bunfs/root/claude:1787:3469)\n at abort (unknown)\n at GI (/$bunfs/root/claude:2679:63534)\n at <anonymous> (/$bunfs/root/claude:2663:3628)\n at <anonymous> (/$bunfs/root/claude:219:497)\n at <anonymous> (/$bunfs/root/claude:104:51118)\n at G (/$bunfs/root/claude:219:490)\n at emit (/$bunfs/root/claude:211:1363)\n at processInput (/$bunfs/root/claude:218:740)\n at flushIncomplete (/$bunfs/root/claude:218:564)","timestamp":"2025-11-19T08:16:01.743Z"},{"error":"Error\n at <anonymous> (/$bunfs/root/claude:46:51689)\n at <anonymous> (/$bunfs/root/claude:64:10217)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/claude:63:1146)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:248:22)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/claude:66:2147)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-19T08:17:17.261Z"}]This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗