ljm42

Just a heads up, I formatted a disk as encrypted XFS in 6.4.0-rc8q and FCP wasn't happy with me: Error: Disk disk1 is formatted as luks:xfs Not complaining, it is a new rc after all

Thanks for posting this. I updated my docker-shell script: https://gist.github.com/ljm42/2b3bfd8ff886015bbce8 to work with your containers. First it tries: docker exec -it <name> bash and it that fails it tries: docker exec -it <name> sh

In that case you'd probably want to remove the if statement and the loop and modify the rsync command to copy directories. Google can probably help with the particular rsync syntax.

The script was designed to move files out of camera folders such as /DCIM/100CANON/, /DCIM/101CANON, /DCIM/102CANON, etc. If you don't need that you can remove the loop and simplify things. But hopefully it will get you started.

This is the script I use to move files from my camera's sdcard onto the array: https://gist.github.com/ljm42/02b54ce9cc36f992515b

Looks like it is fully working on my 6.4 VM with real certs. Nice! My only gripe is that it has its own directory for certs. I'd still prefer it if it just used unRAID's certs rather than generating its own that I have to replace. I tried symlinking them, but unfortunately the flash drive (FAT32) doesn't support that. Even so, congrats on integrating the plugin with SSL and 6.4

no, there's nothing else in the red banner other than "unable to connect to server" this is from my go script: /usr/local/sbin/emhttp -rp 80,443 & Here's the output of controlr while trying to login: I: 2017/06/24 14:42:11 app.go:57: controlr v2.0.5-201.f78ee85 starting ... I: 2017/06/24 14:42:11 app.go:65: No config file specified. Using app defaults ... I: 2017/06/24 14:42:11 app.go:74: Connections to emhttp via https:443 ... I: 2017/06/24 14:42:11 unraid.go:61: starting service Unraid ... I: 2017/06/24 14:42:11 server.go:70: Starting service Server ... I: 2017/06/24 14:42:11 server.go:90: Serving files from /usr/local/emhttp/plugins/controlr I: 2017/06/24 14:42:11 server.go:132: Server started listening https on :2379 I: 2017/06/24 14:42:11 proxy.go:48: Starting service Proxy ... I: 2017/06/24 14:42:11 proxy.go:91: Proxy started listening http on :2382 I: 2017/06/24 14:42:11 proxy.go:92: Proxy started listening https on :2383 I: 2017/06/24 14:42:11 app.go:104: Press Ctrl+C to stop ... ⇛ https server started on [::]:2383 ⇛ http server started on [::]:2382 ⇛ https server started on [::]:2379 {"time":"2017-06-24T14:42:18.890582303-07:00","id":"","remote_ip":"192.168.10.138","host":"towervm.mydomain.com:2379","method":"GET","uri":"/version","status":200, "latency":22936,"latency_human":"22.936µs","bytes_in":0,"bytes_out":31} {"time":"2017-06-24T14:42:27.100895073-07:00","id":"","remote_ip":"192.168.10.138","host":"towervm.mydomain.com:2379","method":"POST","uri":"/login","status":200, "latency":6719725,"latency_human":"6.719725ms","bytes_in":31,"bytes_out":175} W: 2017/06/24 14:42:27 unraid.go:82: Unable to get dockers: Get https://127.0.0.1/Docker: x509: cannot validate certificate for 127.0.0.1 because it doesn't contain any IP SANs Aha! Looks like a certificate error while trying to access https://127.0.0.1/Docker, it should access via FQDN instead

With 2.0.5 on 6.4.0-rc6 via https, when I login it says "welcome root!", which is a definite improvement. Unfortunately, below that is a red banner that says "Unable to connect to server" and there are no users or apps displayed. There are no mixed content errors, which is good, but I'm not sure how to help troubleshoot past this.

Odd, the link works fine on 6.4.0-rc5, but it is empty on 6.3.5 Other than that, the plugin seems to work fine on 6.3.5 (http only) but on 6.4.0-rc5 (https) I still get the mixed content error after logging in.

I tried to uninstall/reinstall and got some errors: plugin: installing: https://raw.githubusercontent.com/jbrodriguez/unraid/master/plugins/controlr.plg plugin: downloading https://raw.githubusercontent.com/jbrodriguez/unraid/master/plugins/controlr.plg plugin: downloading: https://raw.githubusercontent.com/jbrodriguez/unraid/master/plugins/controlr.plg ... done Warning: simplexml_load_file(): /tmp/plugins/controlr.plg:24: parser error : xmlParseEntityRef: no name in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Warning: simplexml_load_file(): If both http & https are enabled, it will start on https. in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Warning: simplexml_load_file(): /tmp/plugins/controlr.plg:24: parser error : xmlParseEntityRef: no name in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Warning: simplexml_load_file(): If both http & https are enabled, it will start on https. in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Warning: simplexml_load_file(): /tmp/plugins/controlr.plg:24: parser error : xmlParseEntityRef: no name in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Warning: simplexml_load_file(): If both http & https are enabled, it will start on https. in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 plugin: xml parse error

Is anyone able to get this update? My system says 2.0.1 is current. It isn't a networking issue as I was able to update Unassigned Devices.

