pfSense

pfSense Version: CE 2.8.0)

Summary:
The timestamp shown in the Auto Configuration Backup log (Services > Auto Config Backup > View Log) does not reflect the user's local time. The log appears to show the timestamp from the Netgate server's timezone (e.g., US Central Time) but incorrectly appends the local pfSense system's timezone offset, creating a contradictory and confusing timestamp.

Steps to Reproduce:

Set the pfSense system timezone to Europe/Madrid (CEST, UTC+2).

Verify with the date command that the system clock is correct and that NTP is fully synchronized.

Make a configuration change (e.g., save DHCP settings) to trigger an Auto Configuration Backup at a known local time (e.g., 23:00 CEST).

Navigate to Services > Auto Config Backup and view the log.

Observed Result:
The log entry shows a timestamp that is several hours behind the actual event time. For an event that occurred at 23:00 CEST, the log shows a time like 16:00:00 but incorrectly appends the local timezone offset, resulting in a timestamp of 16:00:00 +0200.

Expected Result:
The log entry should show the correct local time of the event, for example: 23:00:00 +0200.

Additional Notes:
Troubleshooting confirmed that the pfSense system clock (kernel), hardware clock (RTC), and NTP synchronization are all working perfectly and set to the correct local time. The issue appears to be a presentation bug in the ACB log viewer frontend, which seems to display the timestamp as recorded by the remote Netgate server without converting it to the user's local timezone, while simultaneously appending the local timezone offset.