-
austinite started following (SOLVED) Out Of Memory Errors-Unresponsive System , External Access Guidelines , Is UnRaid really unsecure? and 7 others
-
[Plugin] Network Stats
Same issue. Details: Plugins | Network Stats Network Stats Settings Interfaces to capture : (ALL) eth0 eth1 (ALL) VNSTAT Daemon: Stopped start (clicking start does nothing) Stats | Network Stats: vnstat service must berunning started to view network stats.
-
[Plug-In] Community Applications
Thanks @Squid and @trurl. Manually deleting the advanced buttons.plg from the cache drive and rebooted. It worked. Appreciate it. Edit: Noticed these messages every second in the log, though: May 6 23:02:51 unRAIDTower nginx: 2018/05/06 23:02:51 [error] 9375#9375: *28082 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.92, server: , request: "POST /plugins/advanced.buttons/AdvancedButtons.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.99", referrer: "http://192.168.1.82/Dashboard"
-
[Plug-In] Community Applications
Hi. Running unRAID 6.5.1 and Community Applications fails to upgrade. It shows I'm on version 2018.04.22 and that 2018.05.05 is available. Tried it 4x. System logs only shows the attempt to upgrade (in the GUI, it says it fails and then that is was successful but doesn't actually update) : May 5 12:00:36 Tower ool www[23399]: /usr/local/emhttp/plugins/advanced.buttons/script/plugin 'update' 'communityapplications:.plg' &>/dev/null & Anyone else having this issue or have any recommendations? Thanks.
-
[Support] binhex - Radarr
Just started getting an authentication prompt after upgrading to Version 0.2.0.995 a few minutes ago. Found a discussion on Reddit and someone there mentioned "Web host issues, according to Discord channel" so hopefully it's just temporary. Hitting cancel seems to work fine for now.
-
How much RAM do you have installed in your unRAID server?
64GB DDR4 ECC
-
[CONTAINER] CrashPlan & CrashPlan-Desktop
I'm getting the exact same thing on multiple attempts at initial/clean builds (black screen when attempting to connect via VNC). Seems the current docker has a defect of some kind for new installs.