Is https served on a different port? Currently http works fine for me on port 2378: http://192.168.10.188:2378/ but https on the same port doesn't work: https://192.168.10.188:2378/ Chrome replies "ERR_SSL_PROTOCOL_ERROR" and Firefox says "SSL_ERROR_RX_RECORD_TOO_LONG" I get the same response on my 6.3.5 bare metal unraid server as well as my 6.4.0-rc3 VM. Also, the "Open Web UI ( v2.0.0 )" link just opens a blank tab. It looks like the url is set to "http://:2378"

The major problems that the plugin solved have been fixed since 6.2b22: LT has been keeping the drivedb.h file pretty current since then. If you want to check for updates on a regular basis anyway, the User Scripts plugin is probably the way to go at this point.

The Tips and Tweaks plugin can permanently disable both ftp and telnet

Hi @Squid, how would you feel about adding application-specific checks to FCP? CrashPlan is a set-it-and-forget-it type of program, once things are working people typically ignore it and can go months with no idea that there are problems. FCP can help by alerting users to common error conditions. I'm thinking the logic would be something like this: If a CrashPlan docker is installed, find the /config mapping. i.e. /mnt/cache/appdata/CrashPlan Scan /mnt/cache/appdata/CrashPlan/log/service.log.0 for "inotify.InotifyManager] Unable to add watch for path". If found, show an error saying "CrashPlan is returning an error when attempting to watch a file. Use the Tips and Tweaks plugin to increase the Max User Watches." Example log file Scan /mnt/cache/appdata/CrashPlan/log/service.log.0 for "OutOfMemoryError occurred...RESTARTING!". If found, show an error saying "You need to increase the amount of memory available to CrashPlan. See instructions in the support thread for your docker." (I can PM a file with this if it helps) For added complexity... the service.log.0 appears to rotate based on size, not on restarts. So if an error is acknowledged on line 1000, ideally that same line wouldn't trigger another error on next run.

This page specifically says you need PMS 1.7.2, which is standard plexpass: https://support.plex.tv/hc/en-us/articles/115007689648 So it is a beta *feature*, but it is available in a plexpass *release*. Kind of confusing

You need plexpass version 1.7.2 to watch live TV, and specific clients (Android TV and IOS). Most clients (Android, Apple TV, Roku, web) do not work with live TV yet: https://support.plex.tv/hc/en-us/articles/115007689648 You also need a supported tuner and antenna: https://support.plex.tv/hc/en-us/articles/225877427-Supported-DVR-Devices-and-Antennas For unRAID, the HDHomeRun is probably the best as it is network-based and you don't need to worry about drivers. If you have purchased a PlexPass and are using the LSIO docker with the VERSION environment variable set to "latest", all you need to do is restart the docker to get the latest version.

You have to know the full version string. For instance if you look here: https://www.plex.tv/downloads/ the full version string for the current public release is 1.5.6.3790-4613ce077

Essentially it's down to support It is also the only option that lets you install *any* version of Plex (even beta/forum-only versions) that your Plex account has access to. Finally got around to updating my "Choosing a Plex Docker" post:

That is great news!

For me anyway, I don't know how you are measuring iowait or how you determined Crashplan was the problem. But... the service.log.0 you uploaded contains many lines that look like this: [04.12.17 10:46:41.721 WARN Thread-127 ode42.jna.inotify.InotifyManager] Unable to add watch for path /mnt/user/... according to the link above, that means need to increase your inotify watch value. Whether it will fix the problem you are trying to solve, I don't know but it will fix *a* problem. I suggested the Fix Common Problems plugin because it reduces a bunch of complex troubleshooting steps down to the click of a button. I can't guarantee it will solve this problem, but it will almost certainly help. If you are still having problems after that you might need to contact Crashplan. If you find the solution, please let us know.

The best way to increase the inotify max_user_watches value on unRAID is by using the Tips and Tweaks plugin. As a start, you can double the default number. I'd also recommend installing the Fix Common Problems plugin, as it could have alerted you to this inotify watch problem. There may be other issues it can help with as well.

It's possible you have the old ipmitool version of the plugin and need to uninstall/reinstall per the first post in the thread? Sent from my ONEPLUS A3000 using Tapatalk

Hi dlandon, Just thought I'd give you a rundown of my experience with this plugin today 1. I started reading the thread from the beginning and discovered I was running a really old version due to this: oops I uninstall/reinstalled and am now on the 2017.03.17 version. 2. I think it might help people get started if there was some sort of message telling them they have to start the plugin before they will see any results. Took me a few minutes to figure that out, although perhaps that is because I was used to the old version. I found it in the help afterwards. 3. Then I had a couple of false starts because it kept stopping right after I started it, with no explanation. Noticed this in the syslog: Mar 24 16:01:59 Tower inotifywait[30412]: Failed to watch /mnt/disk1; upper limit on inotify watches reached! Mar 24 16:01:59 Tower inotifywait[30412]: Please increase the amount of inotify watches allowed per user via `/proc/sys/fs/inotify/max_user_watches'. So I increased the watches using the Tips and Tricks plugin. It would be nice if the plugin could detect this and explain why it can't start. 4. There were no results at first but after a few minutes the refresh button started showing results. Thanks for this, I think it will be quite helpful.

Thanks! works great