Skip to main content
Mar 29, 2022 3:35 PM UTC
Question

Error - You are not currently signed in.

After running eval $(op signin), I get "You are not currently signed in." for any subsequent op.

zsh:
```
➜ op --version
2.0.0
Last login: Tue Mar 29 09:39:55 on ttys002

➜ eval $(op signin)
Enter the password for mailto:redacted<li-user uid=.com at my.1password.com:

➜ op account get
[ERROR] 2022/03/29 10:25:36 You are not currently signed in. Please run op signin --help for instructions
```

The signin operation creates the file /var/folders/zc/REDACTED/T/com.agilebits.op.501/.XXXXXXXXXXXXXXXXXXXXXXXXXXX

with the json:

{"jwe":{"kid":"REDACTED","enc":"A256GCM","cty":"b5+jwk+json","iv":"REDACTED","data":"REDACTED"},"shorthand":"my"}

and sets the environment variable

OP_SESSION_XXXXXXXXXXXXXXXXXXXXXXXXXX=REDACTED

Also, op signin -f shows the help text:
"# Run 'eval $(op signin my)' to sign in to your 1Password account."

Which appears to be out of date, given:

eval $(op signin my)
[ERROR] 2022/03/29 10:31:51 expected at most 0 arguments but got 1 instead


1Password Version: 7.9.3 (70903004)
Extension Version: Not Provided
OS Version: mac OS 12.3
Referrer: forum-search:https://1password.community/search?Search=You%20are%20not%20currently%20signed%20in

17 replies

Apr 2, 2022 8:21 PM UTC

I just installed from scratch the 1Password CLI (version 2.0.0) on a linux server and I get the same "You are not currently signed in." error for every operation.

The signing operation seemed successful and the account is visible with:

➜ ~ op account list
SHORTHAND URL EMAIL USER UUID
my https://my.1password.com user@example.com[REDACTED]

Apr 4, 2022 9:58 AM UTC

Hey @mchadwick and @Chmurzak,

Thank you for reaching out to us!
Indeed, that piece of help-text is an oversight, the correct command is eval $(op signin --account me).
To diagnose this, can you please let us know what installation method did you use? Are you migrating from 1Password CLI 1, or are you a new user? Thanks, looking forward to hearing from you!

Best,
Horia

Apr 4, 2022 10:17 AM UTC

Hi @"Horia.Culea_1P",

I'm using a fresh ubuntu server with a fresh installation of CLI 2.0 (no migration from previous version).
Unfortunattely, signin with the additional --account flag is not helping (I have to use my instead of me):

$ op account list
SHORTHAND URL EMAIL USER UUID
my https://my.1password.com user@example.com[REDACTED]
$ eval $(op signin --account me)
[ERROR] 2022/04/04 10:14:35 no accounts found matching filter "me"
$ eval $(op signin --account my)
Enter the password for user@example.com[REDACTED] at my.1password.com:
$ op account list
SHORTHAND URL EMAIL USER UUID
my https://my.1password.com user@example.com[REDACTED]
$ op vault list
[ERROR] 2022/04/04 10:10:12 You are not currently signed in. Please run `op signin --help` for instructions

Apr 4, 2022 10:23 AM UTC

Did you install using apt, or by downloading and running the installer?

Apr 4, 2022 6:12 PM UTC

Hi @Horia.Culea_1P,

I installed using Homebrew 3.4.4. I did not migrate from a previous CLI version. I get similar results to Chmurzak.

```bash
$ op account list
SHORTHAND URL EMAIL USER UUID
my https://my.1password.com [REDACTED]

$ eval $(op signin --account me)
[ERROR] 2022/04/04 13:10:51 no accounts found matching filter "me"

$ eval $(op signin --account my)
Enter the password for [REDACTED] at my.1password.com:

$ op vault list
[ERROR] 2022/04/04 13:11:54 You are not currently signed in. Please run op signin --help for instructions
```

Apr 5, 2022 10:40 AM UTC

After running eval $(op signin), can you please run printenv | grep OP_SESSION_ and let me know if the output is empty, or if you can see an environment variable set? The You are not currently signed in. error makes me think that there is a problem in setting the session token to an environment variable.

Apr 5, 2022 2:52 PM UTC

@"Horia.Culea_1P" - Yes, there is an environment variable set (see original post). Do you need the un-redacted variable name? The number of X's are indicative of the actual length.

Apr 6, 2022 12:07 AM UTC

Having the same issue here. Does the plan your account is associated with matter?

Apr 6, 2022 10:15 PM UTC

Also seeing this issue w/ 1password cli 2.0.0, installed via homebrew on macOS 12.3.1 on my M1 MacBook Air. Running op signin, no matter how, does set the OP_XXX environment variable, but produces the same You are not currently signed in error for any further operations.

However, I can make things work by appending --session $OP_XXX (the same environment variable exported by op signin to commands. So I wonder if there is a problem with finding the specific OP_XXX environment variable that is needed; i.e. the variable is set, but op doesn't know what the value of XXX should be, maybe?

Apr 7, 2022 5:33 AM UTC

Checking in with the same issue on OS X 12.3 with a fresh install of the CLI app using brew commands as per the docs here: https://developer.1password.com/docs/cli/get-started#install

Exact same as what's described above:

  • Env var is set.
  • dot files with JSON data are created in /var/folders/bg/fsxdkll15tj6pllw6dwqcvbm0000gn/T/com.agilebits.op.501/ (Multiple, I assume from my multiple sign-in attempts while trying to make it work)
  • Manually passing --session flag makes it work.