[BUG] Incorrect time after uploading

[dm3010]

The bug

These are two photos from the same phone, taken 3 hours apart in time
Info about before uploading
Time 15:00 (1 photo) and 18:01 (2 photo) - Correct all

After uploading from mobile app, one of the photos has the wrong time
Time 18:00 (1 photo) wrong! and 18:01 (2 photo) - correct

I've tried uploading them via the web interface as well, and the problem is the same

The problem seems to be due to timezone, as the time shift on the wrong photo is the same as +3 hours (My timezone GMT+3)

What surprises me the most is that these photos were taken on the same day with the same phone

The OS that Immich Server is running on

Docker

Version of Immich Server

v1.85

Version of Immich Mobile App

v1.85

Platform with the issue

• Server
• Web
• Mobile

Your docker-compose.yml content

*

Your .env content

*

Reproduction steps

1.
2.
3.
...

Additional information

No response

[andyxpert]

do you have the timezone set correctly ?
https://immich.app/docs/install/environment-variables#general - look for TZ env variable

[dm3010]

I tried adding this option (TZ="GMT+3"), and got an increase in first photo time by another three hours
First photo time is set to 21:00

[uenokatsura]

I have the same problem here, the time was added 8 hours (cause I'm in GMT+8)
This happened on the iOS screenshot.
I tried added TZ="GMT+8" but that made no change at all.
Original File Here

[uenokatsura]

Also a related bug.
Though mobile version can. Immich webui won't list photos "from the future".

[MDsza]

I am loving Immich more and more... but same problem here (in Switzerland = GMT/UTC+1): Only iOS Screenshots are shown with wrong timestamp = +1 hour in the future after uploading to Immich what results in a wrong order of the images on my iPhone AND the WebUI, too. Images shot on the iPhone are shown with the right time stamp... hmmm. Any solution?

[DJPapa66]

Hello,

I have the same problem and don't understand why the recording date isn't just taken. E.G. the photo was taken at 15:52:37 and not 16:52:37. That's it. Why does something have to be calculated? I'm "lucky" that it's only +1 hour (Berlin) for me. I could deal with that if necessary. However, I don't understand it.
It would be great if I could choose how to import - maybe in the settings (with or without calculation).

[BjGoCraft]

Same problem here: Two photos were taken 3 seconds apart. When looking at the metadata locally on my PC, the time on both is right. When uploading both pictures to immich via the web interface, one has the correct time stamp and one is suddenly one hour later (GMT +1).
Edit: I just found out that the picture with the right time has location data while the other hasn't.

[alextran1502]

@BjGoCraft can you share those teo photos for troubleshooting?

Saw your edit, that explains it

[BjGoCraft]

@BjGoCraft can you share those teo photos for troubleshooting?

Saw your edit, that explains it

I did send you an e-mail, I don't want to publish my face :)

[ygaeon]

Can confirm I experience this as well ..

(tried to attach photos here but unable to)

Photo date/timestamp on phone is 2024-04-15 15:37:57
Phone timezone is CET (GMT +2).

Once uploaded to Immich server, photo date/timestamp becomes 2024-04-15 17:37 GMT+02:00

....

While researching a bit, discovered that /etc/localtime was symlinked to /usr/share/zoneinfo/Etc/UTC even though I created the container with --volume /etc/localtime:/etc/localtime:ro and the host's localtime is linked to CEST.

Do you set this /etc/localtime from somewhere else starting up?

Please advice ..

[BjGoCraft]

My /etc/localtime is symlinked to /usr/share/zoneinfo/Europe/Berlin so that is right.
In my docker-compose.yml und the immich-microservices > volumes: > there is - /etc/localtime:/etc/localtime:ro
so all time zones are set to local time. The timezone isn't specified anywhere else. I didn't create the container with any flags but as described in the docs. The problem @dm3010 is experiencing too seems to be linked to if the photo has location data or not

[semiligneous]

I get this too. Seems quite simple to reproduce:

• Docker compose installation, no customisation.
• host tz as something ahead of utc by a few hours
• Leave /etc/localtime mounted from host
• take a screenshot on iOS and immediately upload it via the app
• take a photo on iOS and immediately upload it via the app

Observe that the photo correctly appears with date/time in local time showing in timeline as expected

Observe that the screen shot shows in timeline 'in the future'- if your utc tz offset is large and you took the screenshot late enough in the day, it will even show under tomorrow's date in the timeline

The date itself is off by whatever the utc offset happens to be.

Seems to be impossible to fix (edit: through config files) since it affects only certain media - in this case screenshots but as others have said, possibly also media without a location?
I'm