권한 거부 (공개 키) 치명적 : 원격 저장소에서 읽을 수 없습니다.

권한 거부 (공개 키) 치명적 : 원격 저장소에서 읽을 수 없습니다. Git 저장소를 복제하는 동안

---

Git 저장소를 복제 할 수 없으며이 오류가 발생합니다.

krishna.soni@KRISHNACHANDRAS /c/Projects $ git clone http://stage.abc.com:10088/pqr
http://<url>/<repository> Cloning into '<repository>'... fatal: could not read Username for 'http://<url>': No such file or directory

내가 읽은 의 Bitbucket, Windows 및 "치명적인를 : 비밀번호를 읽을 수 없습니다" , 여전히 문제가 있습니다.

더 진행했지만 지금이 오류가 발생합니다.

sh.exe": chown: command not found

krishna.soni@KRISHNACHANDRAS /c
$ git clone ssh://krishna.sonipayu.in@stage.payupaisa.
/projects
Cloning into 'C:/projects'...
Permission denied (publickey).
fatal: Could not read from remote repository.

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

> krishna.soni@KRISHNACHANDRAS /c
>     $ git clone ssh:<url>
>     ts
>     Cloning into 'C:/projects'...
>     Permission denied (publickey).
>     fatal: Could not read from remote repository.

Please make sure you have the correct access rights

저장소가 존재합니다.

---

Windows 7 문제가 아닌 권한 문제처럼 보입니다.

ssh 키가 인증되지 않았습니다 Permission denied (publickey).

공개 ssh 키를 생성하고 Git 리포지토리 관리자에게 ssh공개 키 추가를 요청해야합니다.

이를 수행하는 방법에 대한 정보 : ssh 키 저장 실패

---

여기에 와서 리포지토리를 가져 오려고하지만 프로토콜 (ssh / https)에 신경 쓰지 않는 사람들 의 경우 ssh 대신 https 를 사용 하고 싶을 수도 있습니다 (지원되는 경우).

예를 들어

git clone https://github.com/%REPOSITORYFOLDER%/%REPOSITORYNAME%.git

대신에

git clone git@github.com:%REPOSITORYFOLDER%/%REPOSITORYNAME%.git

---

SSH를 생성 한 후 Bitbucket 계정이나 SSH를 추가 한 후에도 액세스 관련 문제가 여전히있는 경우 GitBash, OSX 또는 Linux의 터미널에서 다음을 수행해야합니다.

# Lists already added identities (‘ssh keys’)
ssh-add -l

그런 다음 키가 표시되지 않으면 다음과 같이 추가하십시오 ( identity실명으로 교체 ).

# Add a new identity
ssh-add ~/.ssh/identity

이것은 나를 위해 일했습니다.

---

나는 GitHub 와 같은 문제에 직면했다 . 해결하기 쉽습니다.

1. 다음에 설명 된대로 컴퓨터에서 SSH 키를 생성하십시오. SSH 키 생성 .
2. GitHub 계정에 로그인하십시오 : GitHub Login .
3. 계정에서 새로 생성 된 SSH 키 : 내 계정 SSH 키를 추가하십시오 .
4. git clone프로젝트를 다시 시도하십시오 .

---

나는 또한 같은 문제에 직면했다. 나는 다음을했고 그것이 나를 위해 일했다 :

1. Windows의 GIT GUI 클라이언트에서 키를 생성하십시오. 이 키를 클립 보드에 복사하십시오.
2. bitBucket/git 웹 사이트에서 계정을 열고이 키를 프로필에 추가하십시오. 이런 식으로, 서버는 귀하가 합법적 인 시스템에서 액세스하는 합법적 인 사용자임을 알고 있습니다.
3. 그게 다야. 이후 모든 푸시 명령이 작동했습니다.

---

Mac 에서이 문제가 발생했습니다 .Git 저장소에 액세스하도록 SSH를 올바르게 설정하는 동안 다시 시작한 후 (및 Mac이 스탠드 오프 상태 인 경우) 모든 자격 증명이 제거되었습니다. 분명히 어떤 이유로 pub 키가 644로 설정되어 키 체인에서 제거되었습니다. 읽으려면 :

• chmod 600 공개 키
• ssh-add ~/.ssh/[your private key]-아이디가 추가되었음을 표시해야합니다. 원하는 키 파일은 .pub 확장자가없는 파일입니다.
• ssh-add -l 새로 추가 된 신분을 보여줘

편집 : 분명히 MacOS는 키를 제거하는 경향이 있습니다-High Sierra 업데이트를 다운로드 한 후 (아직 설치하지 않았습니다) 내 키가 제거되어 다음을 통해 다시 추가해야했습니다 ssh-add

---

Github (또는 Bitbucket)은 서버에서 ssh 키를 찾을 수 없습니다.

계정 설정에 키를 추가하기 만하면됩니다.

---

저에게 저의 저장소에서 복제 하고 싶을 때 "Permission denied (publickey) fatal : 원격 저장소에서 읽을 수 없습니다"전에 같은 메시지가 나타났습니다. 내 경우의 해결책은 복제 전에 sudo를 사용하지 않는 것입니다.

---

오류가 발생했습니다 ...

Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

... 노트북이 나쁜 Windows 10 업데이트로 사망하고 공장 설정으로 돌아간 후 Git Bash 프롬프트에서 Bitbucket으로 연락하려고 할 때. 백업에서 모든 ssh 파일을 복원했습니다.

컴퓨터를 다시 빌드 한 후 오류의 원인이 Windows 계정 이름과 일치하지 않는 것으로 나타났습니다. 공개 키 파일 id_rsa.pub은 Windows 계정 이름 @과 기호, 컴퓨터 이름으로 구성된 쉽게 읽을 수있는 문자열로 끝나는 것을 알았습니다 .

