You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report! This error can come from several different causes, so we need a few details to work out which one you're hitting:
OpenCode version (opencode --version), your OS, and how you installed OpenCode.
Where you see the error: the TUI, the desktop app, opencode run, or another client (e.g. OpenChamber).
Provider and model you were using (e.g. OpenCode Zen/Go free models, Anthropic, OpenAI, a custom/OpenAI-compatible endpoint).
When it happens: on every message, after the session has been idle for a while, or during long or complex responses. Does retrying help?
Whether you're behind a proxy, VPN, firewall or antivirus, and whether a VPN changes anything.
If you can, the logs from running with --print-logs around the time of the error.
You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know when you're done.
These existing issues may already cover your problem, ordered from most to least likely:
@a1elen — one quick question that would pin this down. While the browser can't open opencode.ai, does curl still work from the same machine, same moment?
If that prints 200 while Chrome fails, we are hitting the same thing on several Rostelecom lines today: the DPI drops the TLS handshake only when the ClientHello carries a post-quantum key share (Chrome and Bun send one, Schannel curl does not — measured 3/3 timeout vs 3/3 OK against the same IP). Also, which ISP and city are you in?
@a1elen confirmed the discriminator here: curl returns 200 on the same machine and moment while the browser cannot load the site (Irkutsk, Rostelecom). That is the same condition as #60399 and #60422 — and not an OpenCode defect, since the connection is dropped during the TLS handshake before any request is sent.
Please follow #60399 for the measurements and the hostlist workaround.
We're closing this for now because we haven't heard back with the details we asked for: OpenCode version, OS and install method, where the error appears, the provider and model, when it happens, any proxy/VPN/firewall, and --print-logs output. The ECONNRESET: The socket connection was closed unexpectedly error has several possible causes, and without these details we can't tell which one you're hitting or reproduce it.
If it's still happening, please reply here with those details and we can reopen it. You may also want to check whether one of these covers your case:
Activity
opencodejr commentedon Oct 30, 2026
Thanks for the report! This error can come from several different causes, so we need a few details to work out which one you're hitting:
opencode --version), your OS, and how you installed OpenCode.opencode run, or another client (e.g. OpenChamber).--print-logsaround the time of the error.You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know when you're done.
These existing issues may already cover your problem, ordered from most to least likely:
a1elen commentedon Oct 30, 2026
same, yesterday was working perfectly, today i cant even open opencode.ai
MLGSW4G commentedon Oct 30, 2026
@a1elen — one quick question that would pin this down. While the browser can't open opencode.ai, does
curlstill work from the same machine, same moment?If that prints
200while Chrome fails, we are hitting the same thing on several Rostelecom lines today: the DPI drops the TLS handshake only when the ClientHello carries a post-quantum key share (Chrome and Bun send one, Schannel curl does not — measured 3/3 timeout vs 3/3 OK against the same IP). Also, which ISP and city are you in?a1elen commentedon Oct 30, 2026
@MLGSW4G yeah, 200
Irkutsk, Rostelecom
MLGSW4G commentedon Oct 30, 2026
@a1elen confirmed the discriminator here:
curlreturns 200 on the same machine and moment while the browser cannot load the site (Irkutsk, Rostelecom). That is the same condition as #60399 and #60422 — and not an OpenCode defect, since the connection is dropped during the TLS handshake before any request is sent.Please follow #60399 for the measurements and the hostlist workaround.
PAVchensky commentedon Oct 30, 2026
same 200. Msk
YourReflection commentedon Oct 31, 2026
@PAVchensky https://github.com/YourReflection/zapret-opencode-bypass
Denisz0785 commentedon Oct 31, 2026
same, Krasnodar, Russian Federation
opencodejr commentedon Nov 2, 2026
We're closing this for now because we haven't heard back with the details we asked for: OpenCode version, OS and install method, where the error appears, the provider and model, when it happens, any proxy/VPN/firewall, and
--print-logsoutput. TheECONNRESET: The socket connection was closed unexpectedlyerror has several possible causes, and without these details we can't tell which one you're hitting or reproduce it.If it's still happening, please reply here with those details and we can reopen it. You may also want to check whether one of these covers your case:
Thanks!