jbrodriguez

I'm trying to offer an insight into why the app works the way it does. I'm certainly not trying to troll you.

mikeydk, Try this ... In the Unraid Users page, set up a new user (mikey as in your example) and set a password for this user, a password that's different from root's password. Then, via any browser, access Unraid's GUI and try to login with this username/password (mikey/<password>). Does it work for you ?

I understand what you're saying, but it's currently not possible. Authentication in Unraid currently only happens via 'root' user. That's out of my hands. It's unfortunate the app doesn't work for your use case.

But the app needs to log into Unraid. That's why I mentioned that your scenario is not currently supported.

Ok, I reviewed the code. It's as I mentioned before: as per the current Unraid architecture, only root can be authenticated. There's currently no workaround for that.

Ok, bear with me, I'm trying to understand the issue you're reporting. You can't edit the username field? That is, you can't remove the 'root' text and replace it with any other text (other username) ? Or is the field not-editable ? Does it happen only for the username field ? Are you able to edit other fields ?

Also, as mentioned by itimpi, the officially sanctioned way to use ControlR remotely is via a vpn (OpenVPN, WireGuard when it makes it to the kernel/Unraid). I'm pretty sure it will sort of work remotely the way you describe it, but it's not a use case I support.

I thought you were referring to the web interface of the plugin, but you're actually referring to the app itself. It shows root just as a placeholder (currently people logs in with root, in the more general case). You can change the username, but you still need to use root's password, due to how Unraid is currently set up. There's a longer explanation in the FAQ. Or are you saying that you can't replace the 'root' username with any other username?

That's right, only root can be authenticated.

The plugin looks at the Unraid settings to connect via either SSL or not. You have SSL set to 'yes' or 'auto'. Could you try setting Unraid SSL to no, then stop/start the plugin ? It should work this way.

Are you accessing the server via https? If no, can you set SSL to 'no' and give it a try (stop/start the plugin after changing the setting).

The logs shows the chosen disk(s) and which data is being sent to each disk, in the planning step. It's located at /boot/logs/unbalance.log I'll take a look at it if you send it over (pm if you prefer).

That could be one way to do it.

If you reinstall it, does it work ?

I haven't unable to find the root cause for this. It seems to happen when running a reverse proxy on the server (a letsencrypt docker or similar). Is that your case ?

It doesn't 'balance' data across drives. Scatter will use all the free space on the drive with the most available space, if there's still content left to move, uses all the free space from the drive with the second most available space and so on.

Looks like you have SSL 'on'/'auto', so you should use the SSL port (443 by default). You can check for some other common issues in the FAQInsert other media

That's reasonable, I'll try to add it in the next release.

Hi, You have pretty much tried every fix for the issue. My main server is on 6.7.0 and I can access it, so I don't think version is the issue here. Would you mind following the instructions at https://github.com/jbrodriguez/controlr-support ? I'll be waiting for your email, and we'll take it from there.

Thanks for the detailed write up ! I'll process it and post back.

I know very little about hard links and their effect, but rsync has a hard-link option, that you can add as a custom rsync argument in the settings page. I just don't know if that would fix your use case.

I haven't installed 6.7.1-rc1 myself, but based on the changelog, the app should support it.

Yes it supports pause/resume parity checks.

v4.10.0 is available on the App Store / Play Store ! This release brings official support for Unraid 6.7.0+ All previous 6.7.x RCs are now unsupported.

You're absolutely right and thanks for the confirmation of the solution ! So for anyone with this issue, there are 2 options: edit /boot/config/plugins/unbalance/unbalance.conf, to remove lines that start with notifyCalc, notifyMove and rsyncFlags remove /boot/config/plugins/unbalance/unbalance.conf altogether, but you'll lose any custom settings