Browser guide wrong time

[qttor]

Something has happened to cause the Guide's current time (vertical line in the guide) to be displayed incorrectly. However, the NPVR Client shows the correct time in its guide but the web browser does not. It seems stuck at close to midnight of the correct day.

Anybody know how /what to do to fix this??? I'm using the latest NPRV version with Windows 10 version 21H2 and Firefox 101.0.1.

[mvallevand]

Does ctrl-f5 fix it?

Martin

[qttor]

Nope. I thought the liine was static, but I now see it's moving. It is 5 hours later than system time i.e. actual time 5:31pm but guide's line shows 11:31 pm.

[qttor]

Oops, the time error is 6 hours, not 5. Sorry. Could it possibly be related to the fact that i'm 6 hours earlier than UTC time??? The Windows clock is correct.

[sub]

What browser?

It's likely the browser's timezone is set incorrectly.

[qttor]

OK I found the problem if anyone runs into this in the future.
If you set the Fireox web browser to resist "fingerprinting" then it always reports the system's UTC time to websites instead of your local time. I never considered that NPVR would be fooled.

[sub]

OK I found the problem if anyone runs into this in the future.
If you set the Fireox web browser to resist "fingerprinting" then it always reports the system's UTC time to websites instead of your local time. I never considered that NPVR would be fooled.

Ultimately NextPVR's web app doesn't care where you are or what timezone you're in, and never even looks at these settings itself. It does ask your browser to convert the UTC date/times to your local time for display though, and it sounds like that was going wrong.

Glad you found a fix.

[mvallevand]

OK I found the problem if anyone runs into this in the future.
If you set the Fireox web browser to resist "fingerprinting" then it always reports the system's UTC time to websites instead of your local time. I never considered that NPVR would be fooled.

This is not a new feature and I have FF set to resist fingerprinting and it has never been a problem. The web clients reports times in epoch time so what it feeds the server is UTC.  It feels more like some addon you have enabled since we would no doubt have heard about this for a long time.

Martin