Skip to content

Failed to fetch models.dev ERROR on every startup #32986

Closed as duplicate
Closed as duplicate

Description

@eskbusiness

OpenCode version: 1.17.8
Operating System: Ubuntu 24.04.4 LTS, kernel 6.8.0-111-generic, x86_64
Terminal: GNU Screen 4.09.01, TERM=xterm-256color

Every time I start opencode it logs an ERROR saying Failed to fetch models.dev. The log shows this on every session. I checked and models.dev resolves to Cloudflare IPs but the TLS handshake gets reset with Connection reset by peer. My model works fine so opencode must have a cached fallback, but the ERROR log every startup is confusing.

Steps to reproduce:

  1. opencode
  2. cat ~/.local/share/opencode/log/opencode.log | grep models.dev
  3. An ERROR entry appears for every single session

I saw issue #12408 about the same models.dev error. My report adds that this is a TLS Connection reset by peer from Cloudflare specifically, and that the cached fallback works fine so the log level should be reduced.

Activity

  1. github-actions commented on Jun 19, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • The description appears to be AI-generated (lengthy structured text with multiple sections, analogies, and pre-written suggested fixes). Please replace it with a concise, human-written description of what you actually observed.
    • Required fields are missing: OpenCode version, Operating System, Terminal, and Steps to reproduce are all left as _No response_. Please fill these in so the issue can be reproduced and investigated.

    Please edit this issue to address the above within 2 hours, or it will be automatically closed.


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

    If you believe this was flagged incorrectly, please let a maintainer know.

  2. added
    needs:complianceThis means the issue will auto-close after 2 hours.
    and removed
    needs:complianceThis means the issue will auto-close after 2 hours.
    on Jun 19, 2026
  3. github-actions commented on Jun 19, 2026

    @github-actions
    Contributor

    Thanks for updating the issue! It now includes all the necessary information — version, OS details, reproduction steps, and a clear description of the problem. Everything looks good.

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