keybase / client

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

KBFS drive is empty, md-server: No secret key available #6002

Open kbarnes3 opened 7 years ago

kbarnes3 commented 7 years ago

Keybase GUI Version: 1.0.18-20170216112451+a5b6199

I updated Keybase on a computer that previously had the old command-line only client on it. After a reboot, I was still signed in, but the KBFS drive did not have the content I'd expect. Instead, I see a kbfs.error.txt file containing:

md-server: No secret key available

It's also probably interesting that I wasn't prompted to enter my secret key. On my other computer I got a challenge for my secret key with KBFS being given as the reason. If I run a command like keybase pgp sign I get prompted for a password every time. This behavior seems different that I'd expect from my other computer and previous versions.

My log ID 66b9b2d3fe362e1c7d0b481c.

maxtaco commented 7 years ago

@zanderz can you look into this? It seems another case of the repairman failing to move files over

zanderz commented 7 years ago

We changed the target directory for key storage awhile back and sometimes the migrating procedure isn't successful. Also, the CLI client may be old enough that the current installer has trouble upgrading. I recommend you make sure the old one is uninstalled, then check %APPDATA%\Keybase for any files ending with .mpack or .ss and move these to %LOCALAPPDATA%\Keybase, then restart the service by issuing keybase ctl restart.

We've made improvements to this migrating feature, but they have yet to be included in a release.

kbarnes3 commented 7 years ago

Thanks @zanderz, moving these files around manually fixed things up. I can see KBFS files and chat normally now.

I'll leave this issue open in case you guys want to use it to track something, but it sounds like this may already be known and tracked. I consider this issue resolved, so please close it when appropriate.