Forum Discussion

jiatao24's avatar
jiatao24
New Contributor
4 months ago
Solved

1Password-CLI not working

I'm installing 1Password-CLI on a new computer and I'm getting this error:

[ERROR] 2025/05/09 15:34:50 connecting to desktop app: write: The pipe is being closed.

Looking at the previous thread here: CLI can not connect to desktop app | 1Password Community

troubleshooting
windows

16 Replies

  • erbanku's avatar
    erbanku
    New Contributor
    4 months ago

    Solved, thanks!

    But if you're not planning to sign the code release, why even publish it? This isn't the first time this has happened, pretty disappointing.

     

    • Joshua_ag's avatar
      Joshua_ag
      Icon for 1Password Team rank1Password Team
      4 months ago

      There was an error on our end, this was not intentional. We are sorry for the error. 

  • Joshua_ag's avatar
    Joshua_ag
    Icon for 1Password Team rank1Password Team
    4 months ago

    Hi Everyone,

    Sorry for the issues you are having, something did go wrong with the signing of the 1Password CLI 2.31.0 and 2.31.0-beta.01 for Windows. Our team is currently working on a fix. 

    While we are working on the solution you can switch to the 2.30.3 version. 

    Either by: 
    - Going to our app updates site and downloading it directly then using our manual installation steps
    - Using winget and 'forcing' the installation of the working version:

    winget install 1password-cli --version 2.30.3 --force

    We will update again once we a fix has been released. 

    • Joshua_ag's avatar
      Joshua_ag
      Icon for 1Password Team rank1Password Team
      4 months ago

      Update: 

      A fixed version of the CLI beta has been released. You can update to that one (and the 1Password for Windows app beta/nightly) to take advantage of the fix. More details in the release notes

      We know that the stable/production versions of the 1Password app and CLI are still not fixed. Work for those is ongoing. 

      • RareBird15's avatar
        RareBird15
        New Contributor
        4 months ago

        Are the betas installable with WinGet, or do I need to follow the manual installation instructions? I've been using WinGet up until now.

  • jpettorino's avatar
    jpettorino
    New Contributor
    4 months ago

    Wow, they broke things across the board.

    After getting fed up trying to make it work on Windows, I switched to my Linux system. And it was broke af there, too. :/

  • jpettorino's avatar
    jpettorino
    New Contributor
    4 months ago

    This seems to break 1Password and VScode integration...

    This quick start guide will get you up and running with the extension.

    1. Set up the CLI - v2.4.0 or greater of the 1Password CLI needs to be https://developer.1password.com/docs/cli/get-started#install.
    2. ...

    (source: https://marketplace.visualstudio.com/items?itemName=1Password.op-vscode)

     

  • RareBird15's avatar
    RareBird15
    New Contributor
    4 months ago

    Can confirm the same issue here. Downgrading also fixed it for me.

  • jiatao24's avatar
    jiatao24
    New Contributor
    4 months ago

    I uninstalled the new version and re-installed 2.30.3 and it seems to be working, so it probably is the same problem as before.

    • wazzamatazz's avatar
      wazzamatazz
      New Contributor
      4 months ago

      Desktop app logs suggest that it's the exact same problem as before - the updated CLI app isn't signed:

      ERROR 2025-05-09T13:16:30.034+00:00 runtime-worker(ThreadId(8)) [1P:op-ipc\src\ipc\windows.rs:376] failed to verify trusted file certificate: WinApi(Error HRESULT(0x800B0100): No signature was present in the subject.)

    • murnana's avatar
      murnana
      New Contributor
      4 months ago

      I also stumbled upon this the first time I set up the CLI, so it helped! Thank you and I'll be sure to check out your site 🙌.

      For the benefit of others, I leave the CLI installation commands using winget.

      ```powershell
      winget install --id AgileBits.1Password.CLI --version 2.30.3
      ```

      • jpettorino's avatar
        jpettorino
        New Contributor
        4 months ago

        users may need to uninstall the broken / unsigned version first...

        TL:DR

        winget uninstall --id AgileBits.1Password.CLI

        winget install --id AgileBits.1Password.CLI --version 2.30.3

         

        All the things.

        PS C:\Users\myuser> op signin
[ERROR] 2025/05/12 10:09:00 connecting to desktop app: write: The pipe is being closed.
PS C:\Users\myuser> op --version
2.31.0
PS C:\Users\myuser> winget install --id AgileBits.1Password.CLI --version 2.30.3
Found an existing package already installed. Trying to upgrade the installed package...
No available upgrade found.
No newer package versions are available from the configured sources.
PS C:\Users\myuser> op --version
2.31.0
PS C:\Users\myuser> winget uninstall --id AgileBits.1Password.CLI
Found 1Password CLI [AgileBits.1Password.CLI]
Starting package uninstall...
Successfully uninstalled
PS C:\Users\myuser> winget install --id AgileBits.1Password.CLI --version 2.30.3
Found 1Password CLI [AgileBits.1Password.CLI] Version 2.30.3
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://cache.agilebits.com/dist/1P/op2/pkg/v2.30.3/op_windows_amd64_v2.30.3.zip
  ██████████████████████████████  8.34 MB / 8.34 MB
Successfully verified installer hash
Extracting archive...
Successfully extracted archive
Starting package install...
Command line alias added: "op"
Successfully installed
PS C:\Users\myuser> op --version
2.30.3
PS C:\Users\myuser> op signin
 Select account  [Use arrows to move, type to filter]
 > Team Account (redacted.from.view)