-
-
Notifications
You must be signed in to change notification settings - Fork 372
Closed
Labels
Docker 🐋Docker relatedDocker relatedbug 🐛Something isn't workingSomething isn't workingnext release/in dev image 🚀This is coming in the next release or was already released if the issue is Closed.This is coming in the next release or was already released if the issue is Closed.
Description
Is there an existing issue for this?
- I have searched the existing open and closed issues and I checked the docs https://jokob-sk.github.io/NetAlertX/
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
Hi,
Netalertx on docker here,
Built on 2025-10-05 Installed version v25.10.1 Database-Path /app/db/app.db Database-Size 22,31 MB (wal: 8,66 MB)
I have a lot of "ghost" devices in my list, so i want to delete them, but each time i click on the save icon in a field i got the "ERROR - DB might be locked - Check F12 Dev tools -> Console or try later."
Tested "Delete all event older from 30 days" -> not error
Thanks.
NB : optional question, can i manually edit the database, and how ? Thanks !
Expected Behavior
Multiple edit is working
Steps To Reproduce
Tools...
Multi Edit...
Click on any save field icon...
app.conf
docker-compose.yml
`---
services:
netalertx:
image: ghcr.io/jokob-sk/netalertx:latest
container_name: netalertx
privileged: false
environment:
- PORT=20211
- TZ=Europe/Paris
volumes:
- $PWD/config:/app/config
- $PWD/db:/app/db
- $PWD/log:/app/log
restart: unless-stopped
network_mode: "host"
`What installation are you running?
Production (netalertx)
Note :
/app/log/db_is_locked.log
0,00 MB
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Docker 🐋Docker relatedDocker relatedbug 🐛Something isn't workingSomething isn't workingnext release/in dev image 🚀This is coming in the next release or was already released if the issue is Closed.This is coming in the next release or was already released if the issue is Closed.
