How to solve Permission denied publickey error when using Git

Question

I m on Mac Snow Leopard and I just installed git   I just tried   git clone git thechaw com cakebook git   but that gives me this error   Initialized empty Git repository in   Users username Documents cakebook  git   Permission denied  publickey   fatal  The remote end hung up unexpectedly   What am I missing  I ve also tried doing ssh-keygen with no passphase but still same error

User · Answer

On Windows  make sure all your apps agree on HOME   Msys will surprisingly NOT do it for you  I had to set an environment variable because ssh and git couldn t seem to agree on where my  ssh directory was

User · Answer

In my case  I have reinstalled ubuntu and the user name is changed from previous  In this case the the generated ssh key also differs from the previous one   The issue solved by just copy the current ssh public key  in the repository  The key will be available in your user s  home  ssh id rsa pub

User · Answer

In my MAC I solved this with   cp    ssh github rsa    ssh id rsa   For some reason my git stopped to find the private key in the github rsa file  This happened in a specific repo  I mean that in other repositories git kept working normally   I think it s a bug   I could find this behavior running ssh -vT git github com

User · Answer

I also had the exact same error   The problem was that when copying the public key into BitBucket  in my case   a non-visible newline at the end was copy pasted   So when copying the public key  first copy it to notepad  remove the empty line at the end  copy it  and paste it

User · Answer

This strange error  in my case was a symptom of gnome-keyring-daemon incorrectly naming the key to which it required a password   I follow the steps outlined here  and entered the password via the terminal  The error  aka the confounding GUI interface  was resolved  See  https   askubuntu com questions 3045 how-to-disable-gnome-keyring

User · Answer

The basic GIT instructions did not make a reference to the SSH key stuff  Following some of the links above  I found a git help page that explains  step-by-step  exactly how to do this for various operating systems  the link will detect your OS and redirect  accordingly    http   help github com set-up-git-redirect   It walks through everything needed for GITHub and also gives detailed explanations such as  why add a passphrase when creating an RSA key   I figured I d post it  in case it helps someone else

User · Answer

Guys this is how it worked for me    Open terminal and go to user  See attached image  Open  ssh folder and make sure it doesn t have any file like id rsa or id rsa pub otherwise sometimes it wont properly rewrite files git --version  Check for git installation and version  git config --global user email  your email id  git config --global user name  your name  git config --list  make sure you have set your name  amp  email  cd    ssh ssh-keygen  it prompts for saving file  allow it cat    ssh id rsa pub   Access your public key  amp  copy the key to gerrit settings    Note  You should not be using the sudo command with Git  If you have a very good reason you must use sudo  then ensure you are using it with every command  it s probably just better to use su to get a shell as root at that point   If you generate SSH keys without sudo and then try to use a command like sudo git push  you won t be using the same keys that you generated

User · Answer

cd     cd  ssh   chmod 400 id rsa

User · Answer

The easiest solution to this  when you are trying to push to a repository with a different username is    git remote set-url origin https   USERNAME github com USERNAME PROJECTNAME git

User · Answer

This error can happen when you are accessing the SSH URL  Read Write  instead of Git Read-Only URL but you have no write access to that repo   Sometimes you just want to clone your own repo  e g  deploy to a server  In this case you actually only need READ-ONLY access  But since that s your own repo  GitHub may display SSH URL if that s your preference  In this situation  if your remote host s public key is not in your GitHub SSH Keys  your access will be denied  which is expected to happen   An equivalent case is when you try cloning someone else s repo to which you have no write access with SSH URL   In a word  if your intent is to clone-only a repo  use HTTPS URL  https   github com  user name   project name  git  instead of SSH URL  git github com  user name   project name  git   which avoids  unnecessary  public key validation     Update  GitHub is displaying HTTPS as the default protocol now and this move can probably reduce possible misuse of SSH URLs

User · Answer

It worked for me  ssh -i  your id rsa path  -T github github com

User · Answer

