Permission denied (publickey). fatal: Could not read from remote repository.

[aasthabapna]

I am not able to run these commands. I tired cloning over https still same error

Administrator@aastha MINGW64 /g/All-Around-Apparel-master (master) $ git push Permission denied (publickey). fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

Administrator@aastha MINGW64 /g/All-Around-Apparel-master (master) $ git remote show origin Permission denied (publickey). fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

Administrator@aastha MINGW64 /g/All-Around-Apparel-master (master) $ git remote add origin [email protected]:DBegrajka/All-Around-Apparel.git fatal: remote origin already exists.

Administrator@aastha MINGW64 /g/All-Around-Apparel-master (master) $ git push origin master Permission denied (publickey). fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

Administrator@aastha MINGW64 /g/All-Around-Apparel-master (master) $ git pull origin master Permission denied (publickey). fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

Administrator@aastha MINGW64 /g/All-Around-Apparel-master (master) $ git remote add origin https://github.com/DBegrajka/All-Around-Apparel.git fatal: remote origin already exists.

Administrator@aastha MINGW64 /g/All-Around-Apparel-master (master) $ git clone https://github.com/DBegrajka/All-Around-Apparel.git fatal: destination path 'All-Around-Apparel' already exists and is not an empty directory.

Administrator@aastha MINGW64 /g/All-Around-Apparel-master (master) $ git remote rm origin git remote add origin ^C

Administrator@aastha MINGW64 /g/All-Around-Apparel-master (master) $

[ybur-yug]

This sounds like an issue with your configuration and not the repository itself.

[aasthabapna]

Config prob as in? What cn i do?

On Fri, Feb 17, 2017 at 11:26 AM, yburyug [email protected] wrote:

This sounds like an issue with your configuration and not the repository itself.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jkbrzt/cloudtunes/issues/46#issuecomment-280560636, or mute the thread https://github.com/notifications/unsubscribe-auth/APayeuCtOj2cOLGdXnO7TDYV1dHrRB1Fks5rdTZ8gaJpZM4MD41G .

[ybur-yug]

It seems as if you removed the origin remote when you met to remove the directory that conflicted with your clone. Try this:

$ cd
$ mkdir tmp
$ cd tmp
$ git clone <the repo>
$ cd <the repo>

and see if it works. There seem to be local conflicts.

[geesdiir]

still i have an error for Please make sure you have the correct access rights and the repository exists.

[MaxWillBeBest]

I have to, but how can I solve it

[tripulse]

Use HTTPS one and reset your git

[rameshrebari]

I resolved this error by changing ssh to http from git repos

[mnreddy1986]

i resolved this error by using https instead of ssh

[mrilyaskarimov]

i use https but still have the same issue...

[mohamedsami0]

i use https but still have the same issue...

my too

[endo64]

I solved same problem by adding below lines to C:\Users\myuser\.ssh\config file:

Host example.com
  AddKeysToAgent yes
  IdentityFile /D/Documents/PPK/myprivatekey.ppk

ssh -vvv [email protected] showed me some insights like the file name it tried to use, auth method it tries etc.

Note that if you use forward slashes it works in bash (mingw) but not in CMD and with back slashes it works in CMD but not in bash.

[farassharp]

update your git version

[Haritsinh]

Solution is so simple, Use https://github.com/wanted-repository.git version instead of [email protected]:wanted-repository.git .

you can also clone git@github which is SSH version but for that you have to generate ssh keys and have to set it in local environment and if you don't want to set up that then just use https version that's it.

[smasish]

bash.exe"-3.1$ git push -f origin master Permission denied (publickey). fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists. bash.exe"-3.1$ How to push my android code to a repository provided by another account? He provided me git repository to submit my android code but I can't push it to his repository. Plz help.

[adarshpandey]

Solution is so simple, Use https://github.com/wanted-repository.git version instead of [email protected]:wanted-repository.git .

you can also clone git@github which is SSH version but for that you have generate ssh keys and have to set it in local environment and if you don't want to set up that then just use https version that's it.

this works:)

[nerugattiraju]

its not working still it show same error

[aliana17]

I solved the same problem by replacing origin with the url of the repo git push https://github.com/reactjs/hi.reactjs.org.git master It worked for me.

[Jaliov]

After days of attempting different solutions this worked for me, thanks

[bhaveshrathod741]

I solved the same problem by replacing origin with the url of the repo git push https://github.com/reactjs/hi.reactjs.org.git master It worked for me.

thanks it works for me

[PhilippeDo]

Added

host my_host
     IdentityFile ~/.ssh/id_rsa

in /etc/ssh/ssh_config

was the right thing to do for me

Hope this help

[shivagh514]

I have just fixed the issue by following these steps : git remote rm origin // for removing the existing connection git remote add origin https://github.com/username/filename.git git push -u origin master

[ShahidHussainAbbasi]

Open command prompt as administration and run below command git push origin master --force

[ShahidHussainAbbasi]

Open command prompt as administration and run below command git push origin master --force

[Sumankkundu]

Thanks shivagh514. I have also faced the same problem:

$ git push -u origin master [email protected]: Permission denied (publickey). fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists._

have fixed the issue by following these steps : $ git remote rm origin

[nikhilkadu]

I had to change the URL git remote set-url origin <new_https_url>

[ErinKenna]

ssh -vvv [email protected] showed me some insights like the file name it tried to use, auth method it tries etc.

I'm also using a ~/.ssh/config file and @endo64's suggestion of ssh -vvv [email protected] really helped me.

debug1: Trying private key: /home/<user>/.ssh/<name_of_key_file>
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0664 for '/home/<user>/.ssh/<name_of_key_file>' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
Load key "/home/<user>/.ssh/<name_of_key_file>": bad permissions

I'd forgotten to check and put appropriate permissions on the key file. i.e. chmod 600 ~/.ssh/<name_of_key_file>

Trying ssh again, the next problem for me was that the private key file generated by PuttyGen was not an acceptable format. So I had to reload and export it as OpenSSH in PuttyGen and replace it in my .ssh dir.

Trying ssh again yielded, "You've successfully authenticated, but GitHub does not provide shell access."

At this point git clone using ssh worked for me.

[nilanjandutta]

change the origin master link from [email protected] to https://github.com , if confused simply copy the browser url link and save it as origin

[himharsh1997]

Some repository required to fork for having required permission to push to it by creating some feature branch.

[himanshu199728]

If you are contributing to some other account repository then note this 2 things -

1. You must have a public key set in your account for the collaboration process.
2. Fork before cloning the project.

[harshraj1234]

It seems as if you removed the origin remote when you met to remove the directory that conflicted with your clone. Try this:

$ cd
$ mkdir tmp
$ cd tmp
$ git clone <the repo>
$ cd <the repo>

and see if it works. There seem to be local conflicts.

Repository "......" doesn't exist