Jump to content

jbrodriguez

Community Developer
  • Content Count

    1581
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by jbrodriguez

  1. Just wanted to confirm that the app will not remove the top-level folder, as it is a user share. I believe Unraid would recreate it if needed, but, by design, the app won't delete it.
  2. It's working for me on the latest app version and 6.8.3, I'll double check later today and post back the findings.
  3. The main concept here is that unbalance should be the only tool writing to the target drive during its operation. If you can make sure that's the case while running other tools (such as plex, mover, etc), then you should be fine.
  4. Yep, there seems to be something wrong, after you hit plan, it should open a 'console' to show the operation progress. Can you check the developer's console for any errors ?
  5. I think internally rsync may spawn a couple processes. I would check the source drive status with the drive speed plugin mentioned in the top banner
  6. Hi, if you're writing to disks that are targets of an operation, the calculations will(may) be off. Let's say disk3 is the target, had 1Tb free when unbalance calculated free space, but then you write 600Gb to this same disk via mover or some other tool. So unbalance starts writing to disk3 thinking there are 1Tb free, when there are actually only 400gb free. That would be the main issue.
  7. Hi, thanks for the suggestion. I can consider that for a future release.
  8. Hi, thanks for the heads up. Which Unraid version are you using ?
  9. Hi, This has happened before when the plugin can't find the Unraid webUI at the given port (443 in your case). Is it possible you added a reverse proxy to your setup (letsencrypt or similar). Also, can you try changing the ssl settings of your server. Set it to either no or yes (depending on your needs) and restart the plugin to check if that helps.
  10. Not an expert on ssl certificates, but the error says you're accessing the server via an ip address while the certificate is built for a hostname (RVC-NAS.local). I'd guess try that ?
  11. Yes, the websocket that manages traffic between the server side of the app and the ui is having certificate issues. Which Unraid version are you running ? I just tried on the latest Firefox and Unraid 6.8.3 and it's working fine. Do you have self-signed certs ?
  12. Hi, the PLAN button should show a ton of additional logging. Can you check the dev tools in Chrome, to see if there's any error there ?
  13. Hey ! Thanks a lot for the kudos ! 👍🏼
  14. That makes sense. Yes it can get chatty if you have a lot of folders, it's transferring the whole state of the operation to update the UI. I've had a couple of ideas on how to improve that, but not enough time Also, that was brought up before by another user and that's where the refresh time setting came from.
  15. Wanted to add a comment regarding UD .... it's definitely not trivial, as the app's logic assume the disks are part of the array. It's doable, but it'll take some time, I'll do it piecemeal.
  16. Yep, pretty much what jbat66 said. The underlying rsync currently can only move data between /mnt/{diskX,cacheX} drives, it doesn't hit the network at all.
  17. I'm not sure on how to fix the sensor readings 🤷🏻‍♂️ I thought I had made some changes to prevent the app from exiting, I'll need to revisit that.
  18. I remember this happened a while back. It would seem like there's an issue with the system sensor readings. Can you try /usr/bin/sensors -A and post back the output
  19. Hi, can you try running the plugin from the command line to check the output ? Something like killall controlr /usr/local/emhttp/plugins/controlr/controlr -port 2378 -showups run both commands on the command line and post the output here.
  20. That sounds good to me ! 😁 👍🏼
  21. Hey @gfjardim, I'll tell you what, I'll take a hard look at the level of effort for this change this weekend, so I can have a better sense of what it involves. I'll post back when I've done it.
  22. Hi, this generally appears when some software other than unraid is listening on port 443. This can happen if you have a proxy in place, you can probably look into that. I'm thinking to rewrite the plugin, so that this will be a non-issue in the future.
  23. I don't really mind to fix it the way Squid proposes (as soon as I can spare some cycles), although I do need to wrap my head around what I actually need to do I'm trying to figure out if that requires a new github repo for the replacement. Or perhaps I can just change the name of the tgz artifact to something different ? And then on unraid, instead of `/boot/config/plugins/unbalance` and `/usr/local/emhttp/plugins/unbalance` I would need to change it to `/boot/config/plugins/unbalanced` and `/usr/local/emhttp/plugins/unbalanced` (for example) ? What about the plugin name, would that need to change ?
  24. Hi, I think I didn't get the notification for your post. To understand, if you tick SSL on, then the app finds the server ? In any case, the error message the app is getting is a 404. Are you sure you're setting the correct port for the server on the app? If you haven't changed the defaults, 80 if http, 443 if https. Let me know if that helps !
  25. Hi, Squid posted the reason for the "v". I'm not sure I follow BRiT, changing it to a "w" would work better ?