Note that  at least for some projects  you must have a github account with an ssh key   Look at the keys listed in your authentication agent  ssh-add -l     if you don t see any  add one of your existing keys with ssh-add  path to your key  eg  ssh-add    ssh id rsa      if you don t have any keys  first create one  See  http   rcsg-gsir imsb-dsgi nrc-cnrc gc ca documents internet node31 html or just google ssh-keygen   To verify that you have a key associated with your github account   Go to  https   github com settings ssh  You should see at least one key with a hash key matching one of the hashes you saw when you typed ssh-add -l just a minute ago   If you don t  add one  then try again

User · Answer

Are you in a corporate environment   Is it possible that your system variables have recently changed   Per this SO answer  ssh keys live at  HOMEDRIVE  HOMEPATH   ssh id rsa pub   So if  HOMEDRIVE  recently changed  git doesn t know where to look for your key  and thus all of the authentication stuff     Try running ssh -vT git github com   Take note of where the identity file is located   For me  that was pointing not to my normal  Users MyLogin but rather to a network drive  because of a change to environment variables pushed at the network level   The solution   Since my new  HOMEDRIVE  has the same permissions as my local files  I just moved my  ssh folder there  and called it a day

User · Answer

I have just experienced this issue while setting my current project  and none of the above solution works  so i tried looking what s really happening on the debug list using the command ssh -vT git github com  I notice that my private key filename is not on the list  so renaming the private key filename to  id rsa  do the job  hope this could help

User · Answer

I met the same issue because of I was thought the difference between SSH and HTTPS is   https   github com USERNAME REPOSITORY git  ssh   github com USERNAME REPOSITORY git  So I changed from HTTPS to SSH just by changing https    to ssh    nothing on the end of the url was changed   But the truth is   https   github com USERNAME REPOSITORY git  git github com USERNAME REPOSITORY git   Which means I changed ssh   github com USERNAME REPOSITORY git to git github com USERNAME REPOSITORY git it works   Stupid error but hope helps someone

User · Answer

I had to copy my ssh keys to the root folder  Google Cloud Compute Engine running Ubuntu 18 04  sudo cp    ssh    root  ssh

User · Answer

It worked for me   Your public key is saved to the id rsa pub file and is the key you upload to your account  You can save this key to the clipboard by running this      pbcopy  lt     ssh id rsa pub    copy the SSH key to the clipboard  return to the web portal  In the SSH Key field  paste your SSH key  In the Name field  provide a name for the key  save

User · Answer

I hit this error because I needed to give my present working directory permissions 700   chmod -R 700  home ec2-user

User · Answer

For me the problem was using sudo  sudo git clone git github com userName repo git was resulting in the error mentioned above  So to fix this I chown the folder I was trying to clone into sudo chown -R  USER  USER  var www iqge org html then using this git clone git github com userName repo git was successfully done

User · Answer

Possible that public private config is incorrect  please follow the steps to do it  execute command anywhere in window ssh-keygen -o -f    ssh id rsa  now go to the c   users xyz  ssh  and open the id rsa key  path can vary  now go to the gitlab and userprofile gt  setting gt ssh keys and add your key here  now try clone

User · Answer

Execute the terminal as admin   If the terminal can t see your  ssh it will return that error

User · Answer

I had a slight different situation  I was logged on to a remote server and was using git on the server  when I ran any git command I got the same message     Permission denied  publickey      fatal  The remote end hung up unexpectedly   The way I fixed it was by changing the file  etc ssh config on my Mac   from  ForwardAgent no    to   ForwardAgent yes

User · Answer

When ever I get a new computer at work or switch jobs these are steps I follow setup github access  Mac or Windows -Go to https   github  yourWorkDomain  com   navigate to    Settings   Developer Settings   Personal access tokens -Generate a new token -Set the token description and only check the    repo    box for scope  this will give you repo status  repo deployment  public repo     repo invite access  -After your are given the token  copy it  don t navigate away yet  confirm the next two steps work  -Try to clone the repo again using    https     -For the username use your Username -For the password  paste the token you copied -All future requests should work now without asking for your username and password

