Cilusse

Server name is 'und.ukb'. I actually changed that very recently, do you think the dot confuses the plugin as the name and certificate apparently don't match ? ... Just reverted to 'und' as name and the issue is fixed! So yes, the dot in the server name confuses the plugin somehow. Thank you for helping me resolve this!

I tried to re-create the Unraid cert as you recommended and it didn't solve the problem. root@und:/boot/config/ssl/certs# ls controlr_cert.pem controlr_key.pem und_unraid_bundle.pem All of those certificate were re-created just now Console output is still the same.

Hi, Thank you for your answer. Here's the console output when run from command line: I: 2020/07/21 20:07:58 app.go:58: controlr v2020.05.09|2.19.0 starting ... I: 2020/07/21 20:07:58 app.go:66: No config file specified. Using app defaults ... I: 2020/07/21 20:07:58 app.go:171: host(https://10.0.0.2:8443) I: 2020/07/21 20:07:58 core.go:81: starting service Core ... I: 2020/07/21 20:07:58 core.go:304: Created system sensor ... I: 2020/07/21 20:07:58 core.go:334: No ups detected ... I: 2020/07/21 20:07:58 server.go:92: Starting service Server ... I: 2020/07/21 20:07:58 server.go:111: Serving files from /usr/local/emhttp/plugins/controlr I: 2020/07/21 20:07:58 server.go:168: Server started listening http on :2378 I: 2020/07/21 20:07:58 server.go:180: Server started listening https on :2379 I: 2020/07/21 20:07:58 api.go:46: Starting service Api ... I: 2020/07/21 20:07:58 api.go:93: Api started listening https on :2382 I: 2020/07/21 20:07:58 app.go:84: Press Ctrl+C to stop ... F: 2020/07/21 20:07:58 server.go:176: Unable to start https server: read /boot/config/ssl/certs: is a directory ⇨ http server started on [::]:2378 ⇨ https server started on [::]:2382 It looks like it doesn't like the certs location but I don't really understand why. The folder contains (along with the Unraid default certificate): root@und:/boot/config/ssl/certs# ls controlr_cert.pem controlr_key.pem Hope this helps! All the best,

Hi, I am having an issue with the plugin. ControlR can connect to my server just fine, but can't show logs and execute actions that necessitate the plugin. Plugin is installed, and when switched to ON, I can see the status changing to Running and then immediately reverting back to Stopped. I tried to re-install the plugin from CA, delete the config files, but it still won't start the service. The console outputs when starting the service. Jul 20 19:30:59 und ool www[6396]: /usr/local/emhttp/plugins/controlr/scripts/start Jul 20 19:30:59 und sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/bash -c /usr/local/emhttp/plugins/controlr/controlr -port 2378 -certdir '/boot/config/ssl/certs' The config file is pretty standard: SERVICE="enable" PORT="2378" CERTDIR="/boot/config/ssl/certs" UPS="disable" I also checked that no other web server is running on 2378 and it is definitely free to use. It used to work just fine a couple weeks ago, and I don't remember changing anything that can affect the plugin, other than normal and regular updates. Is there something wrong with my setup ? Is it a known issue ? Many thanks everyone!