Closed JackD-01 closed 1 month ago
Hi there,
Please disable login or wait until the related Homepage version is released supporting NetAlertX instances with enabled login. See this issue for details:
Also, thanks for the detailed description, this is always appreciated 🙏
Thanks for the feedback, nice to read that I did not do something wrong :-) For now I disable login and wait for a new release of Homepage with support for enabled login. I closed down access from outside my private network to NetAlertX for security.
Thank you for your advice,
Regards, Jack
Just some additional info for others with the same problem..
Took a closer look and you can run NetAlertX with login enabled with Homepage v09.11, as stated by jokob-sk Add sync plugin in NetAlertX(if you don't already), generate a token and copy it into the "API token [n,h]" field, and set "when to run" Use the same token in the services.yaml settings file from Homepage and you now have NetAlertX with logon enabled and you got the NetalertX info presented in the Homepage wigdet.
.
Is there an existing issue for this?
Current Behavior
After updating NetAlertX to v24.10.12(docker) the homepage software gives a api error. It does not show the NetAlertX info on homepage software. (I did refresh an delete tempfiles/cookies) Nothing changes on the homepage software side, I run the latest version (v09.11)
Is there a change on how to get the info out of NetAlertX, do we now need perhaps a api key?. If this is the case than I have to post the bug on the Homepage. (GitHubhttps://github.com/gethomepage/homepage) But for now I put the possible bug/problem here first. because the problem started with the new NetAlertX update I did.
Hope you can help, I am not a programmer, just a happy NetAlertX user, so forgive me if I ask or say something "stupid"
Regards, Jack
ERROR_DATA_API_HOMEPAGE.txt
Expected Behavior
I would like to see "totaal", "connected", "new_devices" and "down_alerts again on my homepage software.
Steps To Reproduce
No response
app.conf
No response
docker-compose.yml
No response
What branch are you running?
Production
app.log
No response
Debug enabled