Setting the server time and timezone in WHM

Use an authorized server-administrator account. Record the current timezone, clock and scheduled jobs. Plan a maintenance window if a restart is needed, and tell application owners when changing the timezone could alter their task schedules.

1. Open Server Configuration > Server Time.
2. Choose the intended timezone. UTC is a useful server-wide standard, particularly when users or systems are in several regions. Keep application-specific display timezones in the application when possible.
3. Select Change TimeZone and review the result. Follow the documented restart requirement in a planned maintenance window so services use a consistent setting.
4. If the clock itself is incorrect, use Sync Time with Time Server and confirm that the configured network time service is reachable.
5. Review operating-system time synchronization after the immediate correction so the clock continues to stay accurate. Avoid multiple competing time services.

Before changing a server's timezone, list scheduled jobs, maintenance windows and applications that interpret time in that zone. A job intended to run after business hours can move to a different local time when the timezone changes.

Keep the server clock accurate and distinguish that from the display timezone. Record a reference timestamp in UTC and the expected local equivalent. Then review the server's time-synchronisation configuration through its supported tools.

What should I check afterwards?

Compare new log timestamps, scheduled tasks and application reports. Some applications and billing systems have their own timezone settings; changing WHM does not prove those settings were changed too. Do not manually rerun billing or renewal jobs simply because their displayed times look different.

Schedule the change with other administrators and preserve the previous setting. If you use a shared hosting account, request guidance rather than trying to change the server clock. Include the service, expected schedule and observed timestamp in your support case. We can help identify whether the difference comes from the operating system, application or browser without altering unrelated workloads.

Compare the server time with a reliable current time source. Check recent log timestamps, scheduled jobs, backups and two-factor authentication. Verify that database and application timezone choices still match the intended business schedule.

If the clock drifts again, investigate the time service, network access and virtualization-host clock rather than repeatedly changing the displayed timezone. Large clock corrections can affect running applications and job ordering, so escalate unexplained differences with the current clock, timezone and relevant service logs.

• Changing the server root password in WHM
• Logging in to WHM securely
• Setting the default nameservers in WHM
• Using WHM disabled features for server-wide restrictions

• Official cPanel & WHM documentation