Devices page "Last Offline" column shows UTC instead of local timezone
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start at the Devices page and inspect how the “Last Offline” column formats timestamps, comparing it with the header clock or tile cards, which the report says show the correct local time. Reproduce by adding the column with a configured timezone such as Asia/Manila. Done means the column displays times in the configured local timezone rather than UTC.
Written by the indexing model from the issue text.
Description
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
The "Last Offline" column on the Devices page is showing times in UTC instead of my local timezone, so every flapping/offline device looks like it dropped 8 hours later than it actually did (I'm on UTC +8). Everything else on the page (the header clock, the tile cards) is correct, so it reads like the timestamps are just wrong.
Expected Behavior
All time are synchronized based on the timezone I set.
Steps To Reproduce
- Add the "Last Offline" column in the dashboard.
- It's time is showing in UTC and not on your local time.
Relevant app.conf settings
docker-compose.yml
services:
netalertx:
image: ghcr.io/netalertx/netalertx:latest
container_name: netalertx
network_mode: "host" # Required for device discovery
restart: unless-stopped
volumes:
- ./data:/data
- /etc/localtime:/etc/localtime:ro
tmpfs:
- /tmp:uid=20211,gid=20211,mode=1700
environment:
- PORT=20211
- TZ=Asia/Manila # Change to your timezone
cap_add:
- NET_RAW
- NET_ADMIN
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.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 456
- Avg merge
- 17h 59m
- Merged PRs (30d)
- 26
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from netalertx/NetAlertX
-
bug 🐛
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
netalertx/NetAlertX#1856 · 1 comment · 7 reactions ·
Maintainers usually reply within 1 day
-
[Bug] MCP SSE endpoint event omits the /server prefix, so clients behind the built-in nginx proxy get a 404 on /mcp/messagesPossibly taken @frdmn claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Docker 🐋
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug 🐛 next release/in dev image 🚀 Waiting for reply⏳
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
netalertx/NetAlertX#1851 · 2 comments ·
Maintainers usually reply within 1 day
-
[Bug] Internet-Check returns 0.0.0.0 when IPv6 is enabled and OpenDNS lookup failsPossibly taken @pujitha24 claimed this 6 days ago. Openbug 🐛 next release/in dev image 🚀 Waiting for reply⏳
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
netalertx/NetAlertX#1845 · 2 comments ·
Maintainers usually reply within 1 day
All issues in netalertx/NetAlertX
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
khuisman/mcp-gee-sweet#1166 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
lugassawan/swe-workbench#823 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
gramaziokohler/compas_timber#870 ·
-
security-scan-failure
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
semantica-agi/semantica#2089 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
autowarefoundation/autoware_carla_scenario#500 ·
Maintainers usually reply within 1 day