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
Go plan: very slow responses and frequent EPROTO TLS handshake failures #58376
I'm using the Go plan in OpenCode, but the experience is currently quite poor. Requests are very slow, and I frequently hit TLS errors.
The most common error is:
EPROTO: The TLS handshake failed. Does the server speak TLS on this port?
The same network environment and account work fine with other providers. For example, when I switch to DeepSeek, everything runs smoothly and there are no TLS handshake failures.
I suspect this might be related to my current OpenCode version 1.19.4. Could the maintainers check if the Go plan endpoint has any TLS compatibility or stability issues?
Plugins
oh-my-openagent
OpenCode version
1.19.4
Steps to reproduce
Ensure you are using the Go plan subscription.
Open OpenCode and attempt to run a coding request.
Observe that the request takes a very long time or fails completely.
Occasionally, the process crashes with the error: EPROTO: The TLS handshake failed. Does the server speak TLS on this port?
Thanks for the report, and sorry the Go plan has been so slow for you.
OpenCode 1.19.4 is part of v1 (the opencode-ai package). v1 now only gets fixes for critical bugs, so this is unlikely to be fixed there. Please try the current v2 release (the @opencode/cli npm package, which provides the opencode command) and see whether the slowness and the EPROTO: The TLS handshake failed errors still happen.
If they also happen on v2, or you think this is critical (for example the process really crashes with no workaround), please reply here with:
the v2 version (opencode --version)
the Go model you used
a debug log excerpt from opencode --print-logs --log-level DEBUG that covers a slow or failing request
whether a proxy, VPN or corporate network is involved
Please also try once without oh-my-openagent so we can rule the plugin out.
If this turns out to be a problem with the Go service or your subscription itself rather than the app, email [email protected] and keep account details out of this public issue.
We haven't heard back, so we're closing this as not planned. The report is about OpenCode 1.19.4 (v1). v1 only gets fixes for critical bugs, and slow Go plan responses with intermittent EPROTO TLS handshake errors don't fall into that category.
If you still see this on the current v2 release (@opencode/cli), please open a new issue with:
the v2 version (opencode --version)
the Go model you used
a debug log from opencode --print-logs --log-level DEBUG that covers a slow or failing request
whether a proxy or VPN is involved
If it's a problem with the Go service or your subscription itself, please email [email protected]. Thanks for reporting it!
Activity
opencode-agent commentedon Oct 23, 2026
Thanks for the report, and sorry the Go plan has been so slow for you.
OpenCode 1.19.4 is part of v1 (the
opencode-aipackage). v1 now only gets fixes for critical bugs, so this is unlikely to be fixed there. Please try the current v2 release (the@opencode/clinpm package, which provides theopencodecommand) and see whether the slowness and theEPROTO: The TLS handshake failederrors still happen.If they also happen on v2, or you think this is critical (for example the process really crashes with no workaround), please reply here with:
opencode --version)opencode --print-logs --log-level DEBUGthat covers a slow or failing requestPlease also try once without oh-my-openagent so we can rule the plugin out.
Related issues, most likely first:
If this turns out to be a problem with the Go service or your subscription itself rather than the app, email [email protected] and keep account details out of this public issue.
opencode-agent commentedon Oct 24, 2026
We haven't heard back, so we're closing this as not planned. The report is about OpenCode 1.19.4 (v1). v1 only gets fixes for critical bugs, and slow Go plan responses with intermittent
EPROTOTLS handshake errors don't fall into that category.If you still see this on the current v2 release (
@opencode/cli), please open a new issue with:opencode --version)opencode --print-logs --log-level DEBUGthat covers a slow or failing requestIf it's a problem with the Go service or your subscription itself, please email [email protected]. Thanks for reporting it!