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
Self-signed TLS certificate no longer working with 1.17.12+ #35365
Opencode 1.17.12+ silently fails to connect to local HTTPS LLM servers with self-signed certificates
Versions: 1.17.12, 1.17.13 (still working in 1.17.11)
Startup takes more than a minute telling that the server is not available.
Send a prompt
Expected Behavior: Prompt processes and returns LLM response
Actual Behavior: Sidecar hangs for ~30-60 seconds then exits with code 0. No error shown in UI. No response received.
With my printf debugging I identified this:
NODE_EXTRA_CA_CERTS is not propagated to the sidecar subprocess
auth.get() hangs indefinitely for providers without auth requirements
AbortSignal is pre-aborted before fetch starts, causing immediate fetch failures
fs.existsSafe() calls in instruction.system() hang on certain paths
My workaround: Downgrade to 1.17.11 or apply patches to load CA certs in sidecar, add timeouts to auth.get(), and skip pre-aborted signals.
Would be happy if that would work again :-)
Plugins
No response
OpenCode version
1.17.12+
Steps to reproduce
Steps to Reproduce:
Run llama.cpp with --ssl-cert-file and --ssl-key-file (self-signed cert)
Configure provider in opencode.json:
Activity
github-actions commentedon Jul 4, 2026
This issue might be a duplicate of existing issues. Please check:
NODE_EXTRA_CA_CERTSis ignored by the opencode process (different platform, but same root cause area)llvs commentedon Jul 7, 2026
Regarding the suggestions of the github-bot: No, I don't think the mentioned issues are related as they are for very old versions.
llvs commentedon Jul 9, 2026
The issue seems to be resolved in version 1.17.18, at least the problem does not show in this version.
Document why both trust mechanisms are needed
github-actions commentedon Sep 8, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.