System health axios error
Can not for the life of my get system health to display anything
I have a user/group setup in prox, api key has the correct permissions when viewing in prox and if login to the homarr pve user and go to the api link manually I get the expected output
Solution:Jump to solution
And you followed the instructions on concatenating the API token? 401 is the unauthorized code so it's absolutely a permission issue, just need to find out which part is incorrect.
15 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
This question gets asked a lot and it's usually permission issues. Can you send a screenshot of the permissions in proxmox?
It persists no matter the way I assign permissions. via user, group, or API and with Admin it still occurs
tried a few different ways just to make quadruple check. Am I missing a step? Create a user, assign a group(optional), gen api token for user. add user, group, or api to vm permissions with audit(admin for testing)? This has been my first time doing anything with prox perms
You really only need a user with pve auditor permissions. Anything else is unnecessary. After you have the user, you make the api token. Once the api token is made don't forget to give permissions to the user and api token iteself.
still persists
I can get it to work in postman, don't know if that indicates anything
Solution
And you followed the instructions on concatenating the API token? 401 is the unauthorized code so it's absolutely a permission issue, just need to find out which part is incorrect.
please note: a 401 on the ping does not mean there's an issue, it's only an issue if the widget it's linked to doesn't work either.
(pings do not use the integrations tokens so there are chances of unauthorized there)
Unless I'm reading wrong, the 401 error is a response from the proxmox API and not from the homarr ping.
Yeah I'm not sure either, it's just that if appears in the console, it may just be the ping not resolving while the widget could be perfectly fine.
I've seen people try to enter the full path to the API in the internal field instead of just the address, resulting in very confusing logs
Fair point. Haha. Troubleshooting is the hardest part.
no 😞 got it now. thanks. should've clued in to trying that after setting it up in postman but never crossed my mind. Thanks
Glad it's working. :)