[looking for maintainers] Broken API path

[hackNthisNthat]

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

https://raw.githubusercontent.com/jokob-sk/NetAlertX/refs/heads/main/api
Breaks Proxmox script as the git clone turns this into a symlink and can not be removed with an rf -rf (I added this locally) and can not be over written with makdir -p $(INSTALL_DIR)/api"

Expected Behavior

Script make the api folder as intended.

Steps To Reproduce

run the script on a brand new LXC of Trixie

Relevant app.conf settings

docker-compose.yml

What installation are you running?

Production (netalertx)

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. 

[jokob-sk]

Hi,

I assume this is not a docker based installation, but bare metal hardware install?

[BetterImpactPeter]

Not bare metal. Not Docker.
Trying to run the Proxmox script on a fresh LXC of Debian 13.

[jokob-sk]

I consider running the proxmox script bare metal = non-containerized instance. Non-containerized instances are community supported so I will tag the issue accordingly and hopefully someone from teh community can help.

[BetterImpactPeter]

No worry. I can appreciate the need for simple binary filters.
I was just following some recent XDA coverage of the product and wanted to give it a spin.

EDIT: Ignore my multiple persona issues. Personal interests and work laptops make a mess. I forget who I'm logged in as.

[moop-moop]

I was able to get the proxmox-install-netalertx.sh to complete without errors by removing links/directories with just a simple recurse.

printf "%b\n" "Cleaning up old mounts if any"
umount "${INSTALL_DIR}/log" 2>/dev/null || true
umount "${INSTALL_DIR}/api" 2>/dev/null || true

# monkey patch
printf "%b\n" "Removing old directories or links if any"
rm -r "${INSTALL_DIR}/api" "${INSTALL_DIR}/log" 2>/dev/null || true
# end monkey patch

printf "%b\n" "Creating log api folders if they don't exist"
mkdir -p "${INSTALL_DIR}/log" "${INSTALL_DIR}/api"

However.... I am still not able to get running on Proxmox + Debian 13 LXC.
netalertx.service seems to be stuck in a perpetual activating state.
Relating to PHP error /app/front/php/server/db.php(194), which seems to be unrelated.

[adm2k]

I am having a similar issue when doing a fresh Install on Debian 13. Docker PS shows the status as restarting - seems to be in some loop.

My docker compose...
services:
netalertx:
container_name: netalertx
image: "jokobsk/netalertx:latest"
network_mode: "host" # Use host network mode for proper network scanning
restart: unless-stopped
volumes:
- ./config:/app/config
- ./db:/app/db
- ./logs:/app/log
- type: tmpfs
target: /app/api
environment:
- TZ=America/New_York # Adjust your timezone as needed
- PORT=20211 # The port NetAlertX web interface will run on