You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi,
My work Win10 machine has a "mapped" Home drive, call it "H:". Due to some recent issues I had to delete my local "profile". Before I did the delete I copied the ".ssh" dir and other things off to the H drive for safe keeping. I now wonder if I can configure Sourcetree to look in that non-standard location for the ssh keys?
This isn't an answer but I had to do something... I moved the .ssh dir back from the mapped H drive mentioned above to my local "profile". I had to reestablish the remote info via:
git remote rename origin old-origin
git remote add origin git@gitlab.myCo.com:me/myProject.git
git push -u origin --all
git push -u origin --tags
Hi! Have you already tried the option 'Load an existing private key file' as shown in our documentation? Are you able to select your SSH key location?
Let us know!
Ana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, I have active ssh keys, this page seems to only tell me how to generate new ones.
My keys are not sitting is the "default" location that putty creates (C:\Users\me\.ssh). Instead, they are on a mapped drive (H:\.ssh). My guess is that Sourcetree only know to look in the .ssh directory in the user's home directory.
I have tried going to Tools -> Options and setting the "SSH Client Configuration" section but that has not worked.
I may have to move the .ssh dir back to the "normal" location
**Edit**
I have tried creating a windows "junction" to link to the mapped drive location. That is not working.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.