git-upload-pack: command not found

I’ve read this answer about eight-five times, but there’s something I’m not understanding correctly:

git-upload-pack: command not found, how to fix this correctly

  • What are the commands for using Git Bash in Windows e.g. when in git diff mode?
  • How do I pass an absolute path to the adb command via git bash for windows?
  • linux PS1 - display branch name only inside a git repo
  • How can I put $HOME/opt/git/bin to my PATH?
  • OSX Yosemite - invalid characters in path
  • Is there a 'git sed' or equivalent?
  • When I try to clone a repository on my server, I get the following:

    bash: git-upload-pack: command not found

    But when I clone by giving clone the -u /usr/local/bin/git-upload-pack option, all works well.

    I guess this makes sense, since that’s the position of the git-upload-pack on my server.

    The top answer suggests my .bashrc file on server needs to be updated to reflect this, as the result of ssh you@remotemachine echo \$PATH does not return /usr/local/bin. (It returns /usr/bin:/bin:/usr/sbin:/sbin).

    But when I look at my .bashrc file, it contains:

    export PATH=/usr/local/bin:$PATH

    So now I’m confused.

    What do I need to do to avoid using the -u /usr/local/bin/git-upload-pack option every time? Why does ssh you@remotemachine echo \$PATH not return /usr/local/bin? Is this something to do with login and non-login shells?

    Please help! Thanks in advance.

  • Find a Pull Request on Github where a commit was originally created
  • Extended regular expressions (ERE) for .gitignore
  • gitlab-shell: Disallowed command
  • Unable to Git Pull to update my Git local repo
  • Diff in Emacs between version of file in working dir and previous commit in git repo
  • Changing “git status” output colors in Posh-Git
  • 5 Solutions collect form web for “git-upload-pack: command not found”

    This is connected to this issue:

    Ssh is not loading your environment by default when sending a command without going to interactive mode.

    good solution is the one with .ssh/environment file:

    in /etc/ssh/sshd_config add:

    PermitUserEnvironment yes

    Then just create .ssh/ directory and dump envronment to .ssh/enviroment:

    cd ~/
    mkdir .ssh
    env > .ssh/environment

    Restart SSH

    /etc/init.d/sshd restart

    Now when you do this from your local machine:

    ssh  "which git-upload-pack"

    you s’d get


    and git clone s’d work.

    Yes, it is to do with login and non-login shells. The .bashrc file only gets loaded in non-login shells. You can use .bash_profile for login shells. Just add the same modification to your PATH in the .bash_profile file and you should be good.

    export PATH=/usr/local/bin:$PATH

    You may find this is an interesting article on the difference between .bashrc and .bash_profile, and login and non-login shells.

    I solved this issue in my case by logging into the remote machine, a Ubuntu box, and doing sudo apt-get install git. Not sure if this is overkill or not, but solved the problem for me instantly.

    My solution for this problem

    1. Check path for the git-upload-pack on your remote machine:

      ssh yourname@IP-addressORdomain 'which git-upload-pack'

    If it gives a path – copy it (without git-upload-pack and trailing slash. Examples: /usr/bin, /home/yourname/bin, /whatever/gituploadpack/path, etc.).

    1. Check your PATH on the remote machine during login shell:

      ssh yourname@IP-addressORdomain 'echo $PATH'

    There is no such a path (/whatever/gituploadpack/path), is not it? Good!

    1. Login to your remote machine:

      ssh yourname@IP-addressORdomain
    2. Open .bashrc_profile:

      nano /home/yourname/.bashrc_profile
    3. Find these lines if any:

      if [ -f ~/.bashrc ]; then

    …and change them for:

        if [ -f ~/.bashrc ]; then
            source ~/.bashrc
    1. Open .bashrc:

      nano /home/yourname/.bashrc
    2. Add these 4 lines:

      if [ -d "/whatever/gituploadpack/path" ] ; then
      export PATH
    3. Exit the remote machine:

    4. Check your PATH on the remote machine during login shell:

      ssh yourname@IP-addressORdomain 'echo $PATH'

    Do you see /whatever/gituploadpack/path? Congrats!

    Note now you’ve solved not only git-upload-pack problem but also git-receive-pack and other executables on your /whatever/gituploadpack/path!

    I was getting the following errors:

    git-credential-osxkeychain died of signal 11

    When I was doing git pull, I would get

    fatal: not found: did you run git update-server-info on the server?

    I am guessing it had to do with my previous invalid github credentials in the keychain.

    • Opened keychain access tool using Command space
    • searched for github in the keychain access tool
    • removed all the entries related to github (since I no longer needed it)
    • followed the setup git password caching section again setup git
    • it worked

    Incase any of the above answers does not help.

    Git Baby is a git and github fan, let's start git clone.