User · Answer

Steps for Mac    Switch user   sudo su - jenkins  Generate key   ssh-keygen -t rsa -b 4096 -C  username     Username is one with which you are using with jenkins  Copy generated public key  cat    ssh id rsa pub   Paste the key to git account   Settings -  SSH and CPG keys -  New ssh keys -  Enter name of the key  can be any  and paste the key to description

User · Answer

In addition to Rufinus  reply  the shortcut to copy your ssh key to the clipboard in Windows is    type id rsa pub   clip   Refs    Print to standard output Copy command line output to clipboard

User · Answer

First of all  I recommend checking some standard things like    login as the correct user in your system  have the right private key in the right location in your system  try to connect with the correct username  hostname  and port  have the public key in the right location  and for the right user  in the external server  restarted the ssh service at your computer     service ssh restart    or in another way depending on how you manage services in your system      It was enough for me

User · Answer

The github help link helped me sort out this problem  Looks like the ssh key was not added to the ssh-agent  This is what I ended up doing  Command 1  Ensure ssh-agent is enabled  The command starts the ssh-agent in the background  eval  quot   ssh-agent -s  quot   Command 2  Add your SSH key to the ssh-agent  ssh-add    ssh id rsa

User · Answer

I was getting the same error  My problem was mixing in sudo     I couldn t create the directory I was cloning into automatically without prefixing the git clone command with sudo   When I did that  however  my ssh keys where not being properly referenced     To fix it  I set permissions via chmod on the parent directory I wanted to contain my clone so I could write to it   Then I ran git clone WITHOUT a sudo prefix   It then worked   I changed the permissions back after that  Done

User · Answer

These are the steps I followed in windows 10  Open Git Bash   Generate Public Key  ssh-keygen -t rsa -b 4096 -C  quot youremailaddress xyz com quot    Copy generated key to the clipboard  works like CTRL C  clip  lt     ssh id rsa pub   Browser  go to Github   gt  Profile  gt  Settings   gt  SSH and GPG keys   gt  Add Key  Provide the key name and paste clipboard  CTRL V    Finally  test your connection  Git bash  ssh -T git github com    Thanks

User · Answer

I was able to get over this issue by following below steps in my ubuntu system  As i was experimenting with passwordless ssh to the system   sudo vi  etc ssh sshd config  1  Commented below        Change to no to disable tunnelled clear text passwords     PasswordAuthentication yes     PasswordAuthentication no ----  commented this    2  Then restarted the sshd daemon as below   service sshd restart

User · Answer

Visual guide  Windows  1 of 2  Git batch side 1 1  Open git batch  Download her   1 2  Paste the text below  Change to your GitHub account email    ssh-keygen -t rsa -b 4096 -C  quot your email example com quot    1 3  Press Enter  Accepts the default file location   1 4  Click Enter Twice  Or set SSH key passphrases - Gitbub passphrases docs   gt  Enter passphrase  empty for no passphrase    Type a passphrase   gt  Enter same passphrase again   Type passphrase again   1 5  The key generate   Your identification has been saved in  c Users user  ssh id rsa     1 6  Copy the SSH key to your clipboard    clip  lt     ssh id rsa pub 2 of 2  Github website user side Under user setting  SSH and GPG keys   gt  New SSH key   Paste the code from step 1 6  Done      If someone doesn t want to use SSH use HTTPS    Github docs  https   docs github com en github authenticating-to-github connecting-to-github-with-ssh

User · Answer

Got same error report   Fixed with using HTTP instead  Since I don t want set  SSH keys  for a test PC   Change URL to HTTP when clone   git clone https   github com USERNAME REPOSITORY git   My problem is a little bit different  I have URL set when adding a existing local repo to remote  by using   git remote add origin ssh   github com USERNAME REPOSITORY git   To fix it  reset URL to HTTP   git remote set-url origin https   github com USERNAME REPOSITORY git   BTW  you may check your URL using command   git remote -v origin  https   github com USERNAME REPOSITORY git  fetch  origin  https   github com USERNAME REPOSITORY git  push    Hope this will help some one like me   D

