cookiemole

Yes! I do. And these things seemed to have popped up after I manually invoked the mover.

I was thinking that too, but I'm getting all these files there too in the root directory of the cache: (I'll set a subset) About.page Addcontainer.page AddVM.page age_mover CA_notices.page Connect.page Dockersettings.page LICENSE Main.page Some of these seem like they could be related to plugins, some seem integral to unraid and I'm just not sure how they ended up there.

I noticed a strange thing after my cache filled up to 100% and all my dockers stopped working. This happened because my mover was misconfigured. Anyway, after I got the mover issue cleared up, all these directories showed up on my cache, in the root directory, and became registered as shares. agents api assets data domains event extra icons images include javascript nchan novnc post-hooks pre-hooks scripts sheets skins spice styles templates udev unraid-components unraid-components- Where did these files come from, where are they supposed to be, and how do I coax them to go back there? I also notice that my web server now stops working an hour or so after booting up the server, giving me "500 Internal Server Error", and I suspect that many of these files are related to the web server.

Sorry if this is a basic question. How do I set the FTP server to be read-only?

I am also having problems with Plex not automatically detecting directory changes when a new movie is added. (I'm running Plex through a docker). However, it does allow me to use Plex's periodic file scan without spinning up the disks. This happens much faster now because it just searches through the list of files in RAM. Could this plugin be intercepting and clearing the "something has changed" flag before Plex has a chance to see it?