Squid

Extra parameters in advanced view

Apps - Previous Apps check off what you want. Everything should be back the way you left it.

Did you manually edit / tweak the original XML at all? Unraid does not preserve any custom edits to the XML

Are they just missing or something like "Docker failed to start" appearing?

Then you reference within the app the host IP address and the port # (eg: from Radarr)

Are the containers all using bridge networking, or on a separate docker network? As you already noticed, using 172.* is definitely not how you want to do things.

AFAIK, a powerdown will stop mover. However, it'll probably only manage to cleanly stop it after the current transfer is finished. If (with everything else going on during a shutdown), mover takes longer than the shutdown timeout, then the system will forcibly kill the process. This will result in a partial file being on the array (in the case of useCache:yes), or a partial file being on the cache pool (useCache:prefer). Because of how Unraid handles multiple identically named files on the array / cache, in the latter case it will appear that the file is corrupted / incomplete. (even though the source file isn't)

How are you moving them?

How are you doing the passthrough? Editing syslinux via one of the legacy methods or using Tools - System Devices? You should be using the latter to prevent this.

https://askubuntu.com/questions/493198/what-is-a-fuse-hidden-file-and-why-do-they-exist

Very long term goal, and *may* be implemented if / when the size of the application feed becomes untenable and requires a shift over to an online SQL system. But, there's also privacy concerns related to that also.

Post your diagnostics

Delete /config/network.cfg on the flash drive. That'll set the server's network back to defaults (ie: DHCP). If you still have problems, then edit /config/disk.cfg and change startArray="yes" to instead be startArray="no"

What about MakeMKV-GUI?

You would need to post your diagnostics (Tools - Diagnostics)

I had something somewhat similar with my TP-Link Deco system. Random network dropouts of the Deco's. While it may or may not be your problem, my solution was off of my main switch I ran another cheap switch which I dedicated specifically to the deco's and had everything else plugged into the main one. Worked for me because I only use the Deco's as AP's. (There's a specific protocol used by mesh networks, which many switches block)

Post the diagnostics

It's probably a bit much to ask for an update for a plugin to fix any issues on a very limited availability pre-release version of the OS.

The memory is currently running at 2666 Speed: 2666 MT/s Manufacturer: Samsung Serial Number: 03CF9BAE Asset Tag: Not Specified Part Number: M391A4G43MB1-CTD Rank: 2 Configured Memory Speed: 2666 MT/s

If the appdata share is stored on a different server than where the container is running from, then yes that is a weird setup (although nothing wrong with it per se)

Check the ethernet cabling or try another port on the switch.

Port 3000 is already in use by another app. Change the host port being used on the template to something else

Is it causing you any issues? I ran a server with an i9-10900 no problems with VM passthrough etc. (No longer do though)

Streams are the active files open to the share. Since you're showing items in there for appdata, I'd surmise that you're also using NFS (I'm not, so mine are always 0 for appdata since generally your containers won't access anything in appdata via SMB)

Group 15 is being used by Unraid. Group 23 is the controller that shouldn't be used at the moment.