[BUG] Request timed out. Check your internet connection and proxy settings
Status Fixed / completed
Reported on v2.1.6
Maintainer reply None cached
Activity 7 comments · opened Jan 13, 2026 · closed Jan 13, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Plan was created fine but after a few modified files, I continuously get Request Timeout and 10 failed attempts. Repeated attempts to open new terminal and resume result in the same error
What Should Happen?
Claude Code should continue implementing the plan as designed. /resume takes longer than it should to recall past conversations
Error Messages/Logs
'API Error: Connection error'Steps to Reproduce
- /resume
- <select conversation>
- confirm where we were in plan implementation
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.6
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
7 Comments
resume the new feature set that was in motion prior to API connection test
● Resuming the reporting feature implementation. The models are created and __init__.py is updated. Let me continue with the Alembic migration.
● Search(pattern: "**/alembic/versions/*.py")
⎿ Found 15 files (ctrl+o to expand)
⎿ API Error: Connection error.
✻ Baked for 3m 24s
❯ resume
⎿ Interrupted · What should Claude do instead?
❯ resume creating the feature as planned
⎿ Request timed out. Check your internet connection and proxy settings
Retrying in 13 seconds… (attempt 6/10)
I'm getting the same issue. Just started about 40 minutes ago. I'm working in WSL. I restarted wsl with wsl --shutdown and made sure I was able to get a ping. Then I continued my conversation and the issue resurfaced. Finally, I just killed the converation and started fresh and it seems to be working fine now, so there may have been some issue within that thread that was causing the problem.
I'm not in WSL but it seems I may have to bite the bullet and give it a restart.
Full reboot, updated VSCode
resume creating feature as planned
● Continuing with the Alembic migration. Let me read an existing migration to follow the pattern.
● Read(alembic/versions/2025_12_23_0917-4051c8c7a429_a....py)
⎿ Read 59 lines
⎿ Request timed out. Check your internet connection and proxy settings
Retrying in 20 seconds… (attempt 9/10)
/resume hasn't returned any past conversations as yet.
it seems /compact is required prior to resuming, which needs to happen quite often so I shall look for some settings to increase conversation size.
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.