"Network" screen stuck on Loading

[Metathesus]

Is there an existing issue for this?

• I have searched the existing open and closed issues and I checked the docs https://github.com/jokob-sk/NetAlertX/tree/main/docs

Current Behavior

"Network" screen stuck on "Loading"

• Cache cleared
• Container recreated with logs and config volume deleted (only the db has been keeped)
• Error in in console browser (F12)

Expected Behavior

Network screen load correctly

Steps To Reproduce

No response

app.conf

No response

docker-compose.yml

services:
  netalertx:
    container_name: netalertx 
    image: "jokobsk/netalertx:latest"      
    network_mode: "host"        
    restart: unless-stopped
    volumes:
      - /mnt/Docker/netalertx/config:/app/config
      - /mnt/Docker/netalertx/db:/app/db      
      # (optional) useful for debugging if you have issues setting up the container
      - /mnt/Docker/netalertx/logs:/app/front/log
    environment:
      - TZ=Europe/Paris     
      - PORT=2480

What branch are you running?

Production

app.log

No response

Debug 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.

[jokob-sk]

Hi @Metathesus - make sure you didn't assign the root Internet node to a child node. This will cause recursion. This shouldn't happen, so please let me know how you did it 😅

You can show parent nodes nodes this way which can help you to find it:

or you can export the devices.csv file and check / fix it there:

[Metathesus]

The parent node of internet was internet. How was it possible? I don't know because it was always greyed out...
I'have delete this device and has been recreatd automatically and now parent is "unknown" and all working well

[Metathesus]

Thanks for your help

[jokob-sk]

Great! Reopening for tracking, will close after next release

[jokob-sk]

releasing in 15 min -> closing