[Issue]: Air Date is 1 day off in NFO #3585

Closed
opened 2026-02-06 23:31:07 +03:00 by OVERLORD · 0 comments
Owner

Originally created by @kdoubledubs on GitHub (Feb 5, 2022).

Originally assigned to: @daullmer on GitHub.

Please describe your bug

I never noticed this til now but all my nfo are off by 1 day earlier than what is posted at thetvdb or themoviedb. I am on 10.7.7. My TZ environment variable is set to America/New_York.
I can confirm log times show correct EST timezone so I know that my TZ config is correct.

Here is an example of the NFO that Jellyfin generates and thetvdb webpage in for background showing the date mismatch.

Screen Shot 2022-02-05 at 10 31 39 AM

Here is an example of a movie having the same behavior:

Screen Shot 2022-02-05 at 10 42 21 AM

I came across GitHub fix (https://github.com/jellyfin/jellyfin-web/pull/3230) and decided to run a test on latest nightly release but it doesn't seem to fix the underlying issue of the NFO creation having the incorrect airdate field off by 1 day. The web client does show correct airdate but the NFO is incorrect.

Jellyfin Version

10.7.7

if other:

No response

Environment

- linuxserver/jellyfin
    jellyfin:
        image: lscr.io/linuxserver/jellyfin:nightly
        container_name: jellyfin
        restart: unless-stopped
        ports:
            - 8096:8096
#           - 8920:8920
            - 7359:7359/udp
#           - 1900:1900/udp
        volumes:
            - ./jellyfin/appdata/config:/config
            - /mnt/media:/media
        environment:
            - PUID=1000
            - PGID=1000
            - TZ=America/New_York
            - JELLYFIN_PublishedServerUrl=192.168.86.102

Jellyfin logs

No response

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Originally created by @kdoubledubs on GitHub (Feb 5, 2022). Originally assigned to: @daullmer on GitHub. ### Please describe your bug I never noticed this til now but all my nfo <airdates> are off by 1 day earlier than what is posted at thetvdb or themoviedb. I am on 10.7.7. My TZ environment variable is set to America/New_York. I can confirm log times show correct EST timezone so I know that my TZ config is correct. Here is an example of the NFO that Jellyfin generates and thetvdb webpage in for background showing the date mismatch. <img width="894" alt="Screen Shot 2022-02-05 at 10 31 39 AM" src="https://user-images.githubusercontent.com/16267805/152658007-2b6d04a5-5a94-45a9-b6b6-21a67841115f.png"> Here is an example of a movie having the same behavior: <img width="1412" alt="Screen Shot 2022-02-05 at 10 42 21 AM" src="https://user-images.githubusercontent.com/16267805/152658023-71306602-0f13-4872-9b7d-050680353e37.png"> I came across GitHub fix (https://github.com/jellyfin/jellyfin-web/pull/3230) and decided to run a test on latest nightly release but it doesn't seem to fix the underlying issue of the NFO creation having the incorrect airdate field off by 1 day. The web client does show correct airdate but the NFO is incorrect. ### Jellyfin Version 10.7.7 ### if other: _No response_ ### Environment ```markdown - linuxserver/jellyfin jellyfin: image: lscr.io/linuxserver/jellyfin:nightly container_name: jellyfin restart: unless-stopped ports: - 8096:8096 # - 8920:8920 - 7359:7359/udp # - 1900:1900/udp volumes: - ./jellyfin/appdata/config:/config - /mnt/media:/media environment: - PUID=1000 - PGID=1000 - TZ=America/New_York - JELLYFIN_PublishedServerUrl=192.168.86.102 ``` ### Jellyfin logs _No response_ ### FFmpeg logs _No response_ ### Please attach any browser or client logs here _No response_ ### Please attach any screenshots here _No response_ ### Code of Conduct - [X] I agree to follow this project's Code of Conduct
OVERLORD added the bug label 2026-02-06 23:31:07 +03:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#3585