BugWP logo BugWP
Back to Community
Home / Community / General

Fixing Sucuri Security Time and Timezone Display Issues

25 threads Sep 16, 2025

Content

If you've noticed that the timestamps in your Sucuri Security audit logs, email alerts, or login reports are showing the wrong time, you're not alone. Timezone and timestamp display problems are a common and long-standing issue reported by many users of the 'Sucuri Security – Auditing, Malware Scanner and Security Hardening' plugin.

Why Does This Happen?

Based on community reports, this issue stems from a complex interaction between several factors:

  • The plugin's internal date/time functions sometimes conflict with the server's time or WordPress's general timezone setting.
  • In the past, some timestamps were recorded in the plugin's API server time (PDT/EDT) rather than the site's local time.
  • Various code patches and updates over the years have occasionally introduced or fixed inconsistencies in different parts of the plugin's interface.

How to Fix Sucuri Time Display Issues

Here are the most effective solutions, compiled from successful user reports and developer responses.

1. Use the Plugin's Timezone Override Setting

The most reliable fix is to use the dedicated timezone setting within the Sucuri plugin itself.

  1. Navigate to Sucuri Security → Settings.
  2. Locate the Timezone option (often found in the General settings section).
  3. Select your correct timezone from the dropdown menu.
  4. Save the changes.

This setting allows the plugin to override other timezone configurations specifically for its own logs and notifications, which has resolved the issue for many users. The 'Sucuri Security – Auditing, Malware Scanner and Security Hardening' team added this option because relying solely on the WordPress general timezone setting proved unreliable for their plugin's functions.

2. Verify Your WordPress Timezone Setting

While the plugin has its own override, it's still good practice to ensure your main WordPress setting is correct, as some plugin functions may still reference it.

  1. Go to Settings → General in your WordPress dashboard.
  2. Confirm that the Timezone option is set to your city or a UTC offset matching your server.
  3. Save any changes.

3. Check for Plugin Updates

Many time-related bugs, such as incorrect intervals for scheduled scans or miscalculated timestamps, have been fixed in subsequent plugin updates. The development team has addressed issues like displaying timestamps in audit logs, fixing the 'in X hours' text for login times, and resolving email time discrepancies. Always ensure you are running the latest version of the plugin to benefit from these fixes.

4. Understand Display Limitations in Audit Logs

If you cannot see a timestamp next to an event in the Audit Log, note that it might be hidden by default. Hover your mouse cursor over the colored severity label (e.g., Info, Warning, Critical) for that event. The full date and time are often displayed in a tooltip. This design choice was made to save space in the table view.

When the Problem Persists

If you have tried all the above steps and the times are still incorrect, the issue may be related to your specific server environment or a hosting configuration that affects how PHP handles dates. In these cases, the problem often goes beyond the plugin's code. You may need to consult your hosting provider to verify the server's timezone configuration.

Time display issues have been a tricky challenge for the plugin's developers due to the number of variables involved. The dedicated Timezone override setting remains the primary and most effective tool for getting your Sucuri Security timestamps to display correctly.

Related Support Threads Support