Cannot connect to API: Connect Timeout Error (attempted addresses: 172.65.90.23:443, 172.65.90.22:443, 172.65.90.20:443, timeout: 10000ms) #50773

Activity

1. github-actions

   assigned

   MrMushrooooom

   on Sep 23, 2026
2. github-actions commented on Sep 23, 2026

   

   github-actionsBot

   on Sep 23, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • No issue template was used — the issue body contains only the error message from the title, with no description, reproduction steps, environment info, or other context
   • Please use the Bug Report template and fill in: a description of what you were doing when the error occurred, your OpenCode version, operating system, and steps to reproduce

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

   This issue might be a duplicate of existing issues. Please check:

   • Subject: OpenCode Desktop Windows – recurring Connect Timeout Error while direct HTTPS access works #48836: Same Cannot connect to API: Connect Timeout Error with identical Cloudflare IPs on Windows
   • Suddenly, I am unable to use opencode (go plan) on the Windows side #50576: Same error message and same IP addresses (172.65.90.x:443, timeout 10000ms)
   • Desktop: Cannot connect to API + AggregateError on high-latency providers (z.ai/GLM, DashScope/Qwen) — Node’s 250 ms connect-attempt cap; same provider works in the CLI #45178: Root cause analysis of this class of connect timeout errors in the Desktop app

   If you believe this was flagged incorrectly, please let a maintainer know.
3. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Sep 23, 2026
4. github-actions commented on Sep 23, 2026

   

   github-actionsBot

   on Sep 23, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

   Feel free to open a new issue that follows our issue templates.
5. github-actions

   removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Sep 23, 2026
6. github-actions

   closed this as not plannedon Sep 23, 2026