Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Can't sigin with CLI - "context deadline exceeded"
Not sure what's awry here, but I cannot log into my account via the CLI - I keep getting the error "context deadline exceeded". I have the same setup on another machine and it works there. Any ideas ...
I'm having the same issue, but I noticed that the behaviour is different depending on whether I've opened and unlocked 1password separately and left it open.
When i run op signin --debug --account <account> without doing so, I get the same as neilio:
11:14AM | DEBUG | Session delegation enabled
11:14AM | DEBUG | NM request: NmRequestAccounts
11:14AM | DEBUG | NM response: Success
11:14AM | DEBUG | NM request: NmRequestAccounts
11:14AM | DEBUG | NM response: Success
11:14AM | DEBUG | NM request: NmRequestAuthorization
11:14AM | DEBUG | NM response: Success
11:14AM | DEBUG | NM request: NmRequestAccounts
[ERROR] 2023/07/04 11:14:53 read: context deadline exceeded
when I open and unlock 1password and run op signin --debug --account <account>:
11:09AM | DEBUG | Session delegation enabled
11:09AM | DEBUG | NM request: NmRequestAccounts
11:09AM | DEBUG | NM response: Success
11:09AM | DEBUG | NM request: NmRequestAccounts
11:09AM | DEBUG | NM response: Success
11:09AM | DEBUG | NM request: NmRequestAuthorization
11:09AM | DEBUG | NM response: Success
11:09AM | DEBUG | NM request: NmRequestAccounts
11:09AM | DEBUG | NM response: Success
11:09AM | DEBUG | NM request: NmRequestDelegatedSession
11:09AM | DEBUG | NM response: Success
the auth popup is at the NmRequestAuthorization step in both cases - but it seems like the application is closing too quickly or something in the case when it's being opened specifically by the CLI.
