jbrodriguez Posted January 24, 2019 Author Share Posted January 24, 2019 Odd. I get 'loading' for a sec or two, then it shows the content. Let's chalk it to gremlins in the machine. 😁 Quote Link to comment
darrenyorston Posted January 30, 2019 Share Posted January 30, 2019 Hi there. I am using unraid v 6.6.6, ControlR v 2018.10.3, and ControlR android app v 4.5.0 I have the user account set to only show a single VM with visible, read, and exec checked. All other VMs or Docker containers are blank. When I log into the app on my tablet, however, all Docker containers are visible (though not selectable). Also, all VMs are visible (though not selectable). How do I prevent Docker containers or VMs even being visible when they have not been selected in the plugin UI? I dont need Dockers to be accessible via the app and also want to control which VMs are visible. Quote Link to comment
jbrodriguez Posted January 30, 2019 Author Share Posted January 30, 2019 Hi, If visible is unchecked, the docker/vm should not appear. So you're accessing the app with a user other than root and you can see everything. What do you mean by not selectable? That there is no action available ? Can you send me screenshots of : - The plugin UI (where you marked not visible the docker/vms) - The docker/vm tabs of the app (as list preferrably) - The description of the user (it's in the User definition of Unraid itself) PM if you prefer. Quote Link to comment
darrenyorston Posted January 31, 2019 Share Posted January 31, 2019 (edited) Yes. I am logging in from the Android app using a user I created called "vmuser". I have to utilise the root password as the one for the actual "vmuser" does not find a server. By unselectable, I mean that the VM is listed with the start, edit, and undefine options greyed out. There is also some weirdness going on with checking the various boxes next to a VM in the plugin. If I check a box another previously checked box disappears and another one appears. It is like playing whack-a-mole. As an example I just removed all check marks. When I check "Visible" for a VM "Read" also is checked. When I then check "Exec" it stays checked for a few seconds then becomes unchecked. If I then go to another VM and check "Visible" it stays checked for a second or so then becomes unchecked. However, the "Exec" which I had previously checked, which went unchecked, now becomes checked. I am using Chrome v 71.0.3578.98. On the Android device, I would like to only have displayed a "Start" and "Stop" button for whatever VMs I want to be selected. I am intending to use your app as an interface to start whatever VM I want onto my monitors. So whilst I have a bunch of VMs I dont need to have shown on the app as starting them doesn't do anything because they don't have GPU pass-throughs. For example, when I am no longer using my desktop VM I want to shut it down and turn off the monitors. When I do want to use it again I can start whichever VM I want to utilise using the Android app. Which means only VMs with GPU passthroughs. The description changes every time I make alterations in the plugin as well. Edited January 31, 2019 by darrenyorston spelling Quote Link to comment
jbrodriguez Posted January 31, 2019 Author Share Posted January 31, 2019 Thanks a lot for the info darrenyorston. With regards to apps showing as unselectable, it was a design decision I made when I implemented the feature. The idea was that you could 'taunt' the non-root users and tell them ... look! look at all the apps you're missing out on, since you're not root 😁 😁 😁 ! Joking aside, I can't remember why I decided to show the docker/vm as non selectable, even if marked as not visible. I've fixed this behavior in my dev environment. If Visible is not checked, the app won't appear. I'm waiting for 6.7.0 stable to release a new version (which should be 'any time now' (tm) 😁). As for the whack-a-mole, that's mostly for consistency. I can see only three scenarios in which the plugin checks a box under the hood: - user checks VISIBLE -> plugin checks READ - user un-checks VISIBLE -> plugin un-checks all the rest - user un-checks READ -> plugin un-checks all the rest There's probably a couple automations I've missed, but it seems to work consistently for now. Quote Link to comment
jbrodriguez Posted February 8, 2019 Author Share Posted February 8, 2019 v2019-02-08 - 2.15.0 is out ! - Add support for 6.7.x This should also fix the issue mentioned by darrenyorston ! Quote Link to comment
bastl Posted February 10, 2019 Share Posted February 10, 2019 If I have a user setup in unraid and the same configured in the ControlR settings to be allowed to VIEW, READ and EXEC a specific VM or Docker that exact using should see that VM and or Docker in the android app, right? I am a bit confused right now. I had the user root conected before and all showed up. As soon as i use another user, none of the Docker or VMs are shown. Did i miss something? Currently on 6.7.0 RC3 and the newest Android app version 4.7.0 Quote Link to comment
jbrodriguez Posted February 10, 2019 Author Share Posted February 10, 2019 39 minutes ago, bastl said: As soon as i use another user, none of the Docker or VMs are shown Can you double check that in the ControlR settings the Visible checkbox is checked for that user/dockers/vms ? Quote Link to comment
bastl Posted February 10, 2019 Share Posted February 10, 2019 Visible is checked for that user and as you can see on the android app no docker or VMs are shown. @jbrodriguez Quote Link to comment
jbrodriguez Posted February 10, 2019 Author Share Posted February 10, 2019 I see. Could you follow the steps at https://github.com/jbrodriguez/controlr-support ? I'd like to replicate the issue with your user data. Quote Link to comment
bastl Posted February 11, 2019 Share Posted February 11, 2019 @jbrodriguez I've send you a pm with the support logs. Quote Link to comment
Saken Posted February 14, 2019 Share Posted February 14, 2019 for some reason if i try to set the refresh timer on this is just locks the app up Quote Link to comment
jbrodriguez Posted February 15, 2019 Author Share Posted February 15, 2019 Thanks for the report Saken ! I'll take a look at it. Quote Link to comment
jbrodriguez Posted February 15, 2019 Author Share Posted February 15, 2019 Regarding bastl issues, we identified a couple of issues with the plugin. I'm making some adjustments that should be ready soon, most likely will wait for 6.7.x stable to release a new plugin version. 1 Quote Link to comment
darrenyorston Posted February 20, 2019 Share Posted February 20, 2019 Finally got the opportunity to have a look at the update. I am having an issue where the web UI isnt accessible with SSL active. Do I need to edit something in the plugin to allow it to work with SSL? Quote Link to comment
jbrodriguez Posted February 20, 2019 Author Share Posted February 20, 2019 Shouldn't be the case. What error are you getting ? Quote Link to comment
jbrodriguez Posted February 20, 2019 Author Share Posted February 20, 2019 Try this in a server terminal ... ps aux | grep controlr # copy the controlr exec string, it will be something like /usr/local/emhttp/plugins/controlr ... killall controlr # paste the previous command /usr/local/emhttp/plugins/controlr ... This is to get an idea of what the plugin is doing, post back the command output. Quote Link to comment
darrenyorston Posted February 20, 2019 Share Posted February 20, 2019 (edited) 8 hours ago, jbrodriguez said: I: 2019/02/21 08:30:15 app.go:57: controlr v2.15.0-398-e62b436-v2019.02.08 starting ... I: 2019/02/21 08:30:15 app.go:65: No config file specified. Using app defaults ... I: 2019/02/21 08:30:15 core.go:73: starting service Core ... I: 2019/02/21 08:30:15 core.go:266: Created system sensor ... I: 2019/02/21 08:30:15 core.go:296: No ups detected ... I: 2019/02/21 08:30:15 server.go:94: Starting service Server ... I: 2019/02/21 08:30:15 server.go:113: Serving files from /usr/local/emhttp/plugins/controlr I: 2019/02/21 08:30:15 server.go:173: Server started listening http on :2378 I: 2019/02/21 08:30:15 server.go:185: Server started listening https on :2379 I: 2019/02/21 08:30:15 api.go:46: Starting service Api ... I: 2019/02/21 08:30:15 api.go:94: Api started listening https on :2382 I: 2019/02/21 08:30:15 app.go:85: Press Ctrl+C to stop ... ps aux | grep controlr # copy the controlr exec string, it will be something like /usr/local/emhttp/plugins/controlr ... killall controlr # paste the previous command /usr/local/emhttp/plugins/controlr ... This is to get an idea of what the plugin is doing, post back the command output. Edited February 20, 2019 by darrenyorston edit Quote Link to comment
jbrodriguez Posted February 20, 2019 Author Share Posted February 20, 2019 It looks fine, I'll do some testing tomorrow and ask you for some more info, depending on the tests Sent from my iPhone using Tapatalk Quote Link to comment
jbrodriguez Posted February 21, 2019 Author Share Posted February 21, 2019 If you change port 2378 to 2379, can you confirm that it works ? There's some issue with the plugin php/js logic to detect whether the server is running ssl or no. I'm looking into it. Also, is your ssl set to yes or auto ? Quote Link to comment
darrenyorston Posted February 21, 2019 Share Posted February 21, 2019 18 minutes ago, jbrodriguez said: If you change port 2378 to 2379, can you confirm that it works ? There's some issue with the plugin php/js logic to detect whether the server is running ssl or no. I'm looking into it. Also, is your ssl set to yes or auto ? Didnt work. I tried a few other ports as well. Same result. SSL is set to yes. Quote Link to comment
jbrodriguez Posted February 21, 2019 Author Share Posted February 21, 2019 1 hour ago, darrenyorston said: Didnt work It should have worked. It was a different error though, right ? Can you: - restart the plugin ( enable no, apply, enable yes, apply) - click on the link (will take you to the 2378 port) - change to 2379 manually - report the result Quote Link to comment
darrenyorston Posted February 22, 2019 Share Posted February 22, 2019 10 hours ago, jbrodriguez said: It should have worked. It was a different error though, right ? Can you: - restart the plugin ( enable no, apply, enable yes, apply) - click on the link (will take you to the 2378 port) - change to 2379 manually - report the result If I change the port to 2379 the server wont start. It shows stopped even though Enable Control Server is set to Yes. And yes I clicked Apply and Done. Its the same error code regardless of the port I try: SSL_ERROR_RX_RECORD_TOO_LONG Quote Link to comment
jbrodriguez Posted February 22, 2019 Author Share Posted February 22, 2019 Ok, repeat the steps above, only this time change to port 2379 in the browser address bar/url, not in the plugin settings (I wasn't clear on that).Let me know how it goes.Sent from my iPhone using Tapatalk 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.