Error: error creating SSH agent: "SSH agent requested but SSH_AUTH_SOCK not-specified" on `git bug push`

[NobbZ]

Please guide me to a way to provide additional information…

Yes, I use SSH URLs for git. No, they are not password protected.

If though starting SSH-Agent and adding the key, the error becomes:

Error: ssh: handshake failed: knownhosts: key mismatch

Regular git operations against the remote work.

[patricioantoniotoledo]

cd ~/.ssh ssh-add ~/.ssh/id_rsa

might help

[NobbZ]

To be honest, I do not even (want to) use SSH-agent.

I want the configured SSH-config to be respected and the command to just work.

I stoped using git-bug because of this a couple of days after posting this issue without a reply.

[octvs]

Might be related, I had a similar issues prompting an handshake fail, which was fixed by building from source.

[dllud]

I was facing the exact same error in the title. Besides starting a SSH Agent eval "$(ssh-agent -s)" and adding the key ssh-add ~/.ssh/mykey, I had to use a full URL (ssh://[email protected]:22/path/to/project.git) in the git remote. Only this got git bug push/pull working. This workaround was reported by @Subfortytwo at #572. It seems like the SSH Agent does not read my ~/.ssh/config?

Anyway, I am on the same page as @NobbZ: I would rather avoid using a SSH Agent. Is that possible? It wasn't needed last time I used git-bug (a couple years ago).

[github-actions[bot]]

This bot triages untriaged issues and PRs according to the following rules:

• After 90 days of inactivity, the lifecycle/stale label is applied
• After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

To remove the stale status, you can:

• Remove the lifecycle/stale label
• Comment on this issue