Skip to content

Desktop 2.1.4 on Windows: ECONNRESET without VPN, works with VPN, curl succeeds #60533

Closed as duplicate

Description

@Denisamak

Description

OpenCode Desktop 2.1.4 on Windows.

The app previously worked. On the evening of October 29, 2026,
requests started failing without a manual update.

Multiple models fail with:
ECONNRESET: The socket connection was closed unexpectedly.

Important:

OpenCode logs repeatedly show:
failed to load OpenCode provider config
GET https://opencode.ai/console/api/v2/config
TypeError: ECONNRESET

Checks performed:

  • App restart and Windows reboot did not help.
  • No proxy variables found in the current PowerShell environment.
  • Service HTTP_PROXY, HTTPS_PROXY, ALL_PROXY and NO_PROXY are empty.
  • "service get" returns {"remote": {}}.
  • No enabled outbound block rules found in Windows Firewall.
  • Only Windows Security is installed.

Could you help diagnose why the app's connection fails while curl
succeeds, and explain how to enable detailed network logging?

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot

No response

Operating System

Windows 11

Terminal

No response

Activity

  1. opencodejr commented on Oct 30, 2026

    @opencodejr
    Contributor

    Thanks for the detailed report and the curl comparison, which made this easy to place.

    I think this is a duplicate of #60399. It has the same pattern: on Windows, requests to opencode.ai fail with ECONNRESET without a VPN and work with one, while curl on the same machine succeeds. Reports there also say it started on Oct 29–30, without any update. The cause found there is that some ISPs' traffic filtering (DPI) drops or resets the TLS handshake that OpenCode 2.x's bundled runtime sends. That handshake includes a post-quantum key share, which makes it about 1.5 KB, while curl's is much smaller and gets through. So the connection is cut before any HTTP request is sent, which is why the provider config fetch fails as well.

    To check whether it's the same cause on your connection, compare a post-quantum handshake with a classic one to the same host (needs OpenSSL 3.5+):

    openssl s_client -connect opencode.ai:443 -servername opencode.ai -groups X25519MLKEM768 </dev/null
    openssl s_client -connect opencode.ai:443 -servername opencode.ai -groups X25519 </dev/null
    

    If the first one hangs or resets and the second one succeeds, it's the same problem. A browser failing to load opencode.ai without the VPN is another sign. #60399 has detailed measurements and workarounds, such as adding opencode.ai to a DPI-bypass host list. If you post there, please include your ISP and region.

    For more detailed logs, the log files are in %USERPROFILE%\.local\share\opencode\log\. With the CLI you can also run opencode run --print-logs ... to see them live.

    Possible duplicates and related issues, ordered by likelihood:

    The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.

  2. opencodejr commented on Oct 31, 2026

    @opencodejr
    Contributor

    Closing this as a duplicate of #60399, since there's been no reply showing a difference. The symptoms match: ECONNRESET to opencode.ai without a VPN, it works with one, and curl succeeds. They point to the same cause, ISP filtering that drops the larger post-quantum TLS handshake.

    Please follow #60399 for updates and workarounds. If the openssl check from my earlier comment shows something different on your connection, reply here and we can reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions