Skip to main content

이 버전의 GitHub Enterprise Server는 2023-09-25. 중요한 보안 문제에 대해서도 패치 릴리스가 이루어지지 않습니다. 성능 향상, 향상된 보안, 새로운 기능을 위해 최신 버전의 GitHub Enterprise로 업그레이드합니다. 업그레이드에 대한 도움말은 GitHub Enterprise 지원에 문의하세요.

오류: 키가 이미 사용 중임

이 오류는 이미 다른 계정 또는 리포지토리에 추가된 키를 추가 하려고 할 때 발생합니다.

Finding where the key has been used

To determine where the key has already been used, open a terminal and type the ssh command. Use the -i flag to provide the path to the key you want to check:

$ ssh -T -ai ~/.ssh/id_rsa git@HOSTNAME
# Connect to your GitHub Enterprise Server instance using a specific ssh key
> Hi USERNAME! You've successfully authenticated, but GitHub does not
> provide shell access.

The username in the response is the account on your GitHub Enterprise Server instance that the key is currently attached to. If the response looks something like "username/repo", the key has been attached to a repository as a deploy key.

To force SSH to use only the key provided on the command line, use -o to add the IdentitiesOnly=yes option:

ssh -v -o "IdentitiesOnly=yes" -i ~/.ssh/id_rsa git@HOSTNAME

Fixing the issue

To resolve the issue, first remove the key from the other account or repository and then add it to your account.

If you don't have permissions to transfer the key, and can't contact a user who does, remove the keypair and generate a brand new one.

Deploy keys

Once a key has been attached to one repository as a deploy key, it cannot be used on another repository. If you're running into this error while setting up deploy keys, see "Managing deploy keys."