Is there any way to configure SSH keys to Lazygit?

[hasin023]

Every time I try to pull or push to a remote repo that is using the SSH link, It says, "Permission denied (publickey)". How can I resolve this??

[mark2185]

How do you push through the cli?

[hasin023]

In the most standard way that lazy git has to offer. 'a'[To add all un-tracked files] -> 'c' [To write commit mssg and commit] -> 'P' [to push]

[mark2185]

I was thinking through using git itself. Do you have to put in the passphrase or stuff like that.

[samuelnihoul]

yes we do

[mark2185]

@samuelnihoul then look into an SSH agent program like keychain.

Once you add your key into the keychain you'll only have to enter the passphrase the first time it is used.

[DusanLesan]

You can use gnome keyring which can be set up to unlock on login to avoid additional pass prompts for ssh https://wiki.archlinux.org/title/GNOME/Keyring

[RollsChris]

I also have this issue

[hasin023]

I couldn't find any fix, so I just stopped using Lazygit :")

[hasecilu]

You need to configure SSH on YOUR SYSTEM not Lazygit, maybe the agent is not working. Maybe bad configuration.
I wrote a guide some time ago maybe someone find something useful there.

[hasecilu]

Mmm, maybe there is a Windows limitation that prevents the same flawless behaviour on Linux.

[RollsChris]

or maybe windows is being snubbed by the linux possy ;) anyway i think this repo should just remove the statement that it supports windows

[SuperSocialForce]

It also happens on my ubuntu machine.

[mark2185]

@SuperSocialForce did you follow @hasecilu's guide and which step fails?

The general solution is to look into an SSH agent program like keychain.

[SuperSocialForce]

It worked! Thanks

[ArcSpecter]

i have the same issue. lazygit is giving me error: Permission denied (publickey, password)
although from same terminal from where I run lazygit if I push things using Git command line, it works just fine (it asks password, i enter it and it pushes changes in)

and I am Debian user.

i guess lazygit is not working properly here. as simple as that
its ok..back to Sublime Merge ;-)

[mark2185]

@r2com Look into an SSH agent program like keychain.

Once you add your key into the keychain you'll only have to enter the passphrase the first time it is used.

[EricDuminil]

For what it's worth:
on my Ubuntu laptop, I have SSH private keys 1 and 2. Both can give access to my git server.
Key 1 is loaded in ssh-agent. git pull works fine in terminal, and doesn't ask for any password. It apparently uses Key 1.

When starting lazygit, it asks me for password for Key 2, which isn't required to access the git server anymore.

[toberoni]

I had this problem because my project's remote repo was configured to use password auth (I guess by VSCode).

In your project try git remote -v and if you see a URL with https this is likely the problem:

> origin  https://github.com/YOUR_GIHUB_USERNAME/YOUR_REPO_NAME.git (fetch)

Solution:
If you change your remote URL the CLI & Lazygit should use SSH instead of password auth:

git remote set-url origin [email protected]:YOUR_GIHUB_USERNAME/YOUR_REPO_NAME.git

Hope that helps!

[arieldd]

This solved it for me, thanks.

[Souvlaki42]

Did anyone find a Windows specific solution? It worked just fine when I tested on Linux but my main workspace is on Windows because I have issues with WSL2.

[mark2185]

The same solution as above should work here as well - setting up an SSH agent.

[azinsharaf]

i think i have found why it fails on window. not sure what could be a workaround.
When i create a ssh key (and include a passphrase) then lazygit can't pull. I created a ssh key without a passphrase and lazygit works.

[mark2185]

The same solution as above should work here as well - setting up an SSH agent.

[tom-gora]

Had this problem resolved it writing myself a wrapper function around lazygit that replaced my alias:

# wrapper for lazygit to init ssh-agent
lg() {
  local IS_AGENT IS_IDENTIFIED FIRST_AVAILABLE
  IS_AGENT="$(pgrep -u "$USER" ssh-agent)"
  local PRIMARY_SSH_KEY="$HOME/.ssh/github_auth_primary"
  local FALLBACK_SSH_KEY="$HOME/.ssh/github_auth_fallback"

  if [ -f "$PRIMARY_SSH_KEY" ]; then
    FIRST_AVAILABLE="$PRIMARY_SSH_KEY"
  else
    if [ -f "$FALLBACK_SSH_KEY" ]; then
      FIRST_AVAILABLE="$FALLBACK_SSH_KEY"
    else
      echo "No SSH keys found. Exiting."
      return 1
    fi
  fi

  if [ -z "$IS_AGENT" ]; then
    echo "SSH agent not running. Should have been bootstraped with the shell."
    echo -e "Run \`eval \"\$(ssh-agent -s)\"\` to start it. Investigate why not running."
    return 1
  fi

  IS_IDENTIFIED=$(ssh-add -l | grep "[email protected]")

  if [ -z "$IS_IDENTIFIED" ] && [ -f "$FIRST_AVAILABLE" ]; then
    /usr/bin/ssh-add "$FIRST_AVAILABLE" &&
      lazygit
  else
    lazygit
  fi
}

If anyone is better at scripting feel free to chime in with suggestions.
NOTE: my ssh-agent is bootstraped in .zshrc to start with the shell session so the script expects it to be running. If not it prints a hint what to do.

[MykolaVaskevych]

This is off-topic, but I hate dealing with SSH keys. I use 1Password manager with a friendly CLI and SSH agent. So, all the hard work of generating, signing, and using SSH 1Password is done for me automatically. It works fine with any terminal and lazy git with zero additional setup steps. https://developer.1password.com/docs/ssh/agent

[MykolaVaskevych]

And no, I am not a bot, and it's not sponsored.