My transaction date gets converted to ??? time zone #12616
Replies: 2 comments 14 replies
|
The value is moving by 10 hours, not 20:
docker compose exec app php -r 'echo "env TZ: ", getenv("TZ"), PHP_EOL, "PHP TZ: ", date_default_timezone_get(), PHP_EOL;'If either value is UTC or empty, make sure the variable is under the services:
app:
environment:
TZ: Australia/Sydneydocker compose up -d --force-recreate app
docker compose exec app php artisan optimize:clearThen repeat the If Source references: |
|
Where exactly is the date displayed wrong? |


Uh oh!
There was an error while loading. Please reload this page.
I couldn't find a similar topic...
If I enter the date of a transaction using the 'real' date and time for my Time Zone (GMT+10), the date recorded in Firefly shows it has been converted to ???.
This often results in the displayed date being 'out' by a day.
An example, I enter a Withdrawal as 15/8/2026 at 17:00 where I use Australia/Sydney
However, this is recorded, and displayed everywhere in Firefly, as 16/8/2026 03:00
This seems to be 20 hrs ahead of my local time zone.
I have this environment variable in my compose.yaml:
TZ: Australia/Sydney
What am I missing, and what do I need to change, so that my entered 'local' date/time is maintained after data entry?
My current work-around is to use '12:00' for the Time field in every transaction - this is 'translated' to '23:00', but at least the date is correct.
TIA
All reactions