Abra recipe release throws a weird SSH error when publishing tags #724

New Issue

pharaohgraphy · 2025-11-07T22:21:44Z

pharaohgraphy commented

2025-11-07 22:21:44 +00:00

This popped up while I was trying to use Abra for the first time to release a recipe update, at first I got an error due to not having allowed the fingerprint for the host previously (I was using HTTPS), so I changed my git remote to use SSH as well & verified it works.

Then this error popped up the 2nd & 3rd time afterwards, and I verified that git works with SSH just fine, I even published the tags myself with SSH later via git manually.

This is the error in question when Abra attempts to publish the tags:

ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

This popped up while I was trying to use Abra for the first time to release a recipe update, at first I got an error due to not having allowed the fingerprint for the host previously (I was using HTTPS), so I changed my git remote to use SSH as well & verified it works. Then this error popped up the 2nd & 3rd time afterwards, and I verified that git works with SSH just fine, I even published the tags myself with SSH later via git manually. This is the error in question when Abra attempts to publish the tags: > ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

decentral1se added the

bug

label 2025-11-09 07:58:54 +00:00

decentral1se commented

2025-11-09 08:00:46 +00:00

@pharaohgraphy thanks for raising, do you have any --debug logs?

abra only supports ssh key auth, no password auth. abra will rely on whatever ssh picks up on the CLI, so if you're passing -p XXX or any options, you'd need to specify those in your ~/.ssh/config for abra to understand them.

This issue isn't that actionable now but hopefully you can get some info back and we can sort this out 🙏

@pharaohgraphy thanks for raising, do you have any `--debug` logs? `abra` only supports ssh key auth, no password auth. `abra` will rely on whatever `ssh` picks up on the CLI, so if you're passing `-p XXX` or any options, you'd need to specify those in your `~/.ssh/config` for `abra` to understand them. This issue isn't that actionable now but hopefully you can get some info back and we can sort this out 🙏

decentral1se commented

2025-11-09 10:03:50 +00:00

We've heard from Bonfire folx that they even had to add a section on this SSH config stuff:

https://docs.bonfirenetworks.org/deploy.html

People just kept running into it.

We've heard from Bonfire folx that they even had to add a section on this SSH config stuff: > https://docs.bonfirenetworks.org/deploy.html People just kept running into it.

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#724