• Content Count

  • Joined

  • Last visited

Community Reputation

24 Good

About ElectricBrainUK

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi guys, For the first issue I'm unsure what the problem would be unless pi hole is blocking the api somehow, though I doubt that as it doesn't really use domain names. Try reconfiguring the server in the unraid api and failing that checking the logs of both the api and the unraid server itself @Irithor glad you appreciate, happy it's worked so far. I'm surprised you got the ha app working at all as it has a few problems that I need to sort out! I guess the main thing would be to check the share it is pointing to when it tries to write to config/* and make sure it's properly
  2. I'm not as familiar with grafana but the auth is set by setting the authorization header to the base64 of username:password
  3. Hey - that is unusual Im guessing the API is sending a cached response probably something I need to fix and not a problem with your config.. Ill look into it - it should mean that you cant perform actions without auth but the bug with the cache means the data about the server is still shared
  4. Those are the logs from unraid api however I mean the ones from unraid itself - there may be something there which explains why the api is failing to connect, did you try reconfiguring the server in the api as well?
  5. Okay, I have heard a couple of users report a similar issue, I would suggest not using the HA VM one as that is in alpha and not consistently working at the best of times. For the unraid one, have you tried deleting the server altogether (in the menu on the left under manual config) and then restarting the docker and reconfiguring? This may help otherwise try deleting the config folder and starting from scratch. You could also check the server logs on unraid itself to see if there is any extra details on why it is failing to connect there.
  6. Hey, That is odd, 503 suggests it cannot authenticate or is being blocked, try re entering your server details in the ui as sometimes they expire especially if you have the config location set to secure. If you have changed the network config to have its own ip on br0.1 etc then it will not work and will throw this error though this may not be the case. You do not need the unraid api on both, the unraid one works more reliably so I would suggest using only that.
  7. Hey, it should prompt you for a username and password if you set the keystorage variable to secure, however you will also have to authenticate rest requests. Otherwise you could put the UI behind some other reverse proxy or something that adds auth
  8. Hey, currently HTTPS is not supported, you can force it to authenticate more requests by setting the KeyStorage variable to secure
  9. In unraid with the docker removed and the app data config deleted you should be fine. For HA I'm less familiar but removing the docker and then all data in the share as well as any references in the config should work fine. For others that come across the issue with cpu usage that jokeringo and I have discussed here there is a solution: https://github.com/ElectricBrainUK/UnraidAPI/issues/33
  10. No that is not normal but killing the process or rebooting your server should fix
  11. That's correct except the discovery prefix should just be homeassistant (without /tower)
  12. Do you have auto discovery enabled in your home assistant mqtt config? And do you have it configured to the same base topic that the unraid api broadcasts on?
  13. That is unusual you shouldn't have to do that, glad it's working now and thanks for letting me know. I'll see if something weird happens with the cookies when you upgrade and try to do it automatically for new users For cpu load and temperature I would recommend glances as it has all this information already and I didn't want to repeat someone else's work!
  14. 503 errors suggests that your unraid api can't connect to your unraid host, how is the networking set up? If you're using a custom bridge the docker network can't communicate with the host. Can you access your unraid ui yourself via a web browser? It is also is possible your username configured is not root, or the password you entered was wrong