jbrodriguez

Only the root password works, because currently root is the only 'true' user: no other user can login in an Unraid system. It has always been like this. Check the faq (https://www.apertoire.com/faq/controlr/), section "I’m having issues accessing the app with any user other than root". So you need to add the server with 'other' user, and the root password. The permissions currently live in the user description, since root owns the system (no other user can login). I'll eventually change this in a future version.

The app is designed to work without the plugin installed, that's why you must use the Unraid webGui's port (80 or 443 by default) in the app. The plugin enables some additional features, which is why I always suggest to install it.

v2019-03-28 - 2.16.0 is out ! Some improvements / bug fixes: - Improved user experience (no more `mini game` 😁) - UI improvements - Log certificate detection - Fix open web ui link

v4.8.0 is available on the App Store / Play Store ! This release brings some improvements / bug fixes: - Support 6.7.0-rc6 - Support pause / resume parity feature - Adjust brightness (TrueBlack theme) - Change app permissions parsing logic - Completely drop 6.1.x support - Fix issue with Auto Refresh - Fix 6.4.x ops support Make sure to update the ControlR plugin (v2019.03.28) NOTES: There was still some code related to v6.1.x which I've completely removed. The app strictly support 6.2.x+ from now on.

Yes, it's my main server and I use it constantly so I hadn't found the time to upgrade 😁 My other server is on 6.6.1 or 6.6.2 I think 👍

Upgraded from 6.5.3 to 6.6.7. No problems at all. Looking forward to 6.7.0 👍 !

It has been reported a couple of times, but I haven't been able to reproduce it. Are you running a reverse proxy on the server, letsencrypt docker or similar ? Let me know, based on that let's dm to troubleshoot.

rsync was flagged due to error 13, "Errors with program diagnostics", according to its manual (some rsync erros messages are pretty opaque). Because of this error, the plugin skipped deletion of the source (skipping deletion always refers to the source). If you check the History tab, that particular operation should be shown with a yellow icon, as well as the specific rsync command that failed. Additionally, the flagged rsync command should have a 'rmsrc' (remove source) button, so that you can manually delete the source if you want to. The next rsync command in your log was flagged due to 'failed to set times', so it looks like you have some files with 'crazy' date/times. Recapping: - An rsync warned about an error 13 (probably due to irregular date/times on some file(s)) - The copy continued, but the source files weren't removed, because of the error/warning - It's now up to you to decided if the copy on the target is valid to you. So you either a - Delete the source (manually or via the rmsrc button), keep the target b - Delete the target, fix the issues on the source, copy/move again Hope this helps.

Are you sure you're running a move operation (either scatter/gather) ? Can you double check the permissions on the data that doesn't get deleted, for any issues ? Finally, the logs should show any issues while removing the source folders. You could check them or send me the relevant parts to check.

I guess you could specify just some folders of the backup set to be scattered. Depends on the size of your data mostly.

😮 I think the values are held in float64 types, so an overflow seems hard to achieve, but it certainly looks like it 🤣 🤷‍♂️

Thank you wgstarks. I'm looking into it.

Thanks ! Did it happen to you with RC5 or are you on RC4 ?

Yes, until I release a new version of the plugin. Now that RC5 is out I guess I'll have to make true on my promise and release a new plugin/app, but I'll wait 'til Tuesday for Stable 😁

Right, on the settings page set the port to 2378. It's the default port and generally it shouldn't be changed. Then make sure the plugin is running, click on the green Open webui.. link, then change the url port to 2379. It should work now. I've already fixed this in dev. I'm waiting for 6.7.x stable to release a new plugin and app, but if there's an rc5, I'll probably go ahead and publish anyway.

Ok, repeat the steps above, only this time change to port 2379 in the browser address bar/url, not in the plugin settings (I wasn't clear on that). Let me know how it goes. Sent from my iPhone using Tapatalk

It should have worked. It was a different error though, right ? Can you: - restart the plugin ( enable no, apply, enable yes, apply) - click on the link (will take you to the 2378 port) - change to 2379 manually - report the result

If you change port 2378 to 2379, can you confirm that it works ? There's some issue with the plugin php/js logic to detect whether the server is running ssl or no. I'm looking into it. Also, is your ssl set to yes or auto ?

It looks fine, I'll do some testing tomorrow and ask you for some more info, depending on the tests Sent from my iPhone using Tapatalk

Try this in a server terminal ... ps aux | grep controlr # copy the controlr exec string, it will be something like /usr/local/emhttp/plugins/controlr ... killall controlr # paste the previous command /usr/local/emhttp/plugins/controlr ... This is to get an idea of what the plugin is doing, post back the command output.

Shouldn't be the case. What error are you getting ?

Try - Enable unBALANCE server -> No - Apply - Enable unBALANCE server -> Yes - Apply Should work. Let me know otherwise.

Regarding bastl issues, we identified a couple of issues with the plugin. I'm making some adjustments that should be ready soon, most likely will wait for 6.7.x stable to release a new plugin version.

Thanks for the report Saken ! I'll take a look at it.

Yes, I saw it in the changelog, new feature in the RC 😑 Only, this time I will REALLY wait for stable, before I release a new version 👍