search

keybase / client

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

Cannot open Keybase folders on Windows #4422

Open bdforbes opened 8 years ago

bdforbes commented 8 years ago

I have set up Keybase on my Windows 10 machine, and there is a K: drive appearing in Explorer, but when I try to open it I get "K:/ is unavailable...".

my log id: 16448dbe43474542fa68fd1c

strib commented 8 years ago

Hmm, looks like KBFS doesn't think you're logged into Keybase with your passphrase. Did you enter your password somewhere? It should have popped up a password entry dialogue if this is your first time running Keybase. Does the GUI offer a login option? Or you could try running keybase login or keybase unlock from the Keybase command client.

agmlego commented 7 years ago

I might have the same situation. Log ID 9a53e950d6b3e5b88448851c.

K: reports as unavailable, and keybase status indicates that KBFS is not running. Running kbfsdokan j: yields a fully-functional KBFS on J: and keybase status indicates that KBFS is now running.

keybase login and keybase unlock do not seem to have an effect on this.

akavel commented 6 years ago

Doesn't work for me either as of now (don't remember if I ever checked if it worked at all...)

newdayrising commented 6 years ago

I have this issue also. I think every time I restart after a clean install or repair I lose the K drive. I changed the drive letter to X and I still have the issue. After three repairs and one complete uninstall/reinstall I'm giving up.

zanderz commented 6 years ago

@akavel @newdayrising Please do a keybase log send at the command line and send us the resulting IDs.

newdayrising commented 6 years ago

46dfce9acd9d0016fb940f1c

zanderz commented 6 years ago

@newdayrising At what point were your logs sent? The installer logs seem to show reboot still pending, which would explain the error mounting the filesystem (Failed to mount dokan filesystem (i=16): Dokan failed: code=-5 "Mount error"). Another explanation could be that some other app is using Dokan. Any ideas @taruti ?

newdayrising commented 6 years ago

I restarted and the drive still is not functioning.

db1ab78a878f773924b0791c

Are there any popular apps that use Dokan? I noticed that the LogMeIn client has a "LogMeIn Files Drive" feature, but it was disabled. I Googled around and couldn't find anything about dokan+logmein. Thanks for looking into this.

newdayrising commented 6 years ago

@zanderz Any updates? Is there a way for me to figure out what application (if any) is causing this issue? I recently completely refreshed my PC and installed Keybase. Not long after installing the K drive stopped working. Since there aren't people constantly complaining about this issue, I'm guessing it's particular to my environment. The only applications I installed that mess with the file system are Insync (https://www.insynchq.com/) or the LogMeIn Client software (http://help.logmein.com/articles/en_US/Downloads/LogMeIn-Client-desktop-app-for-Windows-sfdwn0121).

mickdekkers commented 6 years ago

I think I'm having the same issue. Log ID: 6fc1b5b4b2df3cc668d3ef1c If I try to view the Keybase drive in Windows Explorer it says K:\ is unavailable

zanderz commented 6 years ago

@mickdekkers Your logs show that the filesystem was mounted ok but kbfs can't reach its server. The later part of the logs are filled with: connection error: dial tcp: lookup bserver-0.kbfs.keybase.io: no such host I don't think we had an outage. Are you maybe behind a proxy or something?

zanderz commented 6 years ago

@newdayrising Please send another log from your fresh installation. There are various reasons the mounted filesystem might go away

taruti commented 6 years ago

Looked at this today, At least Insync causes some issues.

@newdayrising can you run sc query dokan1 from cmd.exe?

On a test machine after installing insync, no K:. After a sc query dokan1 K: appears. Investigating why, but this appears to be a driver incompatibility issue.

mickdekkers commented 6 years ago

@zanderz as far as I know, I'm not behind a proxy. I do use a VPN, but it was not active at that time. Is there anything I can do to help debug the issue?

taruti commented 6 years ago

For Insync it seems like 1.3.24 (it autoupdates) works with KBFS, while some earlier versions had issues.

@newdayrising do things work for you at the moment?

newdayrising commented 6 years ago

