Jump to content

bnkath2o

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by bnkath2o

  1. I corresponded with Juan directly and determined that unfortunately unraid 6.1.x does not work with ControlR. He graciously processed a refund through the Google Play store. Though I am disappointed that ControlR did not work out I do completely understand the necessity to draw the line somewhere on back level support. Thank you for the outstanding timely customer service! -Ben
  2. I am trying out your app and am not able to connect to my unraid server. Steps taken: I have installed the plugin and set up a user for ControlR called control and configured said user. I can connect from my phone to the unraid GUI in Chrome. I can access http:<unraid>:2378 When I try to connect via the Android ControlR app and add manually it simply comes back with a "No servers available" message. Using http on default port 80. I do have Eset antivirus running on my devices, it may be blocking this, I will try disabling on my test phone. I am about 8 hours into my 48 hour refund window on the Play store so I'm hoping you can point me in the right direction before I have to get a refund. Config: Unraid v6.1.9 Android v8.0 (Samsung Galaxy S9+) BTW, auto config hangs when it hits one of my Netgear manage switches and never moves on. ControlR log: (note for this post I changed Mac address below) I: 2018/04/05 07:55:00 app.go:57: controlr v2.9.2-371-b91fc11-v2018.03.21 starting ... I: 2018/04/05 07:55:00 app.go:65: No config file specified. Using app defaults ... I: 2018/04/05 07:55:00 core.go:73: starting service Core ... I: 2018/04/05 07:55:00 core.go:274: No sensor detected ... I: 2018/04/05 07:55:00 core.go:287: Created apc ups ... I: 2018/04/05 07:55:00 server.go:70: Starting service Server ... I: 2018/04/05 07:55:00 server.go:89: Serving files from /usr/local/emhttp/plugins/controlr I: 2018/04/05 07:55:00 server.go:151: Server started listening http on :2378 I: 2018/04/05 07:55:00 api.go:46: Starting service Api ... I: 2018/04/05 07:55:00 api.go:99: Api started listening http on :2382 I: 2018/04/05 07:55:00 app.go:85: Press Ctrl+C to stop ... I: 2018/04/05 11:38:53 api.go:134: received /info I: 2018/04/05 11:38:53 api.go:142: info({Version:2 Wake:{Mac:xx:xx:xx:xx:xx:xx Broadcast:255.255.255.255} Prefs:{Number:., Unit:F} Samples:[{Key:UPS STATUS Value:Online Unit: Condition:green} {Key:UPS LOAD Value:9.0 Unit:% Condition:green} {Key:UPS CHARGE Value:100.0 Unit:% Condition:green} {Key:UPS LEFT Value:65.3 Unit:m Condition:green} {Key:UPS POWER Value:77.8 Unit:w Condition:green}] Features:map[sleep:false]}) Additional log after running from console commandline: (x out addresses) Note the remote IP connection attempt root@server:/usr/local/emhttp/plugins/controlr# ./controlr I: 2018/04/05 12:41:07 app.go:57: controlr v2.9.2-371-b91fc11-v2018.03.21 starting ... I: 2018/04/05 12:41:07 app.go:65: No config file specified. Using app defaults ... I: 2018/04/05 12:41:07 core.go:73: starting service Core ... I: 2018/04/05 12:41:07 core.go:274: No sensor detected ... I: 2018/04/05 12:41:07 core.go:296: No ups detected ... I: 2018/04/05 12:41:07 server.go:70: Starting service Server ... I: 2018/04/05 12:41:07 server.go:89: Serving files from /usr/local/emhttp/plugins/controlr I: 2018/04/05 12:41:07 server.go:151: Server started listening http on :2378 I: 2018/04/05 12:41:07 api.go:46: Starting service Api ... I: 2018/04/05 12:41:07 api.go:99: Api started listening http on :2382 I: 2018/04/05 12:41:07 app.go:85: Press Ctrl+C to stop ... I: 2018/04/05 12:42:04 api.go:134: received /info I: 2018/04/05 12:42:04 api.go:142: info({Version:2 Wake:{Mac:xx:xx:xx:xx:xx:xx Broadcast:255.255.255.255} Prefs:{Number:., Unit:F} Samples:[] Features:map[sleep:false]}) {"time":"2018-04-05T12:42:04.0025742-05:00","id":"","remote_ip":"xxx.xxx.x.xx","host":"xxx.xxx.x.xx:2382","method":"GET", "uri":"/api/v1/info","status":200, "latency":160814,"latency_human":"160.814µs","bytes_in":0,"bytes_out":153} Thanks in advance!
×
×
  • Create New...