Gitup: Unable to Push/Pull with Error: authentication required by no callback set

[bjg222]

I have a simple git repo that I cloned in the command line, then opened via GitUp. I can push/pull via command line just fine, but when I try to the buttons in the lower right hand corner of GitUp, I get the error seen in the attached image. My server is on my local work network and does require authentication via SSH, for which I have a trusted key set up for passwordless SSH. I have been unable to find a setting that relates to push/pull that the error message could be referring to.

[swisspol]

Make sure your Git remote URL uses a standard format and see https://github.com/git-up/GitUp/wiki.

[bjg222]

I've reviewed the known issues before posting, but I'm not sure how that helps me? The page doesn't refer to the remote URL format at all. Also, I do not control the remote server, but just use it. The URL I am provided is this: server.company.com:/repo/tools

[zhangyoufu]

@bjg222 You do have set up password-less authentication for SSH, but not for GitUp.

According to https://github.com/git-up/GitUp/wiki:

• SSH config files (typically located at ~/.ssh/config) are ignored by GitUp since it uses libssh2 and not the ssh tool for SSH remote operations.
  
  
  
  • GitUp first attempts to find SSH private keys using the ssh-agent
  
  
  • It then tries all private key files in ~/.ssh/
  
  

GitUp found ssh-agent instance for your login session and ask for available private keys, which does not include your non-default SSH identity.
To solve your problem, ssh-add -K <path_to_your_key>.

[wprater]

I have a key added and Im still getting this error. any ideas?

[LJeub]

I was having the same issue and running git fetch on the repo from the terminal resolved it for me. No idea why that worked?

[luong-komorebi]

I believe a solution for this issue was discussed here https://github.com/git-up/GitUp/issues/35

[xtazz]

Still having this issue cause I have IdentityAgent configured in ssh config, but it's ignored by GitUp. Can I somehow config GitUp to make it work?

[SenHeng]

This is probably an old issue but it's the first result that pops up on google so for future google arrivers here is a solution.

MacOS has a habit of forgetting to restart the ssh-agent on boot, even after adding UseKeychain yes to the ssh config. The simple way is to trigger the ssh agent by running git fetch in the terminal, ssh-agent is then re-activated and GitUp will work again without any changes necessary.