umami-software
Timezone error in v3.0.1 – “Last 24h” & custom range shift data +5h and exclude valid events
Describe the Bug
Description
The timezone window logic is still incorrect in v3.0.1.
Data is displayed correctly in Realtime view, but “Last 24 hours” and all custom date ranges shift timestamps +5 hours, which makes the data appear to be in the future. As a result, valid analytics fall outside the window and are either missing completely or shown at incorrect hours.
Environment
- Umami version: 3.0.1
- Server OS timezone: America/New_York (EST, UTC–05:00)
- PostgreSQL timezone: America/New_York
- Node runtime: restarted after timezone correction
- Browser/UI timezone: America/New_York
- Also tested with: set TZ=UTC before
npm start– issue persists
Evidence
Realtime tracking displays correctly.
Custom range chart example (should show data from 1–4 PM local, instead shows 6 PM–9 PM):
Database
PostgreSQL
Relevant log output
Which Umami version are you using? (if relevant)
3.0.1
Which browser are you using? (if relevant)
Chrome, Edge, Firefox
How are you deploying your application? (if relevant)
node
This may be related to #3781. Also wondering is this only an issue on the last 24 hours/custom time frames, but different time frames are ok?
This same thing is happening to me, except across any range. No matter which graph I'm looking at, the graph is missing the first four hours of whichever bar graph I'm looking at. This happens in the normal hourly views for both real time and compare data.
