Skip to content

Self-signed TLS certificate no longer working with 1.17.12+ #35365

Closed as not planned

Description

@llvs

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:

{
  "providers": {
    "llamacpp": {
      "api": { "npm": "@ai-sdk/openai-compatible" },
      "options": { "baseURL": "https://127.0.0.1:8888/v1" }
    }
  }
}

Screenshot and/or share link

No response

Operating System

Kubuntu Linux 24.04, zabbly Kernel 7.0.13, local llama.cpp (current version) server with self-signed TLS cert

Terminal

No response

Activity

  1. github-actions commented on Jul 4, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

  2. llvs commented on Jul 7, 2026

    @llvs
    Author

    Regarding the suggestions of the github-bot: No, I don't think the mentioned issues are related as they are for very old versions.

  3. llvs commented on Jul 9, 2026

    @llvs
    Author

    The issue seems to be resolved in version 1.17.18, at least the problem does not show in this version.

  4. github-actions commented on Sep 8, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions