New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot log in #6089

Closed
habi opened this Issue Mar 1, 2017 · 16 comments

Comments

Projects
None yet
4 participants
@habi

habi commented Mar 1, 2017

I've downloaded the Keybase app (on OS X 10.12.3 (16D32)) and would like to log in.
But I can't, I get the error shown in the attached screenshot.

screen shot 2017-03-01 at 21 26 07

my log id: 536dbb0dff8f515c6518251c

@cjb

This comment has been minimized.

Show comment
Hide comment
@cjb

cjb Mar 1, 2017

Contributor

Sorry about that. We'll check it out, in the meantime I suspect you'll be able to log in (and then use the GUI) by running keybase login in the terminal.

Contributor

cjb commented Mar 1, 2017

Sorry about that. We'll check it out, in the meantime I suspect you'll be able to log in (and then use the GUI) by running keybase login in the terminal.

@habi

This comment has been minimized.

Show comment
Hide comment
@habi

habi Mar 1, 2017

When I want to log in from the terminal (keybase login), I get an error about

Your keybase username or email address: habi
▶ ERROR SecretSyncer: no device found for ID=$REDACTED$

habi commented Mar 1, 2017

When I want to log in from the terminal (keybase login), I get an error about

Your keybase username or email address: habi
▶ ERROR SecretSyncer: no device found for ID=$REDACTED$
@cjb

This comment has been minimized.

Show comment
Hide comment
@cjb

cjb Mar 1, 2017

Contributor

Thanks, CC @patrickxb. (Perhaps run log send again, please?)

Contributor

cjb commented Mar 1, 2017

Thanks, CC @patrickxb. (Perhaps run log send again, please?)

@maxtaco

This comment has been minimized.

Show comment
Hide comment
@maxtaco

maxtaco Mar 1, 2017

Contributor

We'll try to take a look soon. Have you recently reset your account?

Contributor

maxtaco commented Mar 1, 2017

We'll try to take a look soon. Have you recently reset your account?

@habi

This comment has been minimized.

Show comment
Hide comment
@habi

habi Mar 1, 2017

I've cleaned up my Twitter account and (by error) deleted the keybase tweet.
I wanted to redo that, and thus 'had' to upgrade the app.
I've now done several tries of logging in, the farthest I get is to the point where keybase complains about my key being expired, even though it won't expire until March 2012, as seen in the attachment.

screen shot 2017-03-01 at 21 36 51

habi commented Mar 1, 2017

I've cleaned up my Twitter account and (by error) deleted the keybase tweet.
I wanted to redo that, and thus 'had' to upgrade the app.
I've now done several tries of logging in, the farthest I get is to the point where keybase complains about my key being expired, even though it won't expire until March 2012, as seen in the attachment.

screen shot 2017-03-01 at 21 36 51

@habi

This comment has been minimized.

Show comment
Hide comment
@habi

habi Mar 1, 2017

A new log is sent as 6dd52641f5d2bb206bb9df1c

habi commented Mar 1, 2017

A new log is sent as 6dd52641f5d2bb206bb9df1c

@patrickxb

This comment has been minimized.

Show comment
Hide comment
@patrickxb

patrickxb Mar 1, 2017

Contributor

Ok, your key definitely isn't expired. I see the expiration time of 1537736527 (september 2018).

Contributor

patrickxb commented Mar 1, 2017

Ok, your key definitely isn't expired. I see the expiration time of 1537736527 (september 2018).

@patrickxb

This comment has been minimized.

Show comment
Hide comment
@patrickxb

patrickxb Mar 1, 2017

Contributor

Did you enter the passphrase for the PGP private key when it asked for "You need a passphrase to unlock the secret key..."?

We have had a confusing prompt in the past (I believe a fix for that is in for the next release).

Contributor

patrickxb commented Mar 1, 2017

Did you enter the passphrase for the PGP private key when it asked for "You need a passphrase to unlock the secret key..."?

We have had a confusing prompt in the past (I believe a fix for that is in for the next release).

@habi

This comment has been minimized.

Show comment
Hide comment
@habi

habi Mar 1, 2017

habi commented Mar 1, 2017

@maxtaco

This comment has been minimized.

Show comment
Hide comment
@maxtaco

maxtaco Mar 1, 2017

Contributor

Digging now. Can you export here your public key?

/usr/local/MacGPG2/bin/gpg2 --no-tty --armor --export 090ba12ba7baf36a6c5b4b3df5c29d9fda96595c

Thank you!

Contributor

maxtaco commented Mar 1, 2017

Digging now. Can you export here your public key?

/usr/local/MacGPG2/bin/gpg2 --no-tty --armor --export 090ba12ba7baf36a6c5b4b3df5c29d9fda96595c

Thank you!

@habi

This comment has been minimized.

Show comment
Hide comment
@habi

habi Mar 1, 2017

habi commented Mar 1, 2017

@maxtaco

This comment has been minimized.

Show comment
Hide comment
@maxtaco

maxtaco Mar 1, 2017

Contributor

are you sure that's the same one we'd get with the above?

Contributor

maxtaco commented Mar 1, 2017

are you sure that's the same one we'd get with the above?

@habi

This comment has been minimized.

Show comment
Hide comment
@habi

habi Mar 1, 2017

habi commented Mar 1, 2017

@maxtaco

This comment has been minimized.

Show comment
Hide comment
@maxtaco

maxtaco Mar 1, 2017

Contributor

Oh, I see. The key you have on keybase's servers actually is expired. Can you use the website to update it? I think that will solve your problem. Then you'll be able to log in.

Contributor

maxtaco commented Mar 1, 2017

Oh, I see. The key you have on keybase's servers actually is expired. Can you use the website to update it? I think that will solve your problem. Then you'll be able to log in.

@maxtaco

This comment has been minimized.

Show comment
Hide comment
@maxtaco

maxtaco Mar 1, 2017

Contributor

This is what your key on our servers says:

pub   2048R/DA96595C 2012-03-18 [expired: 2016-03-18]
Contributor

maxtaco commented Mar 1, 2017

This is what your key on our servers says:

pub   2048R/DA96595C 2012-03-18 [expired: 2016-03-18]
@habi

This comment has been minimized.

Show comment
Hide comment
@habi

habi Mar 2, 2017

This was indeed the problem. But I didn't think it could be this from the error messages I got :)
Thanks for pointing me in the right direction, I'm now logged in and everything works as expected.

habi commented Mar 2, 2017

This was indeed the problem. But I didn't think it could be this from the error messages I got :)
Thanks for pointing me in the right direction, I'm now logged in and everything works as expected.

@habi habi closed this Mar 2, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment