Skip to main content

此版本的 GitHub Enterprise Server 将于以下日期停止服务 2023-12-20. 即使针对重大安全问题,也不会发布补丁。 为了获得更好的性能、更高的安全性和新功能,请升级到最新版本的 GitHub Enterprise。 如需升级帮助,请联系 GitHub Enterprise 支持


你 可以访问 管理控制台 以及配置 管理控制台 身份验证速率限制。

About access to the Management Console

From the Management Console, you can initialize, configure, and monitor your GitHub Enterprise Server instance. For more information, see "About the Management Console."

You can access the Management Console using the Management Console password. An administrator created the password during the initial setup process for your GitHub Enterprise Server instance. For more information about Management Console access, see "Administering your instance from the web UI."

Configuring rate limits for authentication to the Management Console

You can configure the lockout time and login attempt limits for the Management Console. If you configure rate limits, the limits apply to both the root site administrator and any Management Console users.

After you configure rate limits and a user exceeds the limit, the Management Console will remain locked for the duration set by the lockout time. 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)."

  1. From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click .

  2. If you're not already on the "Site admin" page, in the upper-left corner, click Site admin.

  3. In the " Site admin" sidebar, click Management Console.

  4. Optionally, under "Lockout time", type a number of minutes to lock the Management Console after too many failed login attempts.

  5. Optionally, under "Login attempt limit", type a maximum number of failed login attempts to allow before the Management Console is locked.

  6. Under the "Settings" sidebar, click Save settings.

    Note: Saving settings in the Management Console restarts system services, which could result in user-visible downtime.

  7. Wait for the configuration run to complete.