It’s been a few years since I’ve worked with Balena, so I’m still doing things the old way with git push. I my balena user name is jason10 but my github account is under drjasonharrison. I suspect that I after I imported keys from github I need to configure my ~/.ssh/config to help with the username.
Here’s the error message I get
Warning: Permanently added the ECDSA host key for IP address '3.221.16.120' to the list of known hosts.
############################################################################
None of the supplied SSH keys matched a known key for user `jason10`
Known ssh key fingerprints for `jason10`:
* 5813566518050886f8c87a1b5020526d
* fac74f3a74f24a353ac14fc13d23a5b0
Please make sure you've configured your keys correctly.
https://balena.io/docs/getting-started/#adding-an-ssh-key
############################################################################
jason10@git.balena-cloud.com: Permission denied (publickey,keyboard-interactive).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Is there a webpage that discusses the ~/.ssh/config for balena? Couldn’t find it in the docs or through google (with site:balena.io/docs). Will probably have to hit stackoverflow.
On the other hand, related with the current issue i understand that you are deploying a project from a drjasonharrison repo. And of course, you introduced your github public key from drjasonharrison on balenaCloud, right? could you please check on Settings > SSH keyshere?
Not sure you need anything else. Confirm me this, and i will try to reproduce myself
The corrected URL appears to be correct.
My balena account has an email of drjasonharrison but balena username jason10
I would have used the provided command from the “add release” dialog:
@jason10 after speaking with a colleague it looks like this is balena’s fault when this is run from specific OS. Out of curiosity are you running Fedora or similar?
Our temporary workaround that can be used while a definitive solution does not yet exist:
Either add PubkeyAcceptedKeyTypes +ssh-rsa to SSH configuration
or prefix your git commands with GIT_SSH_COMMAND="ssh -vvvv -oPubkeyAcceptedKeyTypes=+ssh-rsa" git push balena
or use a different algorithm for the key ( ecdsa or ed25519 should work fine)
Change .ssh/config to refer to the custom named identify file? e.g. id_balena / id_balena.pub
Let us know if that works! Thank you for your patience!
I just upgraded to Ubuntu 22.10 and out of nowhere started receiving the same message.
The bit that solved the annoying message was: PubkeyAcceptedKeyTypes +ssh-rsa in /etc/ssh/ssh_config
I know the topic is solved but just wanted to bump here to update and include the keywords in case someone gets the same error