search

keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.89k stars 1.23k forks source link

Client can't login : ▶ ERROR No resolution for name #5464

Open agusmakmun opened 7 years ago

agusmakmun commented 7 years ago 
$  ~ keybase login
Your keybase username or email address: myemail@foobar.com
▶ WARNING Error running Bug 3964 repairman: lksec load: no device id set, thus can't fetch server half
▶ WARNING In Bug 3964 repair: lksec load: no device id set, thus can't fetch server half
▶ ERROR No resolution for name=agusmakmun

This issue similiar with this one #5378, but here we found ERROR No resolution for name=

my log id: 397ead83494218f5d06a211c

maxtaco commented 7 years ago

Hmm, can you try this?

keybase db nuke
keybase login

As before? My guess is it's a caching bug, but let me know if this helps. I'll track it down if so. Thank you!

agusmakmun commented 7 years ago

I got this question....

$  ~ keybase db nuke
Really blast away your local database? (type 'YES' to confirm): yes
▶ WARNING Nuking database /home/agaust/.local/share/keybase/keybase.leveldb
▶ WARNING Nuking chat database /home/agaust/.local/share/keybase/keybase.chat.leveldb
$  ~ keybase login
Your keybase username or email address: myemail@foobar.com
▶ WARNING Error running Bug 3964 repairman: lksec load: no device id set, thus can't fetch server half
▶ WARNING In Bug 3964 repair: lksec load: no device id set, thus can't fetch server half
Enter a public name for this device: Linux

===============================
IMPORTANT: PAPER KEY GENERATION
===============================

During Keybase's alpha, everyone gets a paper key. This is a private key.
  1. you must write it down
  2. the first two words are a public label
  3. it can be used to recover data
  4. it can provision new keys/devices, so put it in your wallet
  5. just like any other device, it'll be revokable/replaceable if you lose it

Your paper key is

    XXXXXXXXXXXXX

Write it down....now!

Have you written down the above paper key? [y/N] y
 ▶ WARNING PushHandler: Cannot push state in firehose handler: 
gregor service not available (are you in standalone?)
You are logged in as agusmakmun
  - type `keybase help` for more info.

▶ WARNING Problem running new background identifier: API network error: 
Get https://api.keybase.io/_/api/1.0/merkle/path.json?poll=10&sig_hints_low=5&uid=e396bf3d4e70bd25e637cb6e57440719: 
dial tcp: lookup api.keybase.io on 127.0.1.1:53: server misbehaving

Hmmbb why server misbehaving ?, If I look at the browser I got https error:

Your connection is not private

Attackers might be trying to steal your information from api.keybase.io
(for example, passwords, messages, or credit cards). NET::ERR_CERT_AUTHORITY_INVALID

But, now it worked well for me...

$  ~ keybase id agusmakmun
▶ INFO Identifying agusmakmun
✔ public key fingerprint: D3DE F045 5B47 C435 B922 B02E 914B 3FA0 7E53 D974
✔ admin of python.web.id via HTTPS: https://python.web.id/keybase.txt
✔ "agusmakmun" on github: https://gist.github.com/a3dc3c1b799bc0b932092d8992370104
✔ "agusmakmun6" on twitter: https://twitter.com/agusmakmun6/status/821985026757705729
maxtaco commented 7 years ago

something might be weird with your local C/A

Also, please revoke your paper key, since you pasted it into a public forum..

Those errors are ugly but safe to ignore for now...

agusmakmun commented 7 years ago

oops, I forgot it... thank you... :+1: