jbrodriguez

@nearcatch made some changes to the proxy origin detection, try this version, let me know how it goes

released 2026.09.11 adjustment to proxy origin detection

@nearcatch i missed your reply, still not sure what the problem is, i released a new version that logs (sanitized) auth rejections whenever you can give it a try and pls share the /var/logs/unbalanced.logs related to auth

released 2026.09.10 log websocket auth rejection logging any rejections during handshake, for troubleshooting

can you show dev tools console when it fails ?

released 2026.08.29 fix auth under a reverse proxy this should work now, i tested on my server and it worked, let me know of any issues

released 2026.08.28 add shift-click range selection to the folder tree another contribution from dotCooCoo on github, this works on the gather selection pane let us know how it works 😀 i think i have a fix for the reverse proxy issue, will look to land it over the weekend

yea, definitely looks like reverse proxy breaks auth, ill take a look

released 2026.08.07 make the plan phase cancellable, hang-proof, and honest about progress this was an awesome contribution by dotCooCoo on github, makes the planning step a lot more robust !

released 2026.07.18 make the logs page filterable and its length configurable record why a command failed and show it in history show per-disk and total sizes in the gather presence panel Fix gather plan log label thanks to dotCooCoo on github for these changes (the first 3 ones are his) note: (there 2 additional changes, one that improves planning a lot and another that adds multi selection on the folder ui, will merge them soon)

it uses rsync underneath, iirc rsync does that by default move works by doing rsync, then running "rm *" on the source, there has been some discussion about this, "--remove-source-files" could probably work, but would need to take a look, i don't remember if that works at a file level or at the command level, in any case it would be a departure from current logic

hey, hmm you can check /var/log/unbalanced.log, but im guessing it might be a ui error if you're on chrome, can you click on the menu View -> Developer -> Javascript Console ? it may show an error there, can you post a screenshot ?

ill add an issue to look into this

released 2026.05.17 implements a time window to calculate speed (and remaining time) this uses the last ~90 seconds to calculate speed (instead of the previous fixed 60 samples), should prevent some integer overflow that could have been happening

that would be a balanced move, but this is something built in into Unraid, with the allocationg logic (high water, etc) many ppl here prefer to fill up disks, rather than having data scattered to serve as sort of "read-only/archives", there are some threads on the matter what's unusual is what you mention about filling the first drive then failing, if you have the logs related to the error, i could take a look finally, even though "balancing" disks is currently not supported, one of my goals is to have pluggable algorithms/logic, to move/copy files around: one of these algorithms could be to balance disks, versus the default one: fill one disk, then the next and so on. not there yet tho, hopefully sometime this year