Refreshing network view causes "[api] Unauthorized access attempt - make sure your GRAPHQL_PORT and API_TOKEN settings are correct" error

[AlexEardley]

When I attempt to refresh the Network view using NetAlertX's refresh button, it briefly displays "Loading" (the box containing the text and the spinner remain) and then logs the "[api] Unauthorized access attempt - make sure your GRAPHQL_PORT and API_TOKEN settings are correct" error.

It is only the Network page which exhibits this issue - the refresh button works as expected on all other pages.

I had a quick look at what was happening using the developer options and it seems that the request is missing the auth token when triggered from the network page, but not from other pages.

And at this point, I am pretty much out of my depth!

Anybody else experience this behaviour?

Any input welcome!

[jokob-sk]

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

⚠️ Please back up everything first, or ideally spin up a separate container 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

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

Thanks in advance,
j

[AlexEardley]

Hi J,

I can confirm that the bug does not occur when using the dev image - clicking refresh works as expected, though when selecting a network device in the map, the information in its tab below doesn't necessarily reflect the map itself and the current state of devices i.e. the connected devices aren't displayed correctly.

Thank you - I'm happy now, knowing it's nothing I managed to fu myself!

Loving NetAlertX so far, but you can expect a couple of posts in the Ideas category as I get to know it more... ;)

Alex

[jokob-sk]

Thanks for testing and the report. This should be fixed in the next release.
It would be great if you could test the ghcr.io/netalertx/netalertx-dev Docker image in ~15 minutes (or once the latest GitHub Action finishes).

⚠️ Please back up everything first, or ideally spin up a separate container 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

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

Thanks in advance,
j