This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2020-05-23. 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.

Article version: Enterprise Server 2.17

Configuring time synchronization

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.

In this article

Changing the default NTP servers

  1. In the upper-right corner of any page, click .
    Rocketship icon for accessing site admin settings
  2. In the left sidebar, click Management Console.
    Management Console tab in the left sidebar
  3. In the left sidebar, click Time.
    The Time button in the Management Console sidebar
  4. Under "Primary NTP server," type the hostname of the primary NTP server. Under "Secondary NTP server," type the hostname of the secondary NTP server.
    The fields for primary and secondary NTP servers in the Management Console
  5. At the bottom of the page, click Save settings.
    The Save settings button in the Management Console
  6. 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

Ask a human

Can't find what you're looking for?

Contact us