LAST ONLINE field does not display the time zone correctly

[bobwang3]

My installed version: 2024.08.07.0819
Server version: Rocky 9.6 Linux
I deployed version 2021.08.26.1335 on centos7 about 4 years ago, and since the new version became Docker and there was no way to upgrade it directly, I rebuilt the new version 2024.08.07.0819 and gradually updated the old client to the new version.
This process went relatively smoothly and the new version is running fine.
However, I found a small problem, when the web interface of the new version 2024.08.07.0819 displays the client information, the LAST ONLINE is shown as UTC time (example: 08/05/2025 06:06:28 +00:00), instead of East 8 time as I want. I observed my old version 2021.08.26.1335 and it is correct (example: 8/5/2025 2:08:20 PM +08:00)
I ran timedatectl on a rocky9 system and got the following results:

Local time: Tue 2025-08-05 13:26:20 CST
Universal time: Tue 2025-08-05 05:26:20 UTC
RTC time: Tue 2025-08-05 05:26:20
Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

I'm not sure if this is a bug or what I need to change to fix this.

[mattish91]

Are you running the updated version in docker? In that case you could add an environment variable that says "TZ=yourtime/zone"

In my case i set it up as "TZ=Europe/Stockholm" and it displays the correct time.

Otherwise does the server have the correct time zone?