Ubuntu 20.04 system time incorrect or not syncing

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Clock drift or wrong timezone causes authentication, scheduling, and certificate validation issues.

Environment & Reproduction

Displayed time differs from actual time and changes after reboot or network reconnect.

Root Cause Analysis

Disabled NTP sync, incorrect timezone, dual-boot RTC mismatch, or blocked time sources.

Quick Triage

Verify timezone, enable automatic time sync, and confirm outbound network access to NTP.

Step-by-Step Diagnosis

Run timedatectl status, check chrony or systemd-timesyncd service logs, and inspect RTC settings.

Solution – Primary Fix

Set correct timezone, enable NTP synchronization, and align RTC mode for dual-boot systems.

Solution – Alternative Approaches

Use enterprise NTP servers and firewall allowances where public pools are restricted.

Verification & Acceptance Criteria

System time remains accurate through reboot, suspend, and network transitions.

Rollback Plan

Revert custom NTP source overrides and restore default timesync service configuration.

Prevention & Hardening

Monitor clock offset and enforce approved NTP endpoints through configuration management.

Related Errors & Cross-Refs

Incorrect time often triggers TLS errors, Kerberos failures, and scheduler misfires.

Related tutorial: View the step-by-step tutorial for Ubuntu 20.04 LTS.

View all Ubuntu 20.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Review timedatectl, chrony docs, and Ubuntu time synchronization recommendations.