I have used unbalanced in the past but now anytime I try to login I only get the "Something went wrong" error. This last attempt was after a reboot, and then also tried by removing and re-adding the plugin. I have also attempted with different ports and with/without authentication.

Also checking the logs I don't see any error being thrown.

Any idea on this? I'm not even sure where else to check for other issues causing this problem.

May 28 13:33:06 Apollo plugin-manager: unbalanced.plg removed
May 28 13:35:59 Apollo plugin-manager: creating: /boot/config/plugins/unbalanced/unbalanced-2026.05.17.tgz - downloading from URL "https://github.com/jbrodriguez/unbalance/releases/download/2026.05.17/unbalanced-2026.05.17.tgz"
May 28 13:36:03 Apollo plugin-manager: checking: /boot/config/plugins/unbalanced/unbalanced-2026.05.17.tgz - MD5
May 28 13:36:03 Apollo plugin-manager: creating: /boot/config/plugins/unbalanced/unbalanced.cfg - from INLINE content
May 28 13:36:07 Apollo plugin-manager: creating: /boot/config/plugins/unbalanced/unbalanced.env - from INLINE content
May 28 13:36:07 Apollo plugin-manager: executing inline script: /bin/bash '/tmp/inline4-unbalanced.sh'
May 28 13:36:07 Apollo plugin-manager: creating: /tmp/unbalanced-chkconf - from INLINE content
May 28 13:36:07 Apollo plugin-manager: running: /bin/bash /tmp/unbalanced-chkconf
May 28 13:36:07 Apollo plugin-manager: unbalanced.plg installed
May 28 13:36:52 Apollo ool www[173617]: /usr/local/emhttp/plugins/unbalanced/scripts/start
May 28 13:36:52 Apollo sudo:     root : PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/bash -c 'set -a; source "/boot/config/plugins/unbalanced/unbalanced.cfg"; source "/boot/config/plugins/unbalanced/unbalanced.env"; set +a; "/usr/local/emhttp/plugins/unbalanced/unbalanced" --port "7090"'
May 28 13:36:52 Apollo sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
May 28 13:38:11 Apollo ool www[173617]: /usr/local/emhttp/plugins/unbalanced/scripts/stop
May 28 13:38:11 Apollo sudo: pam_unix(sudo:session): session closed for user root
May 28 13:38:18 Apollo ool www[173181]: /usr/local/emhttp/plugins/unbalanced/scripts/stop
May 28 13:38:23 Apollo ool www[173617]: /usr/local/emhttp/plugins/unbalanced/scripts/start
May 28 13:38:23 Apollo sudo:     root : PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/bash -c 'set -a; source "/boot/config/plugins/unbalanced/unbalanced.cfg"; source "/boot/config/plugins/unbalanced/unbalanced.env"; set +a; "/usr/local/emhttp/plugins/unbalanced/unbalanced" --port "33104"'
May 28 13:38:23 Apollo sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)

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 ?

Could we see a modification...any move/copy would immediately delete the successul source file(s) "rsync --remove-source-files"? A live transfer between two disks without this can show two instances of files under fuse which confuses containers that expect one (Sonarr...). I know it is best practice to have things shut down but...sometimes that is not practical.

I didn't really dig and could...does Unbalanced follow the typical behavior of destination file being a .filename.XXXXX then the immediate rename upon successful transfer?

TY.

Kev.

On 6/2/2026 at 4:02 PM, TDD said:

I didn't really dig and could...does Unbalanced follow the typical behavior of destination file being a .filename.XXXXX then the immediate rename upon successful transfer?

it uses rsync underneath, iirc rsync does that by default

On 6/2/2026 at 4:02 PM, TDD said:

any move/copy would immediately delete the successul source file(s) "rsync --remove-source-files"?

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

I think the only concern with --remove-source-files is you still need to remember to rm directories, as it doesn't delete those. It only deletes files.