2.6 KiB
Executable File
Loading...
Often if the application is misconfigured the Loading... dialog is continuously displayed. This is most likely caused by the backed failing to start. The Maintenance -> Logs section should give you more details on what's happenning. If there is no exception, check the Portainer log, or start the container in the foreground (without the -d parameter) to observe any exceptions. It's advisable to enable trace or debug. Check the Debug tips on detailed instructions.
Incorrect SCAN_SUBNETS
One of the most common issues is not configuring SCAN_SUBNETS correctly. If this setting is misconfigured you will only see one or two devices in your devices list after a scan. Please read the subnets docs carefully to resolve this.
Permissions
Make sure you File permissions are set correctly.
- If facing issues (AJAX errors, can't write to DB, empty screen, etc,) make sure permissions are set correctly, and check the logs under
/app/log. - To solve permission issues you can try setting the owner and group of the
app.dbby executing the following on the host system:docker exec netalertx chown -R www-data:www-data /app/db/app.db. - If still facing issues, try to map the app.db file (⚠ not folder) to
:/app/db/app.db(see docker-compose Examples for details)
Container restarts / crashes
- Check the logs for details. Often a required setting for a notification method is missing.
unable to resolve host
- Check that your
SCAN_SUBNETSvariable is using the correct mask and--interface. See the subnets docs for details.
Invalid JSON
Check the Invalid JSON errors debug help docs on how to proceed.
sudo execution failing (e.g.: on arpscan) on a Raspberry Pi 4
sudo: unexpected child termination condition: 0
Resolution based on this issue
wget ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.3-2_armhf.deb
sudo dpkg -i libseccomp2_2.5.3-2_armhf.deb
The link above will probably break in time too. Go to https://packages.debian.org/sid/armhf/libseccomp2/download to find the new version number and put that in the url.
Only Router and own device show up
Make sure that the subnet and interface in SCAN_SUBNETS are correct. If your device/NAS has multiple ethernet ports, you probably need to change eth0 to something else.