![]() ![]() So I made absolutely sure that I use the admin user in the remote URL - same problem. YES I CAN git clone, push, pull with users from command line, and I can also ssh to the server, although only with admin users (seems to be Synology's new standard). Event this post was no help - what am I doing wrong here? So I tried by generating a new key via GitKraken and installing it as described here, but nothing changed. I could clone and push elements via command prompt, no problem with git clone can clone/commit/pull via command prompt but when I do it via GitKraken, I get a "Configured SSH key is invalid" error. This fixed GitKraken for me.I'm trying use GitKraken with my existing git repository hosted on a Synology NAS (web-managed, if this can make a difference). Instead I selected "Use local SSH agent". Unlike Coming Sun's answer I already had a Private/Public key and didn't want to generate a new pair. Similar to Coming Sun's answer I went to GitKraken Preferences/Authentication/General. Please ensure that your key is valid and is an RSA-type key." GitKraken said "Configured SSH key is in an invalid format. I could still git push to first repo from terminal command line, manually entering passphrase. Public key file ~/.ssh/id_rsa.pub format is similar to Josh Patterson answer: ssh-rsa AAAAB3NzaC1yc2.8swZ0Ew=Īt some point gitKraken could no longer push to the first repo. On macOS I had a Private/Public key pair and GitKraken was sucessfully using it to push to a bitbucket repository. Update: I also had to include ssh-add -K ~/.ssh/id_rsa inside my ~/.bash_profile to make it load automatically, otherwise you'll have to run that command on every computer restart. Gitkraken will use your computers own ssh agent which we have configured to authenticate us successfully. ![]() Now when you do git fetch from terminal or do git fetch from Gitkraken, it should both work.Add your ~/.ssh/id_rsa.pub public key to your server (, azure devops, github or w/e).If you don't do this then Gitkraken will use it's own bundled ssh agent and I think this is what cause problem for most people This will tell Gitkraken to use my agent in step 2. Inside Gitkraken, go to "Preferences -> authentication.Do note here that it's an uppercase -K, which means that I want to store my passphrase too inside the local ssh agent, this will cause it to store my passphrase in the keychain so I dont need to re-enter it all the time, very neat! Run ssh-add -K ~/.ssh/id_rsa to save my identity inside my local ssh agent.This is what I did to solve it, from start, sitting on MacOS. I will still add some more information here, because I don't think any answer actually solves the problem all the way. Lots of answers already, and I think most of them are very helpful. This also seems to work on Ubuntu (18.04). It seems that on my mac if I don't run ssh-add -k ~/.ssh/id_rsa then I get errors about having a bad ssh key. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |