fix current time

johnpoz

And what TZ are you set to in the general section? Brazil has what 4 different TZs

What is the output of your date cmd, what tz does it show?

guilherme_egb

I'm using the TZ America/Sao_Paulo.

After typing the date command show:
Mon Nov 11 15:28:50 -03 2019
It's correct.

But in the dashboard show me 16:28:50.

johnpoz

Do

[2.4.4-RELEASE][admin@sg4860.local.lan]/root: date -u
Mon Nov 11 18:34:28 UTC 2019
[2.4.4-RELEASE][admin@sg4860.local.lan]/root: date
Mon Nov 11 12:34:31 CST 2019

Post the output

guilherme_egb

johnpoz

Something not right there.. less it took you like 8 minutes between doing the command ;)

guilherme_egb

Yes, anything is wrong.

I guess that the better solution is upgrade the pfsense.

johnpoz

Not sure of all the changes - but its quite possible there was some change to TZ info between your version and current, etc.. I would for sure update to current... And then if we find a problem with the TZ settings we can submit the problem.

jimp

Also, under System > General Setup, pick a Timezone with a geographic name close to you, do not pick GMT +/- offset type zone.

Gertjan

Also : your system is repaired now https://forum.netgate.com/topic/148033/php-error-timezone ?

guilherme_egb

Yes, this PHP problem has been solved.

Thanks for helping.

johnpoz

So now your time shows correct?

guilherme_egb

I've reboot my pfsense today and then the php is working.

johnpoz

Not what I asked exactly, but take that as a yes to your time is now showing correct everywhere ;)

guilherme_egb

Sorry, I've answered wrong.

Today, I'll try to change my time manually.

paulo_pera

@jimp I'm from Brazil and under System > General Setup, pick a Timezone > using "Etc/GMT +3 (3 hours BEHIND GM)" fix the problem for me. We usually use "America/Sao Paulo" and it works in other systems (TrueNas ie). I guess is something related to tzdata version used with pfSense or the way php is reading the value.
It will be fixed in the 2.5 release https://forum.netgate.com/topic/158490/pfsense-php-time-is-incorrect-in-america-sao_paulo-time-zone/17