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 the number of failed login attempts configured by your authentication policies. For more information, see "Managing access to the Management Console."
Unlocking the root site administrator account
If the root site administrator's Management Console login is locked, someone with administrative SSH access must unlock the login. To immediately unlock access to the Management Console by the root site administrator, use the ghe-reactivate-admin-login command via the administrative shell. For more information, see "Command-line utilities" and "Accessing the administrative shell (SSH)."
Unlocking a Management Console user account
The root site administrator can unlock access to the Management Console for other user accounts.
- Sign into the Management Console as the root site administrator. For more information, see "Accessing the Management Console."
- In the top navigation bar, click User Management.
- Locked user accounts will appear as "State: blocked". To unblock the user and allow authentication, to the right of the user's details, click .
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."