jbrodriguez

hey, that's a good question, i hadn't looked at it this way this plugin always had a closed source component, as it's mostly an extension of the mobile app it provides an api to some functionalities not readily available from unraid initially i implemented a role based access for the app (different users had different permissions), but this became too cumbersome with unraid's "one user (root)" implementation, so i dropped that the other "ui" functionality was to calculate the qrcode to add a server, but it was just too much to have a full ui just for that so, i moved the qrcode to the unraid plugin page i recently found a bug related to the qrcode data, it was always returning http protocol, even if the server was set to https, so i fixed the bug and decided to remove all the dead code and leave only the api services needed for the mobile app (which was always closed source) however i really hope to deprecate this plugin once unraid makes it's api publicly available P.S.: not sure about community app rules 🤷‍♂️, however there are some other plugins in the community apps that are not open source (tailscale comes to mind)

IMPORTANT NOTICE if you're getting the following error for the controlr PLUGIN, please uninstall the plugin / then reinstall i had to change the location of the plg file and it causes this issue

not really sure, from your experience it would seem it doesn't work

IMPORTANT NOTICE if you're receiving the following error for the controlr plugin please uninstall the plugin / then reinstall i had to change the location of the plg file and it causes this issue

hi, i'm not sure if wireguard allows for a broadcast packet to work correctly, a wakeup signal is a magic packet sent to the .255 address of the lan (192.168.1.255), however each device on wireguard is set up in as "separate" network (192.168.2.1), not sure if that packet will be forwarded from 2.1 to 1.255

i missed this post 😮 could you try the newer version of the app ? it shows a different log (instead of [object Object]) does it work if you add the server via https (instead of http) + tailscale ip ? i'll probably be changing the input, so that a user can paste the browser url instead of splitting the url components

right, those are 2 different folders, not sure why on the unbalanced ui, the selection comes as Movies/Music instead of Media/Music 🤷‍♂️

there's something odd about your data, these folders can't be found by the operating system, when issuing a stat command 🤷‍♂️ if you run the following on the command line, does it work ? stat /mnt/disk1/Movies/Music but that's not the "it hangs spinning" problem, i think this isn't good, it means some value can't get converted to json format, i wonder if some size is getting misread by the os (given the os error above), this is what's probably causing the ui to hang, but can't tell for sure is that a healthy drive or it has some issues ? in any case, there's no data transfer happening, it's always coming up with "zero" bytes to transfer,

select one of the items on the left sidebar (transfer operations), it will show a list of transfer rsync commands on the right pane

mmm that seems to be a bug, can you do a t tail -f /var/log/unbalanced.log if that doesn't show anything do a cat /var/log/unbalanced.log it does seem to be running but for some reason, the ui isn't picking up notices about current state of the transfer

you can take a look at the history tab, it will show the successful commands with a green icon and the failed transfer (stopped) with a red icon the files referenced by the transfer with the red icon are still on the source disk, you can remove them from the target/destination disk

hi, currently not possible to opt out from the default args, you can only add arguments could probably make it fully configurable, although it can be risky (for non-experienced users) 🤷‍♂️

ok, so the issue is before that, i'll check the code

this is sort of odd, looks like it can't list the items below the Truenas4 folder can you run find "/mnt/disk1/TheHub/Truenas4/." ! -name . -prune -exec du -bs {} + you don't need to post the whole listing, just the first couple of entries (just the size, edit the name if you want)

rsync error 23 can be triggered by many different reasons, which are not clearly specified due to that, unbalanced plays it "safe": - it flags the command producing the error 23 - does not remove the source folder/files which triggered it this gives you a chance, as the content owner to - check if the files in the destination look ok (probably a spot check or more thorough check if you have important data) - allow you to remove the files on the source, via th rmsrc button on the history page, if you find the folder/files state to your satisfaction to recap, rsync error 23 is too vague to be handled automatically, so it requires some user attention in order to validate the transfer

oh right, i misread the screenshot, unbalanced looks for children of a selection in order to transfer files, what if you select truenas4 folder and unselect $RECYCLE.BIN and any other file/folder you don't want to be transferred

i see, it's not finding anything to transfer, the 1 byte is just a default instead of selecting the children of $RECYCLE.BIN, can you select $RECYCLE.BIN itself ? however, i think someone mentioned here or in github that it doesn't transfer files/folders that start with a $, i haven't been able to confirm that.

can you check the logs in /var/log/unbalanced.log ?

oh cool, that makes sense, i'll check for those changes in my code, thanks for pointing this out !

hi, it should work even with the nut plugin, but perhaps something changed "recently" i'll look into it

unbalanced was recently featured as the Feb 2024 app of the month thanks to the Community Apps team (@Squid 😀) and also thanks to all the people that have sponsored development of the app Thank you ! ♥️ https://github.com/jbrodriguez/unbalance

can you post a screenshot of the issue ?

hi, can you check in the history tab if there are some yellow marked commands for that operation ? they should have a rmsrc button that you can use to delete the source folder, just make sure that your target folder is ok. this happens because rsync flagged the command with some error (generally timestamps, permission or possibly i/o errors)

this is hal, all your base are belo^C^C ... i mean, the switch went fine, thanks for your help ! 🤣

hi, the mobo on my 2nd server died, so i purchased a new one, however the it won't boot my usb for some reason 🤷‍♂️ (it's a VERY old kingston 2gb) i purchased a new usb, installed unraid via disk creator and it boots 👍 i have the access to old usb contents and made a copy on my workstation so, this is what i'm currently thinking - copy the pro key to the config folder on the new usb - restore old config to the new usb and this is where i'm stuck config is quite big on the old usb, so i'm not sure what to copy, should i copy it all ? any other thoughts ?