jbrodriguez

v2019.10.26 (5.6.3) is available ! - Support 6.8.x - Add missing isNumber function - Upgrade some libraries - Switch to yarn

I'll look into it in upcoming releases

Hi, I'm able to connect to my server using http, so it should work. 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 via http (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 (pm if prefer)

v4.16.0 is available on Apple and Google Stores ! - Initial 6.8.x support Let me know if you find any issues P.D.: still can't figure out the temperature unit issue, but I think it's on the plugin side

I can't put a finger on it.. with your data and preferences set to Farenheit, it returns 73 degrees. What Unraid version are you running (to have an idea when this may have started) and what are your temperature settings ?

Thanks ! I'll work with that.

v4.15.2 is available on Apple App Store ! It fixes an issue that was preventing the execution of some commands on the server. ***NOTE: this completes the fix that was made previously available for Android.

Hi, I'd appreciate your help in fixing this. Can you run /usr/bin/sensors -A on your command line and post back the results (pm if you prefer) ?

I know what the issue is, it's a permissions issue. The plugin creates a log file on /boot/logs/unbalance.log and also writes a config file at /boot/config/unbalance.{conf,cfg} /boot and /boot logs have root:root ownership. By default, the plugin settings page runs the plugin as the nobody user. You can change the user you want unbalance to run as, but you can't choose root (this was a design decision I made) So when run as nobody, unbalance fails to create the log file at /boot/logs and exits. That's why it works when you run it from the command line: you're running it as root. I figure that the new user system in. 6.8.x enforces some permissions, so access to this folder is not allowed for a user that has less privileges than root (nobody in this case). I have to think how to solve this, but for the time being, the workaround is the workaround Some ideas to fix it: - allow unbalance to run as root (from the plugin settings page) - wip If anyone has ideas on how to fix this, I'd be glad to hear them 👍

v4.15.2 is available on Google Play Store ! It fixes an issue that was preventing the execution of some commands on the server. This should fix it ! **** Note that this affects iOS too, but Apple Store is throwing a fit today (actually they have a scheduled maintenance of about 8 hours 😮), so it'll become available for iOS soon.

Well, it's a release candidate, so there may still be changes about (it has happened in the past), that's why I generally support only stable releases. In any case, I'm looking to take a stab at this tomorrow.

v4.15.1 is available on the Google Play Store ! It's a hot patch to fix the issues people were having on Android, connecting to an Unraid server with SSL off. This should fix it !

@roastdawggYou're the man ! Thanks for looking into this ! It makes total sense now, my test server is currently on ssl, so it worked when I tested. SSL should be the way to go, even inside the LAN, I'll add the config anyway, hopefully should push an Android-only build by tomorrow at the latest.

I replied on the wrong post but the idea is the same

<snipped> When I was posting the updated version I came across your post about this issue. I have it open in my gitea host (see below), just haven't been able to get it. It should be a quick fix (I think), so I'll work on it once I have preliminary 6.8.x support. And thanks a lot for the reminder (and patience) !

Hi, I tried to replicate this on an android simulator running android 10 (api level 29) and it works. I've also seen from the analytics logs, that there many users on api level 29 using the app successfully. I'm not sure where the "CLEARTEXT communication not allowed by network policy" comes from, is it possible you have some ad blocker, firewall policy, anything usual you can think of ? Another question, is the controlr plugin running on the unraid server ? If it's installed and running, the screenshot shows that the app is unable to connect to it as well (on port 2382). Let me know.

Hi, thanks for your comment. I remember that a LONG time ago 😀, Squid offered a way to hook up into the Community Applications API, so that the app could do that kind of stuff. It's been a while since that and things may have changed under the hood, so I'll need to revisit that. It's #4 in the requests order, but ... hey ! I just implemented #3: Unassigned Devices ! I'll eventually get to it !

Hey, thanks a lot for the detailed report ! I haven't tested the app on Android 10, I suspect it has something to do with that. I'll check it today/tomorrow and post back here

v4.15.0 is available on Apple and Google stores ! 4.15.0 This release brings initial support for the Unassigned Devices plugin. Also, the library that provides analytics and crashes has been replaced. It was Fabric/Google, it's now Appcenter/Microsoft. This is in order to better support GDPR requirements. More on the topic later on. Please check the updated privacy policy for further details. Other changes are: - Core libraries upgrades - Improved performance on Android - Other bug fixes and improvements Please not that this release doesn't address the connection issues with 6.8.x, this is a work in progress and should be ready (hopefully) by the time 6.8.x hits stable.

Short Answer: no Long Answer: no Sorry, not possible at this time.

You're right, probaby the log for the incorrect pwd was when plex was running. I think I'll add a config option to set which port is listening on, to override whatever the plugin thinks it's on .. I'll look into it for the next release

I'm pretty sure it won't work. The authentication flow changed, so the app needs to be adjusted for that. I'm thinking of looking into it by this weekend, although as stated before, I don't really support release candidates.

Hey, you actually have a password issue .. the line W: 2019/10/15 07:24:33 server.go:257: shadowHash != actualHash means the root password you're entering is not correct. Can you double check that ? What I think may be happening is you have SSL set to auto, so the plugin thinks your https is working, when actually it's being used by Plex. Just thinking out loud.

Yes, if it shows Plex using 443, it looks like Unraid is listening on some port other than 443. Can you check that in the Unraid settings ?

The bottom line of the issue is that from the command line, something/someone (😮) other than Unraid is answering on port 443, thus the connection refused error. Can you try lsof -i :443 from the command line and report back ? I've tried that with other users reporting this issue in the past, without much success, but maybe it prints something useful in your case.