Skip to content

BunInstallFailederror on First Run #6052

Closed as not planned
Closed as not planned

Description

@ZeroCool2u

Description

Can't get anymore info out of opencode on this error. Installed using the standard curl command. There is a corporate proxy, but environment variables are configured correctly including the NODE_EXTRA_CA_CERTS variable. All other apps are using the exact same configuration and work correctly.

(base) ubuntu@machinename:/mnt$ opencode
^[\{
  "name": "BunInstallFailedError",
  "data": {
    "pkg": "opencode-copilot-auth",
    "version": "0.0.9"
  }
}

OpenCode version

1.0.193

Steps to reproduce

  1. Set environment variables for corporate proxy usage
  2. Install opencode using standard curl command
  3. Start opencode

Screenshot and/or share link

No response

Operating System

Ubuntu 22.04.5 LTS

Terminal

bash via VSCode

Activity

  1. github-actions commented on Dec 23, 2025

    @github-actions
    Contributor

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

    The common thread in all these issues is that BunInstallFailedError occurs when there are network/proxy/certificate issues preventing successful installation of the opencode-copilot-auth package. Your issue with corporate proxy and NODE_EXTRA_CA_CERTS configuration is particularly similar to #2992.

    Feel free to ignore if none of these address your specific case.

  2. ZeroCool2u commented on Dec 23, 2025

    @ZeroCool2u
    Author

    It also fails when I set OPENCODE_DISABLE_DEFAULT_PLUGINS=true.

  3. rekram1-node commented on Dec 24, 2025

    @rekram1-node
    Collaborator

    @ZeroCool2u what is failing when you set that?

    That plugin shouldnt be installed at all if that flag is set

  4. self-assigned this
    on Dec 24, 2025
  5. ZeroCool2u commented on Dec 24, 2025

    @ZeroCool2u
    Author

    The exact same command is failing, just starting opencode. Same output as before from the same command when that variable is set. I also tried setting it to 1 as well as true, but same result.

  6. lematosdev commented on Jan 6, 2026

    @lematosdev

    i fixed it by setting export NODE_TLS_REJECT_UNAUTHORIZED=0

  7. thdxr commented on Mar 25, 2026

    @thdxr
    Member

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

  8. removed
    bugSomething isn't working
    on May 3, 2026
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