User · Answer

If you have more than one key you may need to do  ssh-add private-keyfile

User · Answer

Let me share my experience too    I was trying to clone some project from the Gerrit repo where I got my public keys in account settings   On the first attempt to make git clone I got the following error   Unable to negotiate with XX XX XX XX port XXX  no matching key exchange method found  Their offer  diffie-hellman-group1-sha1   I figured out that I need to pass the SSH option -oKexAlgorithms  diffie-hellman-group1-sha1 somehow to git clone   Hopefully GIT SSH COMMAND environment variable did the job   export GIT SSH COMMAND  ssh -oKexAlgorithms  diffie-hellman-group1-sha1    But git clone still didn t start to work   Now it throws the  on topic    Permission denied  publickey     I got already SSH keys and didn t want to regenerate them  I checked plain SSH connection to the host and it was ok           Welcome to Gerrit Code Review            Hi XXXXX  you have successfully connected over SSH     Unfortunately  interactive shells are disabled    To clone a hosted Git repository  use     git clone ssh   xxxxx xx xx xx xxx REPOSITORY NAME git   I was confused a bit  I started again and turned on the debug for SSH via -vvv option  And I saw the following   debug1  read passphrase  can t open  dev tty  No such device or address   Possibly  it was an overhead for the GIT SSH COMMAND env variable - my key was secured with passphrase  and I entered it when I was checking the login to the git repo host    So  I decided to get rid of the phasphrase then  A simple command helped me   ssh-keygen -p   Then I entered my passphrase for the  old passphrase  and just hit ENTER twice on the  new passphare  to leave it empty i e  with no passphrase at all and to confirm my choice   After that I got the freshly cloned repo on my local disk

User · Answer

One of the easiest way      go to terminal-    git push  lt Git Remote path gt  --all

User · Answer

Its pretty straight forward  Type the below command   ssh-keygen -t rsa -b 4096 -C  youremailid yourdomain com    Generate the SSH key  Open the file and copy the contents  Go to GitHub setting page   and click on SSH key   Click on Add new SSH key  and paste the contents here  That s it    You shouldn t see the issue again

User · Answer

Use the ssh link from Github but make sure to not append it with ssh just use what the ssh tab on git hub gives you to clone your repo

User · Answer

Another possibility on Windows  which is not covered in any of these answers  and is not covered in the git or github docs on troubleshooting   git may be using a different openssh executable than you think it is   I was receiving the Permission denied  public key  error when trying to clone or pull from github and ssh dev azure com  and I d followed all the instructions and verified that my SSH keys were setup correctly  from SSH s standpoint  using ssh -vT git github com and ssh -vT git ssh dev azure com  And was still getting these errors   git github com  Permission denied  publickey   fatal  Could not read from remote repository   Please make sure you have the correct access rights and the repository exists    I eventually figured out that the problem is that Git for Windows  and Windows  both have their own versions of openssh  This is documented here  https   github com desktop desktop issues 5641  I was relying on the Windows ssh-agent service to store my ssh key passphrases  so git  with it s separate version of openssh  couldn t read my private keys  I consider it a bug that this error message is used - it s misleading   The fix was   git config --global core sshCommand   C  Windows System32 OpenSSH ssh exe     Or in your    gitconfig    core      sshCommand    C   Windows  System32  OpenSSH  ssh exe    Perhaps this will be fixed in git for Windows soon  but this is the 2nd time I ve wasted time on this issue

User · Answer

In MAC  go to Terminal  1  Navigate to Home Directory using command - cd    2  cd  ssh  amp  amp  ssh-keygen  For Defaults  click on Enter Return key for both inputs   Generating public private rsa key pair  Enter file in which to save the key   Users username  ssh id rsa         Enter passphrase  empty for no passphrase    Enter same passphrase again   Your identification has been saved in  Users usernmae  ssh id rsa    3  After that   Do  ls   you will find id rsa pub file   4  Copy the contents in the id rsa pub file  read using the cat command - cat id rsa pub   5  Navigate to BitBucket or any version tool which supports the SSH keys  Paste the contents using the Add Key Option  That s it  Try to commit and push now

