-
-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permission denied (publickey). fatal: Could not read from remote repository. #46
Comments
This sounds like an issue with your configuration and not the repository itself. |
Config prob as in?
What cn i do?
…On Fri, Feb 17, 2017 at 11:26 AM, yburyug ***@***.***> 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
<#46 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APayeuCtOj2cOLGdXnO7TDYV1dHrRB1Fks5rdTZ8gaJpZM4MD41G>
.
|
It seems as if you removed the origin remote when you met to remove the directory that conflicted with your clone. Try this:
and see if it works. There seem to be local conflicts. |
still i have an error for Please make sure you have the correct access rights |
I have to, but how can I solve it |
Use HTTPS one and reset your git |
I resolved this error by changing ssh to http from git repos |
i resolved this error by using https instead of ssh |
i use https but still have the same issue... |
my too |
I solved same problem by adding below lines to
Note that if you use forward slashes it works in |
update your git version |
Solution is so simple, Use you can also clone |
bash.exe"-3.1$ git push -f origin master Please make sure you have the correct access rights |
this works:) |
its not working still it show same error |
I solved the same problem by replacing origin with the url of the repo |
After days of attempting different solutions this worked for me, thanks |
thanks it works for me |
Added
in was the right thing to do for me Hope this help |
I have just fixed the issue by following these steps : |
Open command prompt as administration and run below command |
1 similar comment
Open command prompt as administration and run below command |
Thanks shivagh514. $ git push -u origin master Please make sure you have the correct access rights have fixed the issue by following these steps : |
I had to change the URL |
I'm also using a ~/.ssh/config file and @endo64's suggestion of
I'd forgotten to check and put appropriate permissions on the 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. |
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 |
Some repository required to fork for having required permission to push to it by creating some feature branch. |
If you are contributing to some other account repository then note this 2 things -
|
Repository "......" doesn't exist |
In my case, the ssh agent was not running on my server.
|
suggestion of ssh -vvv [email protected] really helped me. In my case I have resolved this issue by keeping the key name as "id_rsa" which is default. While generating the New Key on CPanel => Manage SSH Key I had kept the keyname as my projectname. That was causing the issue. One thing we should keep in mind that Either use the default "id_rsa" while generating SSH Key or Add the custom key name on ssh directory Thanks everyone for the help. |
Warning: Permanently added the RSA host key for IP address '64:ff9b::dea:b066' to the list of known hosts. |
while push I used
Now on another server after .. (" git pull origin master Please make sure you have the correct access rights |
This worked for me. |
git clone -b Termux-Support-Branch https://github.com/DarkSecDevelopers/HiddenEye.git Help |
thank you its working for me |
Thank you. |
thak you so much, it really worked, but, just curiose, how did you get to that solution? |
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)
$
The text was updated successfully, but these errors were encountered: