GitHub Error Message - Permission denied (publickey)

GitHub isn't able to tướng authenticate you. So, either you aren't setup with an SSH key, because you haven't mix one up on your machine, or your key isn't associated with your GitHub trương mục.

You can also use the HTTPS URL instead of the SSH/git URL to tướng avoid having to tướng khuyến mãi with SSH keys. This is GitHub's recommended method.

Further, GitHub has a help page specifically for that error message, and explains in more detail everything you could kiểm tra.

To solve it:

1. You should have a public key in your trang chủ directory, thus print the nội dung of your public key, in Linux distro run rẩy for example cat ~/.ssh/id_rsa.pub (if the prior doesn't work, kiểm tra the keys inside ~/.ssh/ with .pub extension)

2. Add the nội dung of such a public key to tướng your Github account: click your profile photo -> Settings-> SSH and GPG keys -> New SSH key or Add SSH key

I know about this problem. After add ssh key, add you ssh key to tướng ssh agent too (from official docs

eval `ssh-agent -s`
ssh-add ~/.ssh/id_rsa

After it all work fine, git can view proper key, before couldn't.

You should replace id_rsa with your key.

Example: ssh-add ~/.ssh/id_rsa => ssh-add ~/.ssh/id_ed25511.pub

Did you create a config tệp tin in your ~/.ssh directory? It should have contents lượt thích these:

Host github.com 
 IdentityFile ~/.ssh/github_rsa

Assuming that you created an ssh key named github_rsa

and uploaded it to tướng GitHub...

NOTE: You must follow this way of explicit configuration if you have more phàn nàn 1 key (2 and more) in your ~/.ssh/ directory. If you don't specify key this way, then first key in order is taken and used for github authentication, ví it depends on the key tệp tin name then.

This happened to tướng bu. For some reason my origin got messed up without my realizing it:

Check if your settings are still correct

git remote -v

the url needs to tướng be something lượt thích ssh://[email protected]/YourDirectory/YourProject.git; if you don't see [email protected], use

git remote set-url origin git://github.com/YourDirectory/YourProject.git

to mix it right. Or you could use the github phầm mềm to tướng kiểm tra and mix the Primary Remote Repository url in the settings panel of your particular repository.

Issue solved if you change the ssh access to tướng https access to tướng the remote repository:

git remote set-url origin https_link_to_repository

git push -u origin master

Assuming you are connecting GitHub over SSH, you can run rẩy below command to tướng confirm this.

$git config --get remote.origin.url

If you get a result has following format [email protected]:xxx/xxx.github.com.git, then you should tự the following.

Generate a SSH key(or use existing one). if you had one, you just need to tướng add your key to tướng the ssh-agent (step 2)and to tướng your GitHub account(step 3).

below are for those who don't have SSH key.

Step 1 Generating public/private rsa key pair.

$ssh-keygen -t rsa -b 4096 -C "[email protected]"

You'll be asked to tướng confirm where to tướng save the SSH key and what passphrase you want to tướng use.

Step 2 Add your key to tướng the ssh-agent

• Ensure ssh-agent is enabled

  $eval "$(ssh-agent -s)"

• Add your SSH key to tướng the ssh-agent:

  $ssh-add ~/.ssh/id_rsa

Step 3 Add your SSH key to tướng your account

$sudo apt-get install xclip

$xclip -sel clip < ~/.ssh/id_rsa.pub

Then add the copied key to tướng GitHub

Go to tướng Settings->SSH keys(Personal settings side bar)->Add SSH key->fill out form(key is on your clipboard, just use ctrl+v)->Add key

After going through above steps, you should solve the permission problem.

Reference Link: Generating SSH keys.

answered Aug 21, 2017 at 10:09

Badr BellajBadr Bellaj

12.8k3 gold badges45 silver badges47 bronze badges

First, we need to tướng kiểm tra for existing ssh keys on your computer. Open up Terminal and run:

ls -al ~/.ssh

#or

cd ~/.ssh
ls

and that will lists the files in your .ssh directory

And finally depending on what you see (in my case was):

 github_rsa  github_rsa.pub known_hosts

Just try setting up your RSA and hopefully that will solve your "git push origin" issues

$ ssh-keygen -lf ~/.ssh/github_rsa.pub

NOTE: RSA certificates are keys-paired ví you will have a private and a public certificate, private will not be accessible for you since it belongs to tướng github (in this case) but the public is the one you might be missing when this error happens (at least that was my case, my github trương mục or repo got messed up somehow and i had to tướng "link" the public key, previously generated)

this worked for me:

1- remove all origins

git remote rm origin  

(cf. https://www.kernel.org/pub/software/scm/git/docs/git-remote.html)

*remote : "Manage the mix of repositories ("remotes") whose branches you track.

*rm : "Remove the remote named . All remote-tracking branches and configuration settings for the remote are removed."

2- kiểm tra all has been removed :

git remote -v  

3- add new origin master

git remote add origin [email protected]:YOUR-GIT/YOUR-REPO.git

that's all folks!

If you having issues to tướng make connection with your enterprise Github trương mục then follow the below steps

Solution #1

ERROR: [email protected]: Permission denied (public key). fatal: Could not read
from remote repository. Please make sure you have the correct access
rights

Solution (OSX)

• Open your terminal and follow below commands

• $ cd ~

• $ sudo su

• $ ssh-keygen

  • Enter tệp tin in which to tướng save the key (/var/root/.ssh/id_rsa): $ id_rsa
  • Enter passphrase (empty for no passphrase): $ hit enter
  • Enter same passphrase again: $ hit enter

• $ cd ~/.ssh

• $ cat id_rsa.pub

• copy display nội dung.

• Open GitHub click your profile icon settings>SSH and GPC Keys

• Click on the new ssh key button

• enter any title and key that you copied

• check now your issue is resolved

Solution #2

ERROR 2: remote: Password authentication is not available for Git operations.
remote: You must use a personal access token or SSH key.
remote: See https://github.compnay.com/settings/tokens or https://github.compnay.com/settings/ssh
fatal: unable to tướng access 'https://github.company.com/repo/app.git/': The requested URL returned an error: 403

Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.

https://namespaceit.com/blog/remote-support-for-password-authentication-was-removed-on-august-13-2021-please-use-a-personal-access-token-instead

answered May 29, 2021 at 14:03

DamikaDamika

7822 gold badges8 silver badges19 bronze badges

I think i have the best answer for you, your git apps read your id_rsa.pub in root user directory

/home/root/.ssh/id_rsa.pub

That's why your key in /home/your_username/.ssh/id_rsa.pub can't be read by git. So you need to tướng create the key in /home/root/.ssh/

$ sudo su
$ ssh-keygen
$ cd ~/.ssh
$ cát id_rsa.pub

Then copy the key in your github trương mục. It's worked for bu. You can try it.

answered Jun 10, năm trước at 21:07

Rose PerroneRose Perrone

63.3k60 gold badges213 silver badges248 bronze badges

answered Jan 26, năm nhâm thìn at 15:19

N. OsilN. Osil

5047 silver badges13 bronze badges

I was using github earlier for one of my php project. While using github, I was using ssh instead of https. I had my machine mix up lượt thích that and every time I used to tướng commit and push the code, it would ask bu my rsa key password.

After some days, I stopped working on the php project and forgot my rsa password. Recently, I started working on a java project and moved to tướng bitbucket. Since, I had forgotten the password and there is no way to tướng recover it I guess, I decided to tướng use the https(recommended) protocol for the new project and got the same error asked in the question.

How I solved it?

1. Ran this command to tướng tell my git to tướng use https instead of ssh:

   git config --global url."https://".insteadOf git://
   

2. Remove any remote if any

   git remote rm origin
   

3. Redo everything from git init to tướng git push and it works!

PS: I also un-installed ssh from my machine during the debug process thinking that, removing it will fix the problem. Yes I know!! :)

OK there are few solutions to tướng this one, some of them might already been mentioned but just to tướng keep them together:

• make sure you keys are present, by mặc định another ~/.ssh/ thư mục, i.e. id.rsa and id.rsa.pub

• make sure the keys have correct permissions, you can run rẩy chmod:

  chmod 600 ~/.ssh/id_rsa

  chmod 644 ~/.ssh/id_rsa.pub

• make sure the nội dung of you public key (id_rsa.pub) matches the one uploaded in the remote repository configuration

• Finally fix the problems with ssh agent: ssh-add

Some more info: https://itcodehub.blogspot.com/2015/01/ssh-add-problems-with-ssh-agent-and.html

answered Feb 2, 2017 at 15:28

Allow write access for the key (identity) and then click Add key

^{If on Windows kiểm tra for more details in Using Github via SSH.}

answered Dec 24, năm nhâm thìn at 10:10

If you have already created an SSH key and are still getting the error it is because you need to tướng give the user permissions to tướng read and write to tướng the thư mục you are cloning into. To tự this, sudo chmod 777 ". Of course, this is after you have generated an SSH key and you are still getting this error. Hope this helps future users.

Edit

To add on to tướng this use admin in Windows if you're using the git bash

TLDR:

1. make sure you have write access to tướng the repo (configure it from the repo's settings).
2. make sure the public key is in the SSH and GPG keys of your github trương mục.

For bu, this error usually occurs when I try to tướng clone some repo from a newly installed machine. When receiving a request, github will first kiểm tra the public key hash. If the public key does not match any user, github will reject this request. This case is common if the machine is new and your ssh key is newly generated.

Also in ubuntu, even though there was already SSH key entered in settings in BitBucket, I got this problem. The reason was, I was trying the following:

sudo git push origin master

Not sure why, but it got solved by using

git push origin master

No sudo used.

I was having a similar problem to tướng @Batman. However, because I was running this under /usr/local/src/projectname, running without sudo was not an option.

Just add the -E flag to tướng preseve the environment (your ~/.ssh/ path).

$ sudo -E git clone git@your_repo

From man sudo:

-E, --preserve-env Indicates to tướng the security policy that the user wishes to tướng pre‐ serve their existing environment variables. The security policy may return an error if the user does not have permis‐ sion to tướng preserve the environment.

If you are using Widows-10, follow this instruction. It works for bu.

1. Open terminal as administrator

2. run this command: "ssh-keygen". It generate a ssh key and will show the thư mục where it has been created. Check my image

3. copy the generated "ssh key"

4. go to tướng your github profile ---> settings --> Click SSH and GPH --> Click ""New SSH Key Button" and paste the "ssh key" and finally "clickthe add Button"

In case somebody else needs this. I created an ssh key with a different name lượt thích ar-2022-ssh in the user's .ssh thư mục. The problem with this is that Checking for existing SSH keys specifies that supported public keys for GitHub are one of the following.

id_rsa.pub
id_ecdsa.pub
id_ed25519.pub

Once I changed my ssh key name to tướng one of those when generating a key, it worked connecting to tướng GitHub

1. Check for existing SSH keys:

ls -al ~//.ssh/

2. Generate a new SSH key:

ssh-keygen -t ed25519 -C ""

3. Add your SSH key to tướng ssh agent:

eval "$(ssh-agent -s)"

ssh-add ~/.ssh/id_ed25519

4. Add your public SSH key to tướng your GitHub account:

cat < ~/.ssh/id_ed25519.pub

answered Jun 11, 2023 at 17:14

answered Jul 30, năm ngoái at 3:24

answered Dec 8, năm nhâm thìn at 10:52

JoomlerJoomler

2,7983 gold badges32 silver badges38 bronze badges