JesterEE Posted February 3, 2020 Share Posted February 3, 2020 On 1/13/2020 at 7:08 PM, jbrodriguez said: Oh, the plugin may not be considering that scenario. I'll have to check the code. Quick update: I was working with another build of Unraid that allows the temperatures to be read by the temp sensors plugin and ControlR started working correctly ... confirming the bug. Quote Link to comment
jbrodriguez Posted February 5, 2020 Author Share Posted February 5, 2020 Hi, thanks. Can you provide the output of /usr/bin/sensors -A ? Quote Link to comment
JesterEE Posted February 5, 2020 Share Posted February 5, 2020 2 hours ago, jbrodriguez said: Hi, thanks. Can you provide the output of /usr/bin/sensors -A ? From Unraid 6.8.0-RC7 root@Tower:~# /usr/bin/sensors -A k10temp-pci-00c3 CPU Temp: +61.4°C (high = +70.0°C) MB Temp: +61.4°C -JesterEE Quote Link to comment
jbrodriguez Posted February 5, 2020 Author Share Posted February 5, 2020 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 Quote Link to comment
Turbo123 Posted February 9, 2020 Share Posted February 9, 2020 Hello, I used this late last year on another server that is currently down. (it worked perfectly before) I am now building a new server with the latest build of Unraid (6.8.2) and I'm having these exact problems as well. I use the Android App (latest version) My issue shares a lot of these problems with the error (1001) - Unable to get unRAID state (dockers): Get https://127.0.0.1/plugins/dynamix.docker.manager/include/DockerContainers.php: dial tcp 127.0.0.1:443: connect: connection refused I've done a lot of the troubleshooting you've already given jbrodriguez for others & I can't solve it so I'll give my problem and maybe it can help others/help you pinpoint what I'm doing wrong. The controlr plugin gives the above error when my unraid ssl is set to "auto" and only let's me log into the web app from my desktop browser when SSL is either set to "on" which I don't have a certificate for and as well as when I turn ssl off and run the command /usr/local/emhttp/plugins/controlr/controlr -port 2378 -showups without the certificate information. When I do these two things I can log into the webapp from my desktop browser and see my extra users/set permissions fine. As you can see here: https://imgur.com/a/dP6VIXK However no matter what happens the app never actually adds the server and always gives me this message when I turn on debug. https://imgur.com/a/vkhlGnR Unless I tick SSL on for the app and then it just never adds and endlessly tries to load. This is a fresh Unraid install, on a server I just built. It doesn't have any VPN's/proxies other than the binhex-qbittorent vpn docker and it has a NUT enabled UPS. I've disabled both of these and rebooted the server, it still does the exact same thing every time. I have tried using both the network ip and name both do the same thing. Thanks for any help! I love the app and is pretty amazing for the Unraid platform! Quote Link to comment
jbrodriguez Posted February 12, 2020 Author Share Posted February 12, 2020 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 ! Quote Link to comment
Turbo123 Posted February 15, 2020 Share Posted February 15, 2020 (edited) On 2/12/2020 at 6:33 PM, jbrodriguez said: 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 ! Ok... So basically it was because I was trying to use 2387 on the app... Thanks so much! Edit: I now have both of my servers up and running again and with ControlR as well. Thanks a bunch! love the software. Edited February 15, 2020 by Turbo123 Added more to post 1 Quote Link to comment
cronuslsd Posted March 5, 2020 Share Posted March 5, 2020 Hi team, I'm new to this and having a bit of a challenge. I have the app on my phone and it will connect to my server but the plugin on the server is stuck in a stopped state. I tried uninstalling and reinstalling the plugin but it wont start. Any help would be appreciated. thank you, Quote Link to comment
jbrodriguez Posted March 5, 2020 Author Share Posted March 5, 2020 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. 1 Quote Link to comment
cronuslsd Posted March 5, 2020 Share Posted March 5, 2020 1 hour ago, jbrodriguez said: 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. root@Tsunami-NAS:~# killall controlr controlr: no process found root@Tsunami-NAS:~# /usr/local/emhttp/plugins/controlr/controlr -port 2378 -showups I: 2020/03/05 08:35:02 app.go:57: controlr v2020.01.11b|2.18.1 starting ... I: 2020/03/05 08:35:02 app.go:65: No config file specified. Using app defaults ... I: 2020/03/05 08:35:02 app.go:214: cert: found Tsunami-NAS_unraid_bundle.pem I: 2020/03/05 08:35:02 core.go:73: starting service Core ... I: 2020/03/05 08:35:02 core.go:268: Created system sensor ... I: 2020/03/05 08:35:02 core.go:298: No ups detected ... 2020/03/05 08:35:02 Unable to wait for process to finish: exit status 1 I appreciate the help. Quote Link to comment
jbrodriguez Posted March 6, 2020 Author Share Posted March 6, 2020 I remember this happened a while back. It would seem like there's an issue with the system sensor readings. Can you try /usr/bin/sensors -A and post back the output Quote Link to comment
cronuslsd Posted March 6, 2020 Share Posted March 6, 2020 1 hour ago, jbrodriguez said: I remember this happened a while back. It would seem like there's an issue with the system sensor readings. Can you try /usr/bin/sensors -A and post back the output Linux 4.19.98-Unraid. Last login: Fri Mar 6 07:43:36 -0500 2020 on /dev/pts/1. root@Tsunami-NAS:~# /usr/bin/sensors -A No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. root@Tsunami-NAS:~# looks like you may be right. Any ideas on how to correct this? Quote Link to comment
jbrodriguez Posted March 7, 2020 Author Share Posted March 7, 2020 I'm not sure on how to fix the sensor readings 🤷🏻♂️ I thought I had made some changes to prevent the app from exiting, I'll need to revisit that. Quote Link to comment
The_Athereon Posted March 18, 2020 Share Posted March 18, 2020 Can someone explain what's causing this? It's preventing my phone from connecting. (Was previously working before motherboard upgrade and general system tweeks.) Quote Link to comment
jbrodriguez Posted March 19, 2020 Author Share Posted March 19, 2020 Hi, This has happened before when the plugin can't find the Unraid webUI at the given port (443 in your case). Is it possible you added a reverse proxy to your setup (letsencrypt or similar). Also, can you try changing the ssl settings of your server. Set it to either no or yes (depending on your needs) and restart the plugin to check if that helps. Quote Link to comment
DJ-BrianC Posted March 25, 2020 Share Posted March 25, 2020 Is there a way to report disk space used instead of free so it's consistent with unraid interface? Quote Link to comment
jbrodriguez Posted March 26, 2020 Author Share Posted March 26, 2020 Hi, thanks for the suggestion. I can consider that for a future release. Quote Link to comment
Danibe Posted April 8, 2020 Share Posted April 8, 2020 (edited) On 3/5/2020 at 1:14 PM, jbrodriguez said: 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. I also have a similar problem and tried this command , it gives me this Output: root@DB-Server:~# /usr/local/emhttp/plugins/controlr/controlr -port 2378 -showups I: 2020/04/08 21:26:47 app.go:57: controlr v2020.01.11b|2.18.1 starting ... I: 2020/04/08 21:26:47 app.go:65: No config file specified. Using app defaults ... I: 2020/04/08 21:26:47 app.go:214: cert: found DB-Server_unraid_bundle.pem I: 2020/04/08 21:26:47 core.go:73: starting service Core ... I: 2020/04/08 21:26:47 core.go:271: Created ipmi sensor ... I: 2020/04/08 21:26:47 core.go:298: No ups detected ... 2020/04/08 21:26:48 Unable to wait for process to finish: exit status 1 root@DB-Server:~# Edited April 8, 2020 by Danibe found a misspelling Quote Link to comment
dsmith44 Posted April 10, 2020 Share Posted April 10, 2020 Hi. I am having trouble with the sleep function. This used to work fine, and is very useful, but now sleep is ghosted out on the command strip. I've reinstalled the plugin, and wiped all trace from /boot first, as well as the s3_sleep plugin. Any ideas what could be causing this? The server sleeps find from the s3_sleep buttons. Thanks Quote Link to comment
jbrodriguez Posted April 11, 2020 Author Share Posted April 11, 2020 On 4/8/2020 at 2:31 PM, Danibe said: I also have a similar problem and tried this command , it gives me this Output: root@DB-Server:~# /usr/local/emhttp/plugins/controlr/controlr -port 2378 -showups I: 2020/04/08 21:26:47 app.go:57: controlr v2020.01.11b|2.18.1 starting ... I: 2020/04/08 21:26:47 app.go:65: No config file specified. Using app defaults ... I: 2020/04/08 21:26:47 app.go:214: cert: found DB-Server_unraid_bundle.pem I: 2020/04/08 21:26:47 core.go:73: starting service Core ... I: 2020/04/08 21:26:47 core.go:271: Created ipmi sensor ... I: 2020/04/08 21:26:47 core.go:298: No ups detected ... 2020/04/08 21:26:48 Unable to wait for process to finish: exit status 1 root@DB-Server:~# Hi, it seems like there's an issue with the ipmi sensor. Can you post the output of /usr/sbin/ipmisensors --comma-separated-output --output-sensor-state --no-header-output --interpret-oem-data Also can you check that /boot/config/plugins/ipmi/ipmi.cfg is present ? Quote Link to comment
jbrodriguez Posted April 11, 2020 Author Share Posted April 11, 2020 On 4/10/2020 at 5:43 AM, dsmith44 said: Hi. I am having trouble with the sleep function. This used to work fine, and is very useful, but now sleep is ghosted out on the command strip. I've reinstalled the plugin, and wiped all trace from /boot first, as well as the s3_sleep plugin. Any ideas what could be causing this? The server sleeps find from the s3_sleep buttons. Thanks Hi sleep depends on the s3_sleep plugin, you should have that installed. Other than that, can you check the logs for any issue regarding sleep, it should start with getfeatures:sleep: Quote Link to comment
dsmith44 Posted April 11, 2020 Share Posted April 11, 2020 (edited) 20 hours ago, jbrodriguez said: Hi sleep depends on the s3_sleep plugin, you should have that installed. Other than that, can you check the logs for any issue regarding sleep, it should start with getfeatures:sleep: s3_sleep is installed and the sleep button in the top right is working fine. I have tracked this down to Dynamix System Temp plugin - uninstall that and sleep reappears on the tool bar. Re-install the System Temp plugin and it's gone again. Edited April 12, 2020 by dsmith44 found solution 1 Quote Link to comment
JesterEE Posted April 23, 2020 Share Posted April 23, 2020 New Unraid plugin Docker Folder breaks the parsing the ControlR app does. Dockers that are on are showing as off. Quote Link to comment
jbrodriguez Posted April 23, 2020 Author Share Posted April 23, 2020 Hey thanks for the heads up ! So it changes the standard webUI for dockers and vms ? I'll take a look at it this weekend, although I can't promise anything if it's a change to the standard webUI Quote Link to comment
JesterEE Posted April 23, 2020 Share Posted April 23, 2020 12 minutes ago, jbrodriguez said: Hey thanks for the heads up ! So it changes the standard webUI for dockers and vms ? I'll take a look at it this weekend, although I can't promise anything if it's a change to the standard webUI Ya it changes the WebUI of the docker page by grouping dockers together into collapsible "folder" groups. Really, kinda handy! I'm actually hoping it gets rolled in by the Unraid devs after the bugs are ironed out 🤣. I'm not expecting a fix for ControlR as it's a plugin and not a mainstream UI feature but, just really an FYI for a known conflict. 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.