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
{{ message }}
Repository navigation
ECONNRESET: The socket connection was closed unexpectedly after upgrading from 1.9.5 to 2.2.0 #60657
After upgrading from 1.9.5 desktop opencode to 2.2.0 I got permanent errors in chat for all models ECONNRESET: The socket connection was closed unexpectedly. For more information,…
I've checked next:
desktop client work well at 1.9.5 version but failed on 2.2.0. Few reinstallations steps - 1.9.5 have no problem, may be used as workaround.
opening opencode.ai in chrome failed but page well getted by curl from command line. Curl version curl 8.13.0 (Windows) libcurl/8.13.0 Schannel zlib/1.3.1 WinIDN
Talking with other LLMs I got that most probability is TLS HelloClient message that are filtered by DPI. But anyway 1.9.5 work well it would be good to revert back how opencode client work with TLS from 1.9.5
Thanks for the report and for the curl, Chrome and zapret comparison. It made this easy to place.
I think this is a duplicate of #60399. Everything you describe matches what was found there. Some ISPs' traffic filtering (DPI) drops or resets the larger TLS handshake (ClientHello) that OpenCode 2.x's bundled runtime sends; Chrome sends a similar large one, which is why opencode.ai also fails in Chrome. Schannel curl sends a smaller handshake that gets through. That is also why zapret or a VPN fixes it, and why 1.9.5 still works for you. That issue has more measurements, discussion of a client-side fix and some temporary workarounds.
Possible duplicates and related issues, ordered from most to least likely:
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different. Please add any further details, such as your ISP or region, to #60399.
We haven't heard back, so I'm closing this as a duplicate of #60399. That issue covers the same problem: on some networks, filtering (DPI) drops the larger TLS handshake that OpenCode 2.x sends, so requests fail with ECONNRESET. curl still works, and a VPN or zapret fixes it. Please follow #60399 for updates and workarounds, and add details like your ISP or region there.
If your problem turns out to be different, reply here explaining how and we can reopen this. Thanks again for the detailed report!
Activity
opencodejr commentedon Oct 30, 2026
Thanks for the report and for the curl, Chrome and zapret comparison. It made this easy to place.
I think this is a duplicate of #60399. Everything you describe matches what was found there. Some ISPs' traffic filtering (DPI) drops or resets the larger TLS handshake (ClientHello) that OpenCode 2.x's bundled runtime sends; Chrome sends a similar large one, which is why opencode.ai also fails in Chrome. Schannel
curlsends a smaller handshake that gets through. That is also why zapret or a VPN fixes it, and why 1.9.5 still works for you. That issue has more measurements, discussion of a client-side fix and some temporary workarounds.Possible duplicates and related issues, ordered from most to least likely:
ECONNRESETwithout a VPN, works with a VPN, curl succeedsECONNRESETwith the built-in Zen provider: works with a VPN, fails withoutECONNRESET: The socket connection was closed unexpectedlyreportsThe bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different. Please add any further details, such as your ISP or region, to #60399.
d1m40fficial commentedon Oct 30, 2026
https://github.com/d1m40fficial/opencode-dpi-fix - Try this; it works for me.
opencodejr commentedon Oct 31, 2026
We haven't heard back, so I'm closing this as a duplicate of #60399. That issue covers the same problem: on some networks, filtering (DPI) drops the larger TLS handshake that OpenCode 2.x sends, so requests fail with
ECONNRESET. curl still works, and a VPN or zapret fixes it. Please follow #60399 for updates and workarounds, and add details like your ISP or region there.If your problem turns out to be different, reply here explaining how and we can reopen this. Thanks again for the detailed report!