Skip to main content
We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the English documentation.
All products
Enterprise administrators

This version of GitHub Enterprise was discontinued on 2023-03-15. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Configuring time synchronization

In this article

GitHub Enterprise Server automatically synchronizes its clock by connecting to NTP servers. You can set the NTP servers that are used to synchronize the clock, or you can use the default NTP servers.

Changing the default NTP servers

  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. In the "Settings" sidebar, click Time.
  5. Under "Primary NTP server," type the hostname of the primary NTP server.
  6. Under "Secondary NTP server," type the hostname of the secondary NTP server.
  7. Under the "Settings" sidebar, click Save settings.
  8. Wait for the configuration run to complete.

Correcting a large time drift

The NTP protocol continuously corrects small time synchronization discrepancies. You can use the administrative shell to synchronize time immediately.

Notes:

  • You can't modify the Coordinated Universal Time (UTC) zone.
  • You should prevent your hypervisor from trying to set the virtual machine's clock. For more information, see the documentation provided by the virtualization provider.
  • Use the chronyc command to synchronize the server with the configured NTP server. For example:
$ sudo chronyc -a makestep