Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After update NetalertX I get a Homepage api error #845

Closed
2 tasks done
JackD-01 opened this issue Oct 16, 2024 · 4 comments
Closed
2 tasks done

After update NetalertX I get a Homepage api error #845

JackD-01 opened this issue Oct 16, 2024 · 4 comments
Labels
duplicate This issue or pull request already exists Setup 📥 These are probably setup or user environment related issues.

Comments

@JackD-01
Copy link

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_HOMEPAGE_NETALERTX

My Dashboard_ERROR

ERROR_DATA_API_HOMEPAGE.txt

HOMEPAGE SETTINGS_FOR_NETALERTX

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

  • 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.
@JackD-01 JackD-01 added the bug 🐛 Something isn't working label Oct 16, 2024
@jokob-sk
Copy link
Owner

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:

#838

@jokob-sk jokob-sk added Setup 📥 These are probably setup or user environment related issues. and removed bug 🐛 Something isn't working labels Oct 16, 2024
@jokob-sk
Copy link
Owner

Also, thanks for the detailed description, this is always appreciated 🙏

@jokob-sk jokob-sk added the duplicate This issue or pull request already exists label Oct 16, 2024
@JackD-01
Copy link
Author

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

@JackD-01
Copy link
Author

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.

.
NetAlertX_sync_settings copy

Homepage_netalertx_settings copy 2

with_api_token_and logon_enabled

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists Setup 📥 These are probably setup or user environment related issues.
Projects
None yet
Development

No branches or pull requests

2 participants