System Time Sync Causing Authentication Errors

[Artimaeus]

I have a fresh TrueNAS Scale installation, and I haven't been able to get 2FA, StorJ credentials, or even a local user account other than just the base admin account to authenticate.

1. Manually set the UEFI date/time (Asus doesn't have a way to set NTP within UEFI) to within a second of current time zone
2. Set TrueNAS NTP servers manually
   
3. Verified the time zone in TrueNAS is setup correctly

At a glance, the time seems to be perfectly setup, but I get this error when I try to verify Storj Credentials

<5>NOTICE: Time may be set wrong - time from "gateway.storjshare.io" is -3h59m58.709240327s different from this computer
Error: <5>NOTICE: Time may be set wrong - time from "gateway.storjshare.io" is -3h59m58.709240327s different from this computer <3>ERROR : : error listing: RequestTimeTooSkewed: The difference between the request time and the server's time is too large. status code: 403, request id: , host id: Failed to lsjson with 2 errors: last error was: error in ListJSON: RequestTimeTooSkewed: The difference between the request time and the server's time is too large. status code: 403, request id: , host id:

Logging in with any user other than the Admin one gives a username/password incorrect error, and same with 2FA. I can't seem to track down the source of the problem. I'm not sure why it is saying the time is 4 hours off. Please help!

 

[elvisimprsntr]

Welcome!

Set the CMOS clock to UTC time, not local time.

 

[danb35]

As mentioned, set the CMOS clock to UTC time, and also make sure the time zone is set correctly in TrueNAS.

I'm not sure why this is the case, but it seems to be a much more common source of problems in SCALE than in CORE. Curious.

 

[elvisimprsntr]

I'm not sure why this is the case, but it seems to be a much more common source of problems in SCALE than in CORE. Curious.

Likely a result of more people repurposing Windows HW, who stick with what they know or expect.

 

[Artimaeus]

So, the plot thickens . Adjusting time zone to anything at all shows a 4 hour gap. On a hunch, I'm GMT -4, so is it possible it is expecting GMT 0? That would explain the above error message, but I have no idea how to go about fixing that

 

[danb35]

Once again, the system clock needs to be set to the correct date/fime in UTC. Right now it's about 1625Z on 29 Sep 23. Then, when you set the correct time zone in the GUI, you should see the correct local time, the time sync should work, and the other errors should go away.

 

[Artimaeus]

Sorry for the confusion, I thought you had meant there was a UTC option in the UEFI. After manually setting it to that time, we're all good. Thanks!

 

[elvisimprsntr]

Majority of the universe requires UTC time for the CMOS clock, although there is a registry hack to force Windoze to use UTC

The Official U.S. Time | NIST

The National Institute of Standards and Technology - Time and Frequency Division maintains the standard for frequency and time interval for the United States, provides official time to the United States, and carries out a broad program of research and service activities in time and frequency...

time.gov