컴퓨터를 처음 설정할 때 중간 이니셜을 포함하여 Windows 계정 이름을 만들었지 만 컴퓨터를 공장 설정으로 재설정하면 새로운 DevOps 직원이 중간 이름없이 내 계정 이름을 만들었습니다.

To resolve the issue, I simply edited my public key file id_rsa.pub and removed the middle initial in my name at the end. I had stuck with the same computer name so that was okay. I copied the file contents to the Windows clipboard. I then signed into Bitbucket, went to Bitbucket Settings under my avatar, and added a new public key where I pasted in the new contents.

Back at the Git Bash prompt, I confirmed that it now worked by entering the command...

ssh -T git@bitbucket.org

...and I got back a message that I was signed in.

---

If you generate new public ssh key and inserted it to bitbucket or github and

it not helped - please try to restart your PC. It helped me!!

---

You need to create a new ssh key by running ssh-keygen -t rsa.

---

I faced the same issue while running git clone command from windows command line. But the command runs successfully from Git Bash.

---

In macOS / Linux (Ubuntu):

1. To Authenticate you need to add your public part of your SSH key pair to bitbucket from within your user settings: User Settings --> SSH keys

You will find the said public part in your ~/.ssh directory, usually id_rsa.pub . note the .pub part of the file name for Public. it will help you to generate one if you don't already have one

You are not done yet ...

2. You need to let your system know what key to use with which remote host, so add these lines to your ~/.ssh/config file

Host bitbucket.org
 IdentityFile ~/.ssh/PRIVATE_KEY_FILE_NAME

Where PRIVATE_KEY_FILE_NAME is the name of private part of your SSH key pair, if you haven't messed with it, usually its default name is : id_rsa in this case replace PRIVATE_KEY_FILE_NAME above with id_rsa(the private key DOES NOT have a .pub extension)

---

If all fails, as was the case with me, Uninstall GIT, reinstall. For some reason this fixes.

P.S.

1. I tried generating new Keys and Updating at SSH public keys
2. Also tried deleting all keys and tried to create a fresh key.
3. And NO, nothing wrong with my .gitconfig

---

Useful thread and I don't bring much new to the table. The step I took is also part of the description Maxime helpfully points to but some may overlook it. The section is Adding your SSH key to the ssh-agent.

I had already generated my ssh-key but after a reboot I was unable to clone one of my own repositories.

I had to start the ssh-agent and add the private key to this agent in order to clone.

eval $(ssh-agent -s)
ssh-add ~/.ssh/id_rsa

---

I had the similar issue. I change the ssh keys and restarted and tried all other 'n' solutions. But the actual issue for me was our gitlab default protocol changed from ssh to https.

check the remote url with

git remote -v

change the remote url

git remote set-url origin https://URL

---

While cloning, I had a similar issue [ my ERROR: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights .. etc ]

-- I was using bitBucket/UBUNTU14.04 in my case, but ALREADY had a set of key files that I had previously generated AND I had changed the name of the files. I simply COPIED the files to the standard id_rsa & id_rsa.pub name format. I then re-ran the command with out issue.

OBTW: I could have also used the password prompt by using the HTTP style clone.

---

I had the same error. My solution was to logout and login again as my ssh-agent had become out of sync with the remote ssh key.

Adding this here just in case anyone has seen that the other answers don't seem to apply to their situation.

---

I had a similar problem on linux. I solved the problem by logging into the github server and creating a deploy key. That's under settings for the repository. Then, I copied and pasted my public key (which is usually in ~/.ssh/id_rsa.pub, but your configuration might be different). There is a check box to give this key write access. Click on it (unless you are using git to deploy only, in which case, don't click on it).

---

I was facing the same issue while setting up ssh for gitlab. I already have ssh for github and i could not overwrite that. The steps that worked for me are :

1. Generate SSH with new path and add it to ssh list ssh-add /path/to/new/id_rsa.
2. Create a file named config in ~/.ssh/ using. I used vi ~/.ssh/config/.
3. Add this to the newly created file

# GitLab.com server Host gitlab.com RSAAuthentication yes IdentityFile /path/to/new/id_rsa

4. Save and quit.

After that restart the terminal and try pushing, it should work

---

If you want to clone open source projects to submit a Pull Request:

I wanted to clone an open source project so I could submit some pull requests. The problem was that I didn't have permissions from the owner of the project. No matter, since my intention was to submit a PR, here is a viable alternative:

My solution:

1. Fork Repository

2. Then clone from your forked repository.

3. Work on your features and then submit a pull request.

---

fix for hub cli tool:

• git config --global hub.protocol https for long term
• git remote add OOPS https://github.com/isomorphisms/go.git && git push OOPS for immediate fix

---

This error occurs with the hub command line tool because of their wrong default hub.protocol git-config value. They set repos to

git://github.com/schacon/ticgit.git

instead of what github actually accepts, namely https://github.com/schacon/ticgit.git.

---

Reading LESS=+/"HTTPS instead" man hub will explain where the above "long-term fix" command comes from.

---

You can try adding your ssh key to your private keychain. It worked for me

ssh-add -K ~/.ssh/[your-private-key]

---

It may be stupid but it happened to us:

If you are using bitbucket and Sourcetree and you just copy paste the clone URL to the new repo dialog it will show the same error when pulling or pushing.

Make sure you delete the 'git clone' stuff before the URL.

참고URL : https://stackoverflow.com/questions/21255438/permission-denied-publickey-fatal-could-not-read-from-remote-repository-whil