jbrodriguez Posted October 20, 2019 Author Share Posted October 20, 2019 On 10/18/2019 at 7:40 PM, ErikM1970 said: Thank you! Sent from my iPhone using Tapatalk Pro 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) ? Quote Link to comment
jbrodriguez Posted October 21, 2019 Author Share Posted October 21, 2019 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. Quote Link to comment
ErikM1970 Posted October 21, 2019 Share Posted October 21, 2019 As requested: coretemp-isa-0000 CPU Temp: +41.0°C (high = +80.0°C, crit = +90.0°C) Core 0: +36.0°C (high = +80.0°C, crit = +90.0°C) Core 1: +40.0°C (high = +80.0°C, crit = +90.0°C) Core 2: +41.0°C (high = +80.0°C, crit = +90.0°C) Core 3: +40.0°C (high = +80.0°C, crit = +90.0°C) Core 4: +39.0°C (high = +80.0°C, crit = +90.0°C) Core 5: +39.0°C (high = +80.0°C, crit = +90.0°C) Core 6: +40.0°C (high = +80.0°C, crit = +90.0°C) Core 7: +37.0°C (high = +80.0°C, crit = +90.0°C) power_meter-acpi-0 power1: 203.00 W (interval = 1.00 s) Quote Link to comment
jbrodriguez Posted October 21, 2019 Author Share Posted October 21, 2019 Thanks ! I'll work with that. Quote Link to comment
jbrodriguez Posted October 21, 2019 Author Share Posted October 21, 2019 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 ? Quote Link to comment
ErikM1970 Posted October 21, 2019 Share Posted October 21, 2019 Unraid v6.7.2This issue manifested itself right before I sent the email in this forum approximately three months ago. I think it happened when I installed 4.15 maybe?As for my settings, please see graphic...Sent from my iPhone using Tapatalk Pro Quote Link to comment
jbrodriguez Posted October 23, 2019 Author Share Posted October 23, 2019 (edited) 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 Edited October 23, 2019 by jbrodriguez Quote Link to comment
jbrodriguez Posted October 25, 2019 Author Share Posted October 25, 2019 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) Quote Link to comment
danioj Posted December 29, 2019 Share Posted December 29, 2019 Hi, since upgrading recently, I have been having an issue logging in - in that I can't. Unraid version: 6.8.0 Stable Controlr version: 4.16.0 OS: Android (December 2019 patch) Phone: Galaxy S9 Protocol for accessing Unraid: http After upgrading from last stable of unraid to the current stable I tried to log in via Controlr and it just hung. So I removed the profile and tried to add it again. I experienced the following (repeatedly): Automated method: Click + Add username and password Keep https button unchecked Hit Discover Goes back to Server UI and does nothing. Manual method: Same as above but add hostname (also tried using IP address) Hangs with a spinning wheel and a message saying 'Adding host <IP address> indefinitely. Port is port 80 (unchanged from unraid default). Nothing else has changed since upgrading (except password change) when all worked well and has done since you released the app. I can log into the Unraid GUI via a browser just fine. Have removed app and reinstalled. Same thing happens. Have also reset phone to factory (for another reason) and that didn't have an effect either. In the Unraid log there is a corresponding line for each attempt: 'Dec 29 17:11:37 unraid webGUI: Unsuccessful login user root from <IP address>' I use a reasonably long password with mixed case letters, numbers and symbols. Quote Link to comment
jbrodriguez Posted December 29, 2019 Author Share Posted December 29, 2019 Hi, is it possible that some characters in the password are not being echoed correctly ? Just about the only thing I can think of. In any case, try the following: - 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 Quote Link to comment
danioj Posted December 29, 2019 Share Posted December 29, 2019 (edited) 3 hours ago, jbrodriguez said: Hi, is it possible that some characters in the password are not being echoed correctly ? Just about the only thing I can think of. In any case, try the following: - 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 Hi, done. Trying automated find, results in same behaviour as described above and no debug log to post. Trying manual add, results in the following: EDIT: Googled the error, reckon it is a special character parse problem. Given the complex password I use I'm guessing your gut feeling is right. EDIT2: if it helps, I'm willing to change my password and share the password that doesn't seem to be working to help debug. It's auto generated by the password manager anyway so no bother. Edited December 29, 2019 by danioj Quote Link to comment
jbrodriguez Posted December 30, 2019 Author Share Posted December 30, 2019 Hi, the JSON parse error is about the ControlR plugin, I think it believes you're on https, while you're actually on http. There should be another debug line below the scanServerCheck. Can you try setting your Unraid SSL setting to 'no', just to check if that solves the issue ? Quote Link to comment
danioj Posted January 1, 2020 Share Posted January 1, 2020 On 12/30/2019 at 11:05 AM, jbrodriguez said: Hi, the JSON parse error is about the ControlR plugin, I think it believes you're on https, while you're actually on http. There should be another debug line below the scanServerCheck. Can you try setting your Unraid SSL setting to 'no', just to check if that solves the issue ? Hi, I did as you asked. My SSL setting was Auto (as is the unraid default I believe), i set it to 'no' as requested and tried again. The result was identical. I won't post the image again as it was literally identical, down to the unraid log of unsuccessful login. You mention that there should be another debug line, there is not. I have tried scrolling, copying etc, and nothing. Quote Link to comment
jbrodriguez Posted January 1, 2020 Author Share Posted January 1, 2020 Mmm, ok that's odd ... it means that the server is actually returning some data. Couple of thoughs: do you have a reverse proxy in front of the unraid ui (letsencrypt or similar) ? Is the unraid UI on some port other than 80 ? Finally, can you try the instructions here https://github.com/jbrodriguez/controlr-support ? Quote Link to comment
ErikM1970 Posted January 1, 2020 Share Posted January 1, 2020 Unraid v6.7.2This issue manifested itself right before I sent the email in this forum approximately three months ago. I think it happened when I installed 4.15 maybe?As for my settings, please see graphic...Sent from my iPhone using Tapatalk Pro Please don’t forget about my temperature issue.—Sent from my iPhone using Tapatalk Pro Quote Link to comment
jbrodriguez Posted January 2, 2020 Author Share Posted January 2, 2020 I haven't forgotten, it's more like I haven't been able to replicate it 😮 I need to work on the plugin, so I'll try something as soon as I get there. Quote Link to comment
jbrodriguez Posted January 4, 2020 Author Share Posted January 4, 2020 I made a small change to the ControlR plugin (now v2020.01.04, v2.7.1), can you check if that solves your issue @ErikM1970 ? Quote Link to comment
ErikM1970 Posted January 5, 2020 Share Posted January 5, 2020 I made a small change to the ControlR plugin (now v2020.01.04, v2.7.1), can you check if that solves your issue @ErikM1970 ?I just applied the updated plugin and now the temperature value no longer appears whatsoever on the iOS application.—Sent from my iPhone using Tapatalk Pro Quote Link to comment
jbrodriguez Posted January 5, 2020 Author Share Posted January 5, 2020 Well, there's some progress Can you follow the steps in https://github.com/jbrodriguez/controlr-support Also, one more time /usr/bin/sensors -A Quote Link to comment
ErikM1970 Posted January 5, 2020 Share Posted January 5, 2020 Well, there's some progress Can you follow the steps in https://github.com/jbrodriguez/controlr-support Also, one more time/usr/bin/sensors -A Done!—Sent from my iPhone using Tapatalk Pro Quote Link to comment
ParkerSaj t Posted January 6, 2020 Share Posted January 6, 2020 Hi, I cannot connect to my server, this is what it says: Quote Link to comment
jbrodriguez Posted January 6, 2020 Author Share Posted January 6, 2020 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 ? Quote Link to comment
jbrodriguez Posted January 11, 2020 Author Share Posted January 11, 2020 (edited) 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) Edited January 11, 2020 by jbrodriguez Quote Link to comment
Haugi Posted February 1, 2020 Share Posted February 1, 2020 Hi, i use a vpn to my homenetwork and want to start the server from your app. This dosent work any more. I can use everything fine when i`m normaly connected to the local lan. I use the fritzbox vpn client. Can you help here? Thx Quote Link to comment
jbrodriguez Posted February 1, 2020 Author Share Posted February 1, 2020 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 ? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.