jbrodriguez

I got a similar error today and it was due to permission issues: trying to write to a folder for which the user didn't have permissions.

Glad to know you got it working ! You can set the port from the Settings page, so you don't have to run the plugin manually each time. Not sure what the issue is with the unknown port error. I looked it up but nothing really came up.

This is the issue. It doesn't say that the port is in use, but that might be an option. Try lsof -i :6237 to find out if there's any process currently using the port. Other than that, is it possible that you're running ONLY ipv6 (no ipv4) ?

Hi, checked the logs, there are several successful gathers, and towards the end of the log, some attempts that get flagged due to flag:(rsync: failed to set times on "/mnt/disk11/Media2": Operation not permitted (1)) Not sure what's the issue with that share (Media2), but for some reason rsync can't set times on it 🤷🏼‍♂️

Check the log ... /boot/logs/unbalance.log for additional information about the error (send it over if you want, I can take a look, pm if you so prefer)

I haven't thought about UD support in the app. It should probably just work, but I have just not looked into it [emoji2369] Sent from my iPhone using Tapatalk

Sorry, it's Settings > Open Source Libraries. By the way, the app has an issue with the OnePlus android devices, text is clipped, because they use a proprietary font. If you change the system font to Robot, you'll see the text no longer clips (as in the Settin... above)

Ok, try this then. Use the same settings as I mentioned in the previous post, then - Go to Settings > Credits - 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 (pm if you prefer)

In the app, try this Ip/Hostame: <ip address> Port: 443 username: root password: <password> secure: on Does it not work ?

Boyturtle, There are some troubleshooting steps in the FAQ (https://www.apertoire.com/faq/controlr/), section "I can’t connect to my server". Try that and let me know if it still doesn't work.

Hi, Try Ip/Hostame: <ip address> Port: 443 username: root password: <password> secure: on Let me know how it goes.

I'm working on adding basic support (limited display-only) for unassigned devices into the app. I could really use some sample data to better understand different scenarios. If you're using the app, unassigned devices and would like to help, please follow the instructions at https://github.com/jbrodriguez/controlr-support IMPORTANT: Make sure you're running Unassigned Devices v2019.06.10 or above.

Thanks for the feedback. I'll take it under consideration.

I don't have too much more to say, to be honest. For remote access, the app supports an OpenVPN(/WireGuard) setup, not a reverse proxy such as nginx. The port to use is the Unraid webGUI port, not the plugin's. This is stated in the FAQ (https://www.apertoire.com/faq/controlr/) I'm currently unable to provide support for any other scenarios (even if they may or may not somewhat work).

It's used to obtain the user's access to dockers and vms in the app, defined via this plugin (as shown in the first post).

I'm trying to offer an insight into why the app works the way it does. I'm certainly not trying to troll you.

mikeydk, Try this ... In the Unraid Users page, set up a new user (mikey as in your example) and set a password for this user, a password that's different from root's password. Then, via any browser, access Unraid's GUI and try to login with this username/password (mikey/<password>). Does it work for you ?

I understand what you're saying, but it's currently not possible. Authentication in Unraid currently only happens via 'root' user. That's out of my hands. It's unfortunate the app doesn't work for your use case.

But the app needs to log into Unraid. That's why I mentioned that your scenario is not currently supported.

Ok, I reviewed the code. It's as I mentioned before: as per the current Unraid architecture, only root can be authenticated. There's currently no workaround for that.

Ok, bear with me, I'm trying to understand the issue you're reporting. You can't edit the username field? That is, you can't remove the 'root' text and replace it with any other text (other username) ? Or is the field not-editable ? Does it happen only for the username field ? Are you able to edit other fields ?

Also, as mentioned by itimpi, the officially sanctioned way to use ControlR remotely is via a vpn (OpenVPN, WireGuard when it makes it to the kernel/Unraid). I'm pretty sure it will sort of work remotely the way you describe it, but it's not a use case I support.

I thought you were referring to the web interface of the plugin, but you're actually referring to the app itself. It shows root just as a placeholder (currently people logs in with root, in the more general case). You can change the username, but you still need to use root's password, due to how Unraid is currently set up. There's a longer explanation in the FAQ. Or are you saying that you can't replace the 'root' username with any other username?

That's right, only root can be authenticated.

The plugin looks at the Unraid settings to connect via either SSL or not. You have SSL set to 'yes' or 'auto'. Could you try setting Unraid SSL to no, then stop/start the plugin ? It should work this way.