User · Answer

If the user has not generated a ssh public private key pair set before  This info is working on theChaw but can be applied to all other git repositories which support SSH pubkey authentications   See gitolite  gitlab or github for example       First start by setting up your own public private key pair set  This   can use either DSA or RSA  so basically any key you setup will work    On most systems you can use ssh-keygen          First you ll want to cd into your  ssh directory  Open up the terminal and run            cd    ssh  amp  amp  ssh-keygen      Next you need to copy this to your clipboard          On OS X run  cat id rsa pub   pbcopy    On Linux run  cat id rsa pub   xclip   On Windows  via Cygwin Git Bash  run  cat id rsa pub   clip      Add your key to your account via the website    Finally setup your  gitconfig          git config --global user name  bob    git config --global user email bob        don t forget to restart your command line to make sure the config is reloaded             That s it you should be good to clone and checkout    Further information can be found at https   help github com articles generating-ssh-keys  thanks to  Lee Whitney   -  If the user has generated a ssh public private key pair set before   check which key have been authorized on your github or gitlab account settings determine which corresponding private key must be associated from your local computer   eval   ssh-agent -s    define where the keys are located    ssh-add    ssh id rsa

User · Answer

This works for me   ssh-add    ssh id rsa

User · Answer

I was struggling with same problem that s what i did and i was able clone the repo  I followed these procedure for iMac   First Step   Checking if we already have the public SSH key    Open Terminal  Enter ls -al    ssh to see if existing SSH keys are present    Check the directory listing to see if you already have a public SSH key Default public are one of the following d dsa pub id ecdsa pub id ed25519 pub id rsa pub  If you don t find then go to step 2 otherwise follow step 3  Step 2   Generating public SSH key   Open Terminal  Enter followong command with you valid email address that you use for github ssh-keygen -t rsa -b 4096 -C  your email example com  You will see following in terminal Generating public private rsa key pair  When it prompts to Enter a file in which to save the key   press Enter  This accepts the default file location  When it prompts to Enter a file in which to save the key   Users you  ssh id rsa    Press enter  Just press enter again  At the prompt  type a secure passphrase  Enter passphrase  empty for no passphrase    Type a passphrase  press enter if you don t want to Enter same passphrase again   Type passphrase again  press enter again   This will generate id rsa pub   Step 3  Adding your SSH key to the ssh-agent   Interminal type eval    ssh-agent -s   Add your SSH key to the ssh-agent  If you are using an existing SSH key rather than generating a new SSH key  you ll need to replace id rsa in the command with the name of your existing private key file  Enter this command   ssh-add -K    ssh id rsa   Now copy the SSH key and also add it to you github account    In terminal enter this command with your ssh file name pbcopy  lt     ssh id rsa pub This will copy the file to your clipboard Now open you github account Go to Settings   SSH and GPG keys   New SSH key Enter title and paste the key from clipboard and save it  Voila you re done

User · Answer

I was getting this error because I generated the ssh keys with the wrong email  I was able to connect using ssh  but not using git  The solution was to regenerate the keys using the main email address of my github account

User · Answer

I was getting a similar Permission denied  publickey  error when trying to run a makefile   As an alternative to the SSH steps above  you can Install the native GitHub for Mac application   Click Download GitHub for Mac from - https   help github com articles set-up-git platform-mac  Once you complete setup with your git hub account  I also installed the git hub command line tools but unsure if this step is required or not  then I received an email -   GitHub  A new public key was added to your account  and my error was fixed

User · Answer

More extensive troubleshooting and even  automated fixing can be done with    ssh -vT git github com   Source  https   help github com articles error-permission-denied-publickey

[git] How to solve Permission denied (publickey) error when using Git?

Examples related to git

Examples related to ssh

Examples related to ssh-keys

Examples related to public-key