Hello @taruti. My Insync client is at v. 1.4.5. I'm still having the K drive issue. I uninstalled and re-installed Keybase, but that didn't solve the problem. There must have been leftover files, though - it recognized the device and my login name. If you think a full uninstall (I'm guessing I'll need to remove Appdata folders?) is necessary, I'll perform one.

Result of sc query dokan1:

SERVICE_NAME: dokan1
        TYPE               : 2  FILE_SYSTEM_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

@zanderz 2a20c66a121d1d1774193d1c

zanderz commented 6 years ago

@newdayrising I doubt reinstalling of Keybase would help. What you can try is to open CMD as admin and go to %programFiles%\Dokan\Dokan Library-1.1.0\sample\mirror, and run mirror /r [testdir] /l [mountletter] and make sure you can browse the given directory at the given mount letter. If the mirror sample is not present, you can uninstall Dokan and install it from https://github.com/dokan-dev/dokany/releases/download/v1.1.0.2000/DokanSetup_redist.exe If the problem is some other driver conflicting with Dokan, it should show up in the mirror sample too.

newdayrising commented 6 years ago

Ok. Insync is definitely causing the K drive to not load (Dokan?). If I remove it from automatically starting with Windows, Keybase works without issue. Once Keybase is loaded, I can start Insync and it seems to also work without issue. If Insync auto-starts the K drive is always "unavailable."

I probably should have tested this much earlier.

@zanderz I haven't performed the steps you provided because I think it's definitive that another driver is interfering. Let me know if you believe it will assist in resolving this issue. I'm going to reach out to Insync support and see what they have to say.

Thank you!

zanderz commented 6 years ago

I doubt it's necessary, sounds like you've narrowed it down already, thanks.

taruti commented 6 years ago

@newdayrising A solution could be to change the startup order so keybase is loaded before Insync on startup.

Thank you for your help,. seems like the test machine where things appeared to be "fixed" just happened to load them in a different order on startup. This has helped us to narrow things down.

rfgamaral commented 5 years ago

I'm also having this issue on my work laptop. It works fine on my home PC. Both are running Windows 10, same build:

image

Here's the log id: 4ba991fe687f54da0747431c

Any ideas @zanderz ?

maxtaco commented 5 years ago

@zanderz you mean. Sorry Tom for the mention!

rfgamaral commented 5 years ago

Yes, sorry :(

zanderz commented 5 years ago

@rfgamaral Your logs show that kbfs is mounting the filesystem correctly. After that, though, I see 2 things:

  1. a flaky connection to KBFS servers
  2. FS CreateFile - Refusing real access: SID match error.

2 can happen if Dokan and/or Keybase were installed under different Windows accounts than that currently logged in. (right @taruti ?)

rfgamaral commented 5 years ago

@zanderz

2 can happen if Dokan and/or Keybase were installed under different Windows accounts than that currently logged in. (right @taruti ?)

I only have one account on this machine, so that's not likely the problem?

The problem might be one other thing...

Like I said, this is my work laptop, and there's a few things I'm locked out from doing. For instance, if I plug a USB drive, I can't access it, it's locked. Actually, a lot of storage related things are locked out. But Google Drive works fine though.

SaltwaterC commented 5 years ago

I have possibly the same situation. Whenever it starts from a freshly booted computer, it shows the volume as unavailable. After messing around with kbfsdokan in command line, which was not ideal as I had a cmd standing around, I have figured out that by killing the kbfsdokan process spawned by Keybase, another one will be spawned immediately. The respawned process mounts a fully functioning drive.

mcx808 commented 4 years ago

Same issue here in 2020. Log ID 48c60beaa73ef06cc35d981c I tried updating Dokan manually to 1.3.1.1000, same issue.

jbshirk commented 11 months ago

Same problem here, as of the last few days. There was an office365 update rolled out universally. Now my KBFS is no longer accessible (K: drive) shortcut stopped working.

Edition Windows 10 Pro Version 22H2 Installed on ‎6/‎6/‎2022 OS build 19045.3693 Experience Windows Feature Experience Pack 1000.19053.1000.0