NS8 core timezone off

Support
, ,
1

NethServer Version: NS8 current (updated this week)
Module: Nextcloud 1.5.0
Module: Roundcube 2.0.8

Today when I logged into NS8-Nextcloud the time for appointments and time in the personal information is off by 4 hrs. I’m guessing that in the core update that I did a few days ago must have messed up the time.

I am in Canada, Eastern timezone (presently daylight savings) which should be -4 hrs from UTC, so I’m not sure how I this change has happened.

i.e. Nextcloud shows 16:00 when the actual time is 12:00.

I also notice that Roundcube is showing the same 16:00 time.

I can’t find a place to change the time in the console so wondering how I’m supposed to fix this?

Thanks.

2

Please check the system time using timedatectl

[root@ns8rockytest ~]# timedatectl 
               Local time: Fri 2025-07-18 18:34:42 CEST
           Universal time: Fri 2025-07-18 16:34:42 UTC
                 RTC time: Fri 2025-07-18 16:34:42
                Time zone: Europe/Vienna (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

To set another timezone, see How to Set the Timezone and Configure NTP on Rocky Linux | Vultr Docs

3

Thanks @mrmarkuz

Here is what I get when running timedatectl

# timedatectl
               Local time: Fri 2025-07-18 12:52:11 EDT
           Universal time: Fri 2025-07-18 16:52:11 UTC
                 RTC time: Fri 2025-07-18 16:52:11
                Time zone: America/Toronto (EDT, -0400)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

So this looks OK.

Nextcloud 1.5.0 had “Automatic” in the calendar settings. Until today, it always was OK. Now it says "Automatic (Reykjavik) !!! When I manually change to Canada/Toronto, it’s OK.

Roundcube also has “Auto” as the “Timezone”. When I change it to Canada/Toronto, it is also OK.

So it appears that the “Automatic” is picking up something incorrectly.

Where can I find where that is?

4

Please check the timezone settings of your local device. It seems “Automatic” uses the timezone of the device that connects.

5

Thanks again @mrmarkuz .

Yes, that makes sense because I’ve seen this “Reykjavik” show up before on Windows. But in this case the time, date and timezone are correct on the device.

image
image764×536 15.5 KB

Any other suggestions on where to check?

6

There are browser addons that change the sent timezone for example Spoof Timezone – Get this Extension for 🦊 Firefox (en-US)
Did you already try another browser or device?

7

Hmm. Good idea.
It looks like Chrome works OK. I’m using LibreWolf. It hasn’t been a problem before but today it is.
When I went to cloud.domain.tld it pushed this:

image
image637×596 17.7 KB

This also unusual. The certificate was not a problem before.

I will look into why Librewolf may screw up the time.

8

I think I found the issue. Looks like the update of Librewolf enabled privacy.resistFingerprinting. With that setting enabled, it will always use UTC. When I turn off the setting, it shows the correct time when set to “Automatic (Toronto)”. Why it didn’t show up before, is unusual.

Now I have to look into why the certificate is acting up.

2 Likes