no1home

Thanks guys. With this info I used the ltConfig plugin to change peer_fingerprint to -DE204D- and the tracker was happy again with the new docker version. -DE203s- works also. Btw, the error I was receiving from my tracker was "Error: Anonymous client". Couldn't figure it out without your help.

Switched to Theme Engine and all is well. Thanks.

Feb 3 05:44:38 Tower nginx: 2020/02/03 05:44:38 [error] 6468#6468: *2831 open() "/usr/local/emhttp/<br /><b>Warning</b>: filemtime(): stat failed for /usr/local/emhttp/plugins/unassigned.devices/assets/style-dark.css in <b>/usr/local/emhttp/plugins/dynamix/include/Helpers.php</b> on line <b>248</b><br />/plugins/unassigned.devices/assets/style-dark.css" failed (2: No such file or directory), client: 192.168.1.170, server: , request: "GET /%3Cbr%20/%3E%3Cb%3EWarning%3C/b%3E:%20%20filemtime():%20stat%20failed%20for%20/usr/local/emhttp/plugins/unassigned.devices/assets/style-dark.css%20in%20%3Cb%3E/usr/local/emhttp/plugins/dynamix/include/Helpers.php%3C/b%3E%20on%20line%20%3Cb%3E248%3C/b%3E%3Cbr%20/%3E/plugins/unassigned.devices/assets/style-dark.css?v= HTTP/1.1", host: "tower", referrer: "http://tower/Main" I'm getting this error in my log with the Dark Theme plugin installed whenever I click on the Main tab of the unRAID gui. If I remove the plugin, the error goes away.

I have this error as well but it seems to be pretty harmless. See the issue posted here Issue#151. Perhaps there is another error in your log causing deluge to crash for you.

My favorite thing about unraid is that it still runs great on my very modest hardware. Can't think of any new features I need right now.

Try "Check for Updates" on the Docker page.

Seeing this error in the log since upgrading to the deluge 2.0 version: 2019-06-19 00:33:39,400 DEBG 'watchdog-script' stderr output: /home/nobody/deluge.sh: /home/nobody/config_deluge.py: /usr/bin/python2: bad interpreter: No such file or directory I changed the shebang on line 1 to "#!/usr/bin/python3" and modified the print statements to be python3 compatible and all is working.

Just upgraded from 6.3.5 to 6.4.0, process went very smoothly. The only thing I had to do was upgrade my CA Backup plugin to v2 and re-enter settings. One thing I noticed in the Docker page, "Version" shows as "not available" for all of my dockers. Loving the speed of the new interface. Thanks for all your hard work on this release.

I had this problem as well (Intel Q6600). The kernel showed acpi_cpufreq module was loaded but cpufreq-info showed "no or unknown cpufreq driver is active on this CPU". I discovered that I had to enable Intel SpeedStep in the BIOS CPU Management settings. After booting the driver was functioning.