Whether you have recently moved to a new country, noticed your system clock displaying the wrong hour, or are managing a remote cloud server located halfway across the globe, ensuring your Linux machine has the correct local time is critical. An incorrect timezone does not just make you late for meetings; it can cause severe issues with scheduled cron jobs, break SSL certificate validations, and completely scramble system log timestamps, making troubleshooting nearly impossible. Therefore, knowing how to change the timezone in Ubuntu Linux is a fundamental system administration skill.
In this comprehensive guide, we will explore the dual approaches to time management in Linux, providing precise step-by-step instructions for both desktop users who prefer a graphical interface and server administrators who rely entirely on the command-line terminal.
Why Correct Timezones Matter in Linux
On a personal desktop, the timezone simply dictates the clock on your taskbar. However, beneath the surface, Linux relies heavily on chronological accuracy:
- Software Updates: The
aptpackage manager checks digital signatures against the current time. If your clock is wildly inaccurate, repository connections will be rejected. - Log Auditing: When troubleshooting a server crash, system administrators rely on
syslogtimestamps. If the server is operating on UTC but the admin assumes it is on EST, diagnosing the exact moment of failure becomes a chaotic guessing game.
Prerequisites and Requirements
Before proceeding with timezone modifications, ensure that:
- You are running a supported version of Ubuntu Linux (these instructions apply to 20.04 LTS, 22.04 LTS, 24.04 LTS, and most Debian-based derivatives).
- You have access to a user account with sudo (administrator) privileges. Standard users cannot alter system-wide time settings.
- Your machine has an active internet connection if you wish to use automated network time synchronisation (NTP).
Method 1: Change the Timezone via the Command Line (Terminal)
For server administrators running headless Ubuntu Server, or power users who prefer efficiency, the timedatectl command is the modern, powerful standard for managing time in Linux.
Step 1: Check the Current Timezone
Open your terminal (Ctrl + Alt + T) and type the following command to view your current system time status:
timedatectlThis will output a block of text detailing the Local time, Universal time (UTC), and the currently configured Time zone (e.g., Etc/UTC or Europe/London).
Step 2: List Available Timezones
Linux formats timezones using a “Region/City” naming convention. To find the exact name of your desired timezone, list them using this command:
timedatectl list-timezonesBecause this list contains hundreds of entries, it is highly recommended to pipe the output into the grep command to filter for your specific region or city. For example, to find timezones in America, type:
timedatectl list-timezones | grep AmericaStep 3: Set the New Timezone
Once you have identified the correct region and city format, use the set-timezone parameter to apply the change. You must use sudo for this action. For example, to change the timezone to New York, execute:
sudo timedatectl set-timezone America/New_YorkThe change is instantaneous. You can run the timedatectl command again to verify that the “Time zone” field has updated correctly.
Method 2: Change the Timezone Using the GUI (Ubuntu Desktop)
If you are using the standard Ubuntu Desktop edition with the GNOME environment, changing the timezone is a simple, visual process.
Step 1: Access System Settings
Click the system menu in the top-right corner of your screen (where the battery and network icons reside) and select Settings.
Step 2: Navigate to Date & Time
Scroll down the left-hand sidebar menu until you find Date & Time (on newer Ubuntu versions, this is located inside the System tab). Click on it.
Step 3: Unlock and Change the Timezone
By default, the timezone is often managed automatically via your internet connection. To change it manually:
- Toggle off the switch for Automatic Time Zone.
- Click on the Time Zone row directly below it.
- A world map will appear. Simply click on your location on the map, or use the search bar at the top to type in your nearest major city.
- Close the window, and your system clock in the top panel will instantly update.
Alternative Methods: The Legacy Approach
If you are working on an extremely old, legacy Linux server that does not support systemd or the timedatectl command, you can still change the timezone by reconfiguring the tzdata package. Run this command:
sudo dpkg-reconfigure tzdataThis launches an interactive, text-based menu within the terminal where you can navigate through geographic areas and cities using your arrow keys.
Troubleshooting Common Time Issues
The Clock is Still Wrong After Changing the Timezone
If the timezone is correct but the hour is still drifting, your system is likely not syncing with a network time server (NTP). You can force network time synchronisation by running:
sudo timedatectl set-ntp trueEnsure your server can access the internet over port 123 (the standard NTP port) so it can fetch the highly accurate time data.
Frequently Asked Questions
Should servers run on a local timezone or UTC?
It is an industry best practice for all Linux servers, especially those in cloud environments (like AWS or DigitalOcean) or database servers, to be set to UTC. This prevents catastrophic data errors relating to Daylight Saving Time jumps and ensures logs from servers across different global regions align perfectly.
Does changing the timezone require a reboot?
No. Changing the timezone via timedatectl or the GUI applies the changes immediately to the system. However, long-running services or cron daemons that were started before the change might still operate on the old time until they are manually restarted.
Managing system time is a small but vital component of maintaining a healthy operating system. By mastering how to change the timezone in Ubuntu Linux via the command line, you ensure your scheduled tasks execute flawlessly and your system logs remain impeccably accurate, saving you from severe administrative headaches down the line.
