Time Zone Issue from event dashboard

[Damiendhn]

What installation are you running?

Production (netalertx) 📦

Is there an existing issue for this?

• I have searched the existing open and closed issues and I checked the docs https://docs.netalertx.com/

The issue occurs in the following browsers. Select at least 2.

• Firefox
• Chrome
• Edge
• Safari (unsupported) - PRs welcome
• N/A - This is an issue with the backend

Current Behavior

Hello,

Since version 26.2.6, I have noticed a problem with the time display in the “event” dashboard.

My time zone is set to Europe/Paris, but events are shifted 1 hour into the future.

Expected Behavior

Same date/time with correct timezone

Steps To Reproduce

No response

Relevant app.conf settings

docker-compose.yml

Debug or Trace enabled

• I have read and followed the steps in the wiki link above and provided the required debug logs and the log section covers the time when the issue occurs.

Relevant app.log section

  PASTE LOG HERE. Using the triple backticks preserves format.

Docker Logs

  PASTE DOCKER LOG HERE. Using the triple backticks preserves format.

[jokob-sk]

Can you please share your:

1. Docker compose?
2. TIMEZONE setting?

[Damiendhn]

Synology Docker composer 👍

services:
netalertx:
container_name: netalertx
image: "jokobsk/netalertx:latest"
network_mode: "host"
cap_drop:
- ALL
cap_add:
- NET_RAW
- NET_ADMIN
- NET_BIND_SERVICE
- CHOWN
- SETUID
- SETGID
volumes:
- /volume1/docker/netalertx/data/logs:/tmp/log
- /volume1/docker/netalertx/data:/data:rw
- /etc/localtime:/etc/localtime:ro
environment:
- TZ=Europe/Paris
- PORT=15000
- PUID=0
- PGID=100
tmpfs:
- "/tmp:uid=0,gid=0,mode=1700,rw,noexec,nosuid,nodev,async,noatime,nodiratime"
restart: unless-stopped

[Damiendhn]

NetAlertX setting :

[jokob-sk]

Thanks, I think I've found the issue.

This should be fixed in the next release.

It would be great if you could test the ghcr.io/netalertx/netalertx-dev Docker image in ~15 minutes (or once the latest GitHub Action finishes).

⚠️ Please back up everything first, or ideally spin up a separate container with its own DB and config (a copy of your current setup), as database changes may occur.

After updating:

• Click the 🔄 refresh button in the blue header at the top
• Hard refresh your browser cache (shift + reload) to force js and css files reload

Disclaimer: Running the dev container long-term may lead to data loss, as upgrade paths are not guaranteed.

Thanks in advance,
j

[Damiendhn]

I'll try to do that today.

Thank you.