Client: git: 'remote-keybase' is not a git command

[programehr]

I ran into this error: "git: 'remote-keybase' is not a git command. See 'git --help'." when trying to pull/push/clone.
I'm using version 2.12.2-20181218091941+29273f4110

[strib]

@programehr can you please share more info about what operation system you're running on, and what version/distribution of git you're using? And running keybase log send and posting the resulting log ID here would be useful as well.

Normally this is an issue with your local git environment, which is not properly looking for remote protocol helpers.

[programehr]

I'm using git version 2.18.0.windows.1 on Windows 10. I tried keybase log send several times and got an API network error avery time.
By the way, I didn't have a problem with this until today. I updated keybase today, but am not sure if it has to do with the problem.
Thanks.

[strib]

Are you using cygwin or some other non-standard terminal when you're running the commands?

[programehr]

I use MinGW.

[strib]

Not familiar with that one. Does git-remote-keybase.exe exist in an executable location?

[programehr]

It's in my AppData\Local\Keybase folder.

[strib]

That's the same location as your keybase.exe, which I assume works fine in this shell.

In the past, there was a user who fixed a similar issue by restarting bash (or closing the terminal and re-opening a new one). Maybe try that?

If that doesn't work, you can try copying git-remote-keybase.exe into your git's git-core directory, though that really shouldn't be necessary.

[programehr]

Restarting the terminal didn't work, but... copying into git-core did!
Thanks!

[strib]

Ok, thanks for the update. That's not really a great solution since it won't get updated when we put out new releases. You might want to do some more investigation to figure out why git isn't able to find remote helpers that exist in your path.

[programehr]

Restarting the terminal didn't work, but... copying into git-core did!
Thanks!

[ghost]

I needed to symlink git-remote-keybase.exec e.g. (using relative path from $HOME) ln -s .\AppData\Local\Keybase\git-remote-keybase.exe .\scoop\apps\git\current\mingw64\libexec\git-core\, which worked. A default Keybase install on Windows does not make this helper available.

[zanderz]

Does MinGW not automatically pick up changes to the current user's Windows path when it starts? If not, the only choice is to manually change the MinGW shell configuration for every Windows program that depends on modifying the path after it is installed, such as Keybase.

[nnjeremy]

I have a similar issue on Windows 10. Everything work perfectly when I use command line in git bash but I have the "git: 'remote-keybase' is not a git command." error with GitHub Desktop when I try to fetch. Copying git-remote-keybase.exe into the git-core directory work. But it's not a great solution because the file won't get updated (cf @strib previous message).
Thanks!

[jucie]

In Windows 10 I created a symbolic link and it worked. That will work even when keybase gets updated.

cd "C:\Program Files\Git\cmd
mklink git-remote-keybase.exe C:\Users\myuser\AppData\Local\Keybasegit-remote-keybase.exe

[marchage]

run from an elevated "Command Prompt"/cmd.exe, not Powershell.

[charltonstanley]

Confirmed what @jucie and @marchage mentioned.

run cd "C:\Program Files\Git\cmd mklink git-remote-keybase.exe C:\users\<myuser>\AppData\Local\Keybase\git-remote-keybase.exe
where <myuser> is your user profile name. Don't copy and paste the code like i did and not change the profile name... it doesn't work. 😛

[WonkySoft]

FWIW, I had this problem. It was simply because it was a brand new install of GitHub desktop that I was trying to clone the Keybased repo from. I restarted GitHub and it worked fine. I presume because it picked up the PATH environment variable that pointed to the keybase directory.

[scotthammack]

I just ran into this issue on a fresh install of Git 2.30.0 on Windows 10. I was able to fix it with:
export PATH=$PATH:/c/Users/<username>/AppData/Local/Keybase
It seems that the path used by Git Bash is completely independent of the path that Windows's Command Prompt uses. To keep it working permanently, I added the above to my ~/.profile