Skip to main content
설명서에 자주 업데이트를 게시하며 이 페이지의 번역이 계속 진행 중일 수 있습니다. 최신 정보는 영어 설명서를 참조하세요.

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

관리 콘솔에 대한 액세스 문제 해결

관리 콘솔에 대한 액세스 문제를 해결할 수 있습니다.

About problems with Management Console access

If you experience problems accessing the Management Console, you can try the following troubleshooting steps.

Unlocking the Management Console after failed login attempts

The Management Console locks after ten failed login attempts are made in the span of ten minutes. You must wait for the login screen to automatically unlock before attempting to log in again. The login screen automatically unlocks as soon as the previous ten minute period contains fewer than ten failed login attempts. The counter resets after a successful login occurs.

To immediately unlock access to the Management Console, use the ghe-reactivate-admin-login command via the administrative shell. For more information, see "Command-line utilities" and "Accessing the administrative shell (SSH)."

Troubleshooting failed connections to the Management Console

If you cannot connect to the Management Console on your GitHub Enterprise Server instance, you can review the following information to troubleshoot the problem.

Error: "Your session has expired" for connections through a load balancer

If you access your GitHub Enterprise Server instance through a load balancer and connections to the Management Console fail with a message that your session has expired, you may need to reconfigure your load balancer. For more information, see "Using GitHub Enterprise Server with a load balancer."