I’m using homepage as the dashboard for my applications. Recently i saw on the homepage documentation, that they offer a widget for truenas which could display system load, uptime and an alert counter.
I’ve created an api token in truenas and tried to add the widget to my dashboard, but sadly i get this api error:
API Error: Unknown error
URL: http://ipofmytruenas/api/v2.0/alert/list
Raw Error:
{
"errno": -113,
"code": "EHOSTUNREACH",
"syscall": "connect",
"address": "ipofmytruenas",
"port": 80
}
Instead of the api token you can also use username and password, but i get the same error.
I’m uncertain if it’s an configuration error on my side or if the widget itself has a problem. Can anyone else who’s using homepage try to add the widget.
If it’s a problem with the widget i will file a bug report on the homepage github.
I get an API error in the TrueNAS homepage widget since the TrueNAS update to version 24.04.1. However, after a minute, the information in the widget loads successfully.
The error message says: ‘* API Error: Unexpected token ‘I’. “Invalid API key” is not valid JSON.’
But as I mentioned, after a minute, the details in the widget load successfully. It’s pretty weird.
Temporarily switch to username and password. I think it’s a problem with the switch from rest API to websocket
Edit:
And my previous problem was caused by myself. I run my docker stack from a jailmaker jail and did not use a bridge, therefore the jail could not communicate with the truenas host. After switching to a bridge all if good on that part.
Thanks for reply. I tried to switch to username and password for authentication before. I’m using special characters in username and password as well. I guess hompeage can not handle this because in this case i run into other errors.
Maybe i will simply wait for fix in TrueNas or homepage.
Same issue here and it’s pretty annoying. Even if the information appears after 30 sec or so, any click on the page makes it collapse and disappear for another 30 sec
Thank you! I saw that and I’m looking forwart to it…
At the same time, checking for updates gives back a timeout for me… I’m looking into this currently.
Until the fix drops, I can confirm that using username and password for the widget instead of an API key works fine. You can revert back to using the API key when 25.04.02 drops.