Seraphys

Same

Hello, I am one of the devs of the Profilarr project. We are vying to start v2 soon so I was wondering if you would be willing to deprecate your template so we can make sure the experience is as fluid as possible for the upcoming versions? Thanks

It's kind of disappointing LT ignoring this plugin if it's going to take them over

Hmmm i only ask because ive seen posts by squid saying image is antiquated and shouldn't be used lol. I attached an image of the error i had captured before restarting. As for the docker restarts i have scripts for restarting stuff like the arrs cause they get borky after running a long time.

The diag was unfortunately gotten after I had restarted. The syslog I attached in my first post had the errors. Isn't docker directory and overlay2 the current recommendation?

Attachedseraphys-diagnostics-20251103-0750.zip

So while jdupes was running after using automover plugin, my docker was suddenly corrupted. I don't know if it had anything to do with each other just that the corruption preceded jdupes starting. I am on unraid 7.2 diagnostics attached. syslog-192.168.1.100.log

I agree docker seems very sluggish comparatively to 6. Nothing wrong in the logs it just seems like it's unrefined

The docker page seems quite slow to load comparatively to unraid 6.12. Is this because of the responsive ui?

this is also happening to me on 6.12.5

Just something I think is worthy to note, at some point I think you guys need to consider making something like the mover tuning settings native to unraid rather then letting people rely on the plugin. The mover is such an integral part of unraid and forcing users to rely on 3rd party and sometimes unreliable plug-ins isn't a particularly great user experience.

That would be nice. Tbh mover tuning at this point has become so big and bloated it gets very borky after a while.

Possible to add age related moving and to disable size thresholds?

Blank screen after updating to 2025.09.23

Right now when i disable mover on a schedule it disables mover completely. When i press mover button nothing happens.

Please and Thank You!

The previous plugin had the ability to disable the scheduler but still keep all filters for manual move button operation. Is this something youd be able to do?

Updated to the latest version and the docker no longer opens up the link for access

So is eth0 macvlan and all created custom docker networks are macvtap or are both macvtap. I only ask this because while eth0 uses static ip addresses the newly created docker networks seem to all use the host ip like when bridge is enabled.

So I'm currently using macvlan with bridging turn off on eth0. When I create a custom docker network it is being listed as a bridge network even though I have bridging turned off. Can someone explain what is going on and what the newly created custom docker network is?

Does host access to custom networks need to be enabled now that bridging is working? It's normally off for ipvlan

Does this mean that in theory all call trace crashes related to macvlan should be resolved in this release?

i have the same issues, this plugin is bugged in many ways now in the newer unraid versions. I would stay away until its updated for anything beyond 6.12.8

Been using this plugin a while. Getting this recurring pipe error in logs ever since update. Apr 7 21:39:52 Seraphys usbhid-ups[3556]: nut_libusb_get_string: Pipe error

Yes I noticed it on 6.12.9 initially it was fine on 6.12.8. Thanks for confirming and hopefully it gets fixed soon!