jbrodriguez

After reviewing the issue with drdebian, we found it's an issue with the default font in some Android devices. Setting the system-wide font to Roboto fixes the issue. I'll be doing some additional research into the matter, but will probably offer an option of using Robot for the app, at least.

Oh, ok. Not sure about the speed in that case. The portion of the log you sent looks fine 🤷🏼‍♂️ Be aware that move is implemented as copy then delete. If there's an operation-ending error during transfer, the original files are left intact in the source disk. You can review which command failed in the history screen.

Send me the logs, I'll take a look (/boot/logs/unbalance.log) 30/40 mbps seems about par, it's reading from a drive, then writing to a different drive and parity. I guess you reach 100mbps from another pc and using cache? Sent from my iPhone using Tapatalk

Hi, thanks for the report. Would you mind following the steps in https://github.com/jbrodriguez/controlr-support, so I can reproduce the issue with the same data ?

Hi, glad you were able to solve it.

I'd like to say a quick thanks to all of you people who donated this past year. I didn't reply individually but I certainly appreciated it (and the notes you wrote). Thanks !

The companion plugin provides the features described in the "I’ve read about a companion plugin. What’s its purpose ?" section of the FAQ

By can't uncheck, you mean it's grayed out right ? Just to be sure, you did provide enough data to the plugin to perform any given operation (chose files/folders and target drive in gather, the full steps in scatter). Other than that, I wouldn't really know. In Chrome, you could take a look at the Developer Console and check for any error.

Move works by copying then deleting, but if a command fails, it doesn't delete the source by design, so your original files are intact. You can check the operation "log" in the History tab and check which command ('rsync') failed and act accordingly (delete target folder manually, retry the operation, etc.) Why did it fail ? What does the log say ? It's a fair point. Maybe I could just leave it open, you can always click to delete it.

Thanks BRiT ! I'll look into it.

I took a look at the code with regards to SUID/SGID. It checks that permissions are "r--r--r--" or "rw-rw-rw-" (for files), "rwxrwxrwx" (for folders), so if SUID/SGID are set, it will report a file or folder permission issue. Not sure how to go about this, but SUID/SGID don't seem too common, I think ?

Yes, that happens on some Android phones for some reason. The app is just reading the phone's ip address from the network stack and proposing it (presumably less typing), but in some cases it picks up the IPv6 address. Not sure why, Android phones and even provider's OS can be quite different. As for auto, Unraid creates an SSL certificate and redirects http -> https transparently for the user, I'll check if that's still the case. Or perhaps, new installs work a bit differently from older installs (fresh 6.6.x install vs upgrading to 6.6.x).

Hi, it's written in the FAQ, from a user standpoint (what should I do as an app user), instead of from plugin's view (auto means ssl). The last version of the app always connects to the plugin via ssl, regardless of the Unraid setting, so it shouldn't be a problem You already solved it by doing ssl=yes, but I'm not sure what issue you were having. Were you unable to add the server ? Were you unable to access the additional features the plugin provides ?

I remember something like this happened before, not sure what was it. The check box is disabled until there's enough input for the operation, make sure about that. If you can try on Chrome, could you check the dev console for any errors? Last option, send me the log (/boot/logs/unbalance.log), to take a look. Sent from my iPhone using Tapatalk

Hi, I'm away from my development machine, so I can't look at the history. I'll take a look next week and report back. Sent from my iPhone using Tapatalk