How to Change Timezone on Ubuntu 26.04

To change timezone on Ubuntu 26.04, select an IANA timezone and apply it with timedatectl. The new local-time setting takes effect immediately and normally takes only a few minutes to configure over SSH, without restarting the VPS.

Prerequisites

• Ubuntu Server 26.04 LTS installed and reachable over SSH.
• A root shell or a normal user with working sudo privileges.
• The destination timezone as an IANA name, such as America/Chicago, Europe/London, or Asia/Kolkata.
• No special RAM, disk, or domain requirement; a VPSLake Linux VPS provides the server access needed for this change.

Step 1: Record the current time settings

Check the existing timezone and synchronization state first so you have a baseline for the change.

timedatectl status
date '+Local: %F %T %Z %z'
date -u '+UTC:   %F %T %Z'

A newly provisioned VPS commonly starts in UTC. The dates will differ on your machine, but the report should contain lines like these:

               Local time: Thu 2026-10-08 14:20:11 UTC
           Universal time: Thu 2026-10-08 14:20:11 UTC
                 Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
              NTP service: active
Local: 2026-10-08 14:20:11 UTC +0000
UTC:   2026-10-08 14:20:11 UTC

The timezone controls how software displays the current instant; it does not set the clock itself. Keep NTP enabled so changing the display zone does not turn into a clock-accuracy problem.

Step 2: Find the exact IANA timezone

Ubuntu expects a zoneinfo identifier, not a label such as “Central Time” or an abbreviation such as CST. List the installed choices and copy the complete spelling.

timedatectl list-timezones | grep -E '^(Africa|America|Asia|Australia|Europe)/'

If you want to browse every available entry, use a pager:

timedatectl list-timezones | less

Press q to exit. Example entries include:

America/Chicago
America/Los_Angeles
America/New_York
Asia/Kolkata
Australia/Sydney
Europe/London

Use the city-based entry that matches the location whose civil-time rules you need. These names include daylight-saving transitions where applicable; use UTC when you want one fixed reference for logs and scheduled operations.

Step 3: Apply the Ubuntu 26.04 timezone

Run timedatectl so systemd updates the active setting and persistent /etc/localtime configuration together.

sudo timedatectl set-timezone YOUR_REGION/YOUR_CITY

Replace YOUR_REGION/YOUR_CITY with the exact value from Step 2, such as America/Chicago or Asia/Kolkata. A successful command normally prints nothing. Read back the saved setting and resolved timezone file:

timedatectl show --property=Timezone --value
readlink -f /etc/localtime

For America/Chicago, the result should resemble:

America/Chicago
/usr/share/zoneinfo/America/Chicago

This is the recommended systemd operation; do not edit /etc/localtime by hand or manually change the hardware clock. See the official timedatectl documentation for the supported properties and timezone operations.

Step 4: Check Ubuntu’s time synchronization

Timezone selection and network synchronization are separate settings, so confirm that the underlying clock is still synchronized after the update.

timedatectl show --property=NTP --property=NTPSynchronized
systemctl is-active systemd-timesyncd
timedatectl timesync-status

On a fresh Ubuntu installation using the default synchronizer, you should see results similar to:

NTP=yes
NTPSynchronized=yes
active
Server: 91.189.89.198 (ntp.ubuntu.com)
Leap: normal

The server address, poll interval, and offset will vary. Ubuntu’s time synchronization guide explains that systemd-timesyncd is the normal service and that chrony takes over when it is installed. If chrony is active on your VPS, do not start a second time daemon; verify the NTPSynchronized value and inspect Chrony instead.

Verify the new timezone

Compare the chosen zone with UTC and the saved /etc/localtime target. The two timestamps should represent one instant with different offsets.

timedatectl show --property=Timezone --property=NTPSynchronized
date -u '+UTC:   %F %T %Z'
date '+Local: %F %T %Z %z'
readlink -f /etc/localtime

After choosing America/Chicago, the important lines should look like this:

Timezone=America/Chicago
NTPSynchronized=yes
UTC:   2026-10-08 14:20:40 UTC
Local: 2026-10-08 09:20:40 CDT -0500
/usr/share/zoneinfo/America/Chicago

Your timestamp will be different. The change is complete when Timezone and the /usr/share/zoneinfo/ path match your choice and synchronization reports yes.

Troubleshooting

Failed to set time zone: Invalid or unknown time zone

The argument is not an exact identifier in Ubuntu’s installed timezone database. Run timedatectl list-timezones, copy the full Region/City spelling, and retry. Do not use a Windows timezone name, a display label, or a three-letter abbreviation.

Authentication is required or Access denied

Changing the system-wide timezone is an administrator operation. Test the account with sudo -v, add sudo to the command, or reconnect as root; changing permissions on /etc/localtime is not necessary.

System has not been booted with systemd

You are probably inside a minimal container, chroot, or restricted shell rather than a complete Ubuntu VPS. Check the init process with ps -p 1 -o comm=. If systemd is not PID 1, set the timezone through that container or image runtime instead of changing the host’s files.

NTPSynchronized=no or systemd-timesyncd is inactive

First check whether another daemon owns time synchronization:

systemctl is-active chrony
systemctl status systemd-timesyncd --no-pager

If Chrony is not active and systemd-timesyncd is missing or stopped, restore Ubuntu’s default service:

sudo apt update
sudo apt install -y systemd-timesyncd
sudo timedatectl set-ntp true
sudo systemctl enable --now systemd-timesyncd
timedatectl show --property=NTP --property=NTPSynchronized

Allow outbound UDP port 123 in any provider firewall or security group. If synchronization remains unavailable, inspect sudo journalctl -u systemd-timesyncd -n 30 --no-pager and confirm that DNS and outbound network access work.

Hardening and operational notes

• Use UTC for infrastructure that serves multiple regions so logs and maintenance windows share one stable reference.
• Review local-time cron jobs after selecting a daylight-saving zone; their corresponding UTC execution time can change seasonally.
• Keep exactly one time-synchronization service enabled. Do not use date to manually correct a production clock.
• Record the selected IANA identifier in your provisioning notes so a rebuild gets the same behavior.

FAQ

Does changing the timezone change Ubuntu’s actual clock?

No. timedatectl set-timezone changes the representation of the current instant, while NTP keeps that instant aligned with network time. The UTC and local date checks show the distinction.

Which timezone should I use for a VPS in India?

Use Asia/Kolkata, the IANA identifier for India Standard Time. It normally displays a +0530 offset and does not follow seasonal daylight-saving changes.

Can I use PST, CST, or IST instead of a city name?

Use a full IANA name such as America/Los_Angeles, America/Chicago, or Asia/Kolkata. Abbreviations are ambiguous and do not reliably carry the location’s full seasonal rules.

Do I need to reboot Ubuntu 26.04 afterward?

No. The system timezone applies immediately and persists across reboots. Restart only an application that explicitly cached the old timezone during startup or deliberately uses its own UTC setting.