Parent node keeps changing even locked

[tradexsrl]

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

hi , i let the scanners run and then i setup the details of each devices found , in network details i setup the parent node - relationship type and parent node port and locked everyting. after a while when i come back to the devices the parent node setup is lost
please see the screenshot where parent node is setup to a wrong access point fi instead of a switch

Expected Behavior

i expected that if locked no further change are made by the next plugin run

Steps To Reproduce

1. change the parent node in a device details
2. select relationship type
3. select parent node port
4. lock everything
5. let the plugins run and see the problem

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

stdout.txt
app.txt

  PASTE LOG HERE. Using the triple backticks preserves format.

Docker Logs

netalertx_logs.txt

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

[PachangaDad]

I concur with these noticed behaviors. Noticed it last night while cleaning my scan results and trying to make corrections to my network inventory. Thank you for posting. I also noticed it reverted back to the first entry in the selection list. I my case, it was an Atomi Gateway vs RT-AC router.

[tradexsrl]

i hope will be resolved quickly because it is very usefull the network diagram for all of my offices and equipment

[jokob-sk]

I think it's duplicate #1503

Can you try the -dev image as per linked thread?

[tradexsrl]

Hi , ok i'll test the dev image but i have seen that this problem is apparently only on netalertx on synology nas with docker , i'm attaching the docker-compose that works for the scanning limitation of these box:

services:
netalertx:
image: ghcr.io/jokob-sk/netalertx:latest
container_name: netalertx
network_mode: "host"
restart: always
privileged: true

environment:
  - TZ=Europe/Rome
  - PUID=0
  - PGID=0
  - PORT=20211

tmpfs:
  - "/tmp:uid=0,gid=0,mode=1700,rw,noexec,nosuid,nodev,async,noatime,nodiratime"

volumes:
  - /volume1/docker/netalertx/data:/data
# to sync with system time
  - /etc/localtime:/etc/localtime:ro  

cap_drop:
  - ALL
cap_add:
  - NET_ADMIN
  - NET_RAW
  - NET_BIND_SERVICE
  - CHOWN
  - SETUID
  - SETGID

[tradexsrl]

tried with -dev image and seems the problem is solved on synology nas
please let me know when the -dev will be merged with latest one for docker so i can switch back

[jokob-sk]

Subscribe to the releases and you will get notified automatically: https://github.com/netalertx/NetAlertX?tab=readme-ov-file#-get-notified-whats-new

Closing as duplicate

[tradexsrl]

Hi , with latest dev image problem reappear (Built on: 25/02/2026, 23:01:37 | Version: dev-20260225-220044 )

[jokob-sk]

Hi @tradexsrl - can you please send me a video? It seems to work on my end (see below) - please continue here if issue persists: #1503