jbrodriguez

Hi, can you try running the plugin from the command line to check the output ? Something like killall controlr /usr/local/emhttp/plugins/controlr/controlr -port 2378 -showups run both commands on the command line and post the output here.

That sounds good to me ! 😁 👍🏼

Hey @gfjardim, I'll tell you what, I'll take a hard look at the level of effort for this change this weekend, so I can have a better sense of what it involves. I'll post back when I've done it.

Hi, this generally appears when some software other than unraid is listening on port 443. This can happen if you have a proxy in place, you can probably look into that. I'm thinking to rewrite the plugin, so that this will be a non-issue in the future.

I don't really mind to fix it the way Squid proposes (as soon as I can spare some cycles), although I do need to wrap my head around what I actually need to do I'm trying to figure out if that requires a new github repo for the replacement. Or perhaps I can just change the name of the tgz artifact to something different ? And then on unraid, instead of `/boot/config/plugins/unbalance` and `/usr/local/emhttp/plugins/unbalance` I would need to change it to `/boot/config/plugins/unbalanced` and `/usr/local/emhttp/plugins/unbalanced` (for example) ? What about the plugin name, would that need to change ?

Hi, I think I didn't get the notification for your post. To understand, if you tick SSL on, then the app finds the server ? In any case, the error message the app is getting is a 404. Are you sure you're setting the correct port for the server on the app? If you haven't changed the defaults, 80 if http, 443 if https. Let me know if that helps !

Hi, Squid posted the reason for the "v". I'm not sure I follow BRiT, changing it to a "w" would work better ?

Hey, I'm not sure why I asked you about sensors, that has nothing to do with the APC ups 🤷🏻‍♂️ Could you please send the output of /sbin/apcaccess ? And finally, try this. killall controlr Then /usr/local/emhttp/plugins/controlr/controlr -port 2378 -certdir /boot/config/ssl/certs -showups and post back the output

Hi, thanks. Can you provide the output of /usr/bin/sensors -A ?

Hi, using the VPN should be the same as being on the physical LAN, I don't have any experience with fritzbox though. One thing you need to make sure is that port 2382 is available on the VPN. Maybe you're restricting some ports if coming from the vpn tunnel ?

Hi, that response "JSON Parse error: Unexpected identifier OK" indicates that there seems to be a proxy or something similar in place. Can you confirm this ?

Yes, you need to select source /destination for the checkbox to be enabled

Hi, is it possible you are running Unraid 6.8.2, just curious ? This issue has surfaced before and it's more common when there's a reverse proxy sitting in front of Unraid (such as letsencrypt for example) Is that your case ? As for the app, can you try this ? - Go to Settings > Open Source Libraries - After the react native credits, you’ll find a debug button, hit it once (counter should read 1) - Now try connecting manually (you should see a ‘debug initialized ‘ message at the bottom) - It should go back to the main screen - Go to manual add again - It should be displaying some debug message - Take a screenshot and send it over Let me know how it goes

Hi, it moves all the folder/files below the root you select, but only those folder whose size can fit into the available space in other disks. Hope that makes sense

That's odd, I just tried it and it's working. Do you think there could be a network issue on your lan ?

Yes, that's the latest. Would you mind following the steps in https://github.com/jbrodriguez/controlr-support ?

Oh, the plugin may not be considering that scenario. I'll have to check the code.

Hey @darrenyorston, have you upgraded the mobile app to the latest version (which supports Unraid 6.8.x) ? The app still works without the plugin.

Just make sure that the plugin is actually running ... in the plugin settings page, set it to disable server, apply changes, then set it to enable server, apply changes and it should work.

v2020-01-11b (2.18.1) is out ! This fixes the formula to convert Celsius to Fahrenheit for the system and ipmi temperature sensors. Thanks a lot @ErikM1970 for helping in figuring this out !

Thanks a lot for the kind comments @airport!

Upgraded the plugin ! 2020-01-04 - 2.17.2 Debug logging

Hey @ErikM1970, I check the support files you sent but I can't seen anything unusual with them. So I created a new version of the plugin, to try and debug the issue. So pls try the following - Upgrade the plugin to v2020.01.11 (2.17.2) - On the command line do killall controlr /usr/local/emhttp/plugins/controlr/controlr -port 2378 -certdir /boot/config/ssl/certs -showups That last `-showups` should be there only if you have UPS enabled in the controlr settings, otherwise just remove that part. Then access the server from the mobile app, it will display some log lines in the command line, please post those log lines here (or send them via pm if you prefer)

Hey @JesterEE, I somehow missed your post. Do you have an APC ups on your system ? Can you try disabling the UPS setting on the plugin to check it that works ?

Hi that error is about the plugin, if you haven't installed it, there shouldn't be a problem. Can you follow the steps in https://github.com/jbrodriguez/controlr-support ?