Setting the correct server time zone ensures that cron jobs, logs, backups, and scheduled tasks run at the expected times. WHM provides a straightforward interface to configure this. An incorrect time zone can also cause issues with cPanel & WHM license validation.
Step 1: Log in to WHM
Open your browser and navigate to https://your-server-ip:2087. Enter your root credentials to access the WHM dashboard.
Step 2: Navigate to Server Time
In the left-hand sidebar, go to Home » Server Configuration » Server Time.
Step 3: Select the Time Zone
From the Time Zone dropdown menu, select the appropriate time zone for your server. The menu lists all available time zones grouped by region.
Step 4: Apply the Change
Click the Change TimeZone button to save your selection.
Step 5: Reboot the Server
Reboot the server to ensure the time change is consistent across all services and processes. You can do this via WHM » System Reboot.
Important Notes
- cPanel & WHM recommends setting your server to Universal Time, Coordinated (UTC). This helps prevent Daylight Saving Time errors and simplifies log analysis when working with servers in different time zones.
- You can also set the time zone from the command line using the
timedatectlcommand. This is only available to the root user — cPanel users cannot use this command even with shell access. - If your server's time is slightly off, you can use the Sync Time with Time Server button on the Server Time page to synchronize with your network's time server.
- Changing the time zone affects all cron jobs, scheduled tasks, log timestamps, and certificate validation times on the server.
- Always reboot after changing the time zone to ensure all running services pick up the new setting.
Troubleshooting
- Time still incorrect after changing time zone: Ensure you rebooted the server after applying the change. Some services cache the time zone on startup.
- License validation errors: Verify the server time is accurate. A significantly incorrect system clock can cause cPanel license validation to fail.
- cron jobs running at wrong times: Confirm the time zone is set correctly and check that the cron schedules account for the server's time zone (not your local time zone).