Env variable GRAPHQL_PORT not used

[jokob-sk]

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

A custom value in the docker-compose file defining the GRAPHQL_PORT variable is not respected

Expected Behavior

Use the value GRAPHQL_PORT as the value of the GRAPHQL_PORT setting

Steps To Reproduce

1. Create a docker-compose file with a custom environment variable changing the default GRAPHQL_PORT value

Relevant app.conf settings

N/A

docker-compose.yml

...
  - GRAPHQL_PORT=20322

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]

@Marvelous2095

This should be available/fixed in the next release.

It would be great if you could test the ghcr.io/netalertx/netalertx-dev-unsafe Docker image in ~15 minutes (or once the latest GitHub Action finishes).

⚠️ Please back up everything first, or ideally spin up a separate container (make sure you use a unique PORT and GRAPHQL_PORT if running instances concurrently) with its own DB and config (a copy of your current setup), as database changes may occur.

After updating:

• Click the 🔄 refresh button in the blue header at the top
• Hard refresh your browser cache (shift + reload) to force js and css files reload

👉 If I don’t receive confirmation that this works, I may revert the changes to avoid introducing bugs.

Disclaimer: Running the dev container long-term may lead to data loss, as upgrade paths are not guaranteed.

Thanks in advance,
j

[Marvelous2095]

Tested ghcr.io/netalertx/netalertx-dev-unsafe:unsafe (created 2026-09-21T07:31:22Z, i.e. after your comment) in a separate container with a fresh volume and its own ports (PORT=20331, GRAPHQL_PORT=20332, network_mode: host), while another instance was running on 20211/20212:

• The GRAPHQL_PORT setting is now 20332 (before it stayed 20212 despite the env var), the API listens on 20332 (no collision with the other instance), the UI proxy /server/ reaches it (403 without token), and it stays 20332 after a container restart.
• Same image, new devices got devParentRelType = default (35/35) and there is no Error decoding JSON object in the log (relates to New devices get literal '[]' string in devParentRelType instead of the configured default #1798/NEWDEV_devParentRelType is declared as an array but defaults to a string: "Error decoding JSON object" on every scan, and new devices get devParentRelType='[]' #1784).
• Minor observation, in case it's not intended: /data/config/app.conf still says GRAPHQL_PORT=20212 while the effective value is 20332 (I assume the env value is applied at runtime and not written to the file).

Test container removed afterwards.

[jokob-sk]

Thanks for testing - sounds like it's working as intended.