Squid

Yes Transmission is available in the Apps "Store" Unraid boots from the flash drive, and then runs from RAM exclusively. No "boot" drive in the classic sense. Only the settings are stored on the flash drive.

It looks like you assigned the drive originally when it was on a built-in SATA port. Now you've moved it to your SAS controller, and it has changed the device identifier. Cross-flashing the controller to IT mode fixes this. (or move it back)

Post your diagnostics (Tools - Diagnostics) - add entire zip file to your next post

Or increase the threshold of what FCP considers to be an hack attempt

As long as the script has actually run, the log will always be present, if only saying that the script ran at such and such time.

https://forums.unraid.net/topic/57181-docker-faq/page/2/#comment-566088

Actually any copy operation, even initiated over the network will not traverse the network when using smb3 I just wanted to see why people wanted this

Without digging through PRs and change logs you might need to be on 6.9 to set no network and be able to override it in extra parameters

The obvious question here is why do you need it? What use case is there that say Windows Explorer cannot accomplish?

None. A name is a name is a name. I respond to Andrew, Squid, (and my wife's favourite: Asshole). Doesn't change who I am. The whole point is to change the repository from linuxserver/letsencrypt to linuxserver/swag. The only place this would cause an issue is if you're routing your traffic from other containers through "Letsencrypt" vs "Swag". Which you're probably not. (You tend to only do that with containers that connect to a VPN ie:Binhex, and not this one which simply forwards requests to a different port)

That module was added in quite a number of releases of the OS ago. Effectively what the message means from mcelog is that the stock mce module (ie: Intel) isn't support, and the system is switching to using the edac_mce_amd module instead.

this What do you mean by this?

If 6.8.3, probably this https://forums.unraid.net/bug-reports/stable-releases/683-docker-image-huge-amount-of-unnecessary-writes-on-cache-r733/ TLDR; update to 6.9

One thing to try is (assuming you have a cache drive) is for the /config path mappings (edit the templates, switch to advanced view), switch them from /mnt/user/appdata/.... to instead be /mnt/cache/appdata/...

Have you entered in the encryption key?

I would say that it looks to me like a CPU issue, not memory - hence the bios update.

Personally, I'd check for BIOS updates first. (Although MSI's website seems to be having some issues today)

Wow... You must be in the middle of nowhere. What do you have Satellite Internet?

That's entirely network / internet related. Once you're actually installing an app, then it winds up becoming a general support thing, and you should probably post there and attach a set of diagnostics. What country do you live in?

Next rev of Unraid supports clicking on a notification that takes you to where you need to be to handle it. As I get around to it, I'll be adding the appropriate links to all the possible notifications within Unraid, including FCP

Backup server active means that the primary server for downloads wasn't able to be reached (GitHub), so CA switched to it's backup server (Limetech Hosted via Amazon AWS). Main difference when this happens is that plugins probably will fail when downloading, and most of the icons for the Apps won't appear. But, since it's downloading off of the backup, posting CA's log won't give me any info as to your problem previously (since a router reboot solved that) where nothing would download at all and the incorrect error message was appearing in CA regarding that.

Try a different USB port. Ideally USB2 if you can

Does that work if you already using it for transcoding in another container? I would think that is the point of the container...

If you're still having problems @comet424 with the downloads, update CA then go to Apps, Settings, Enable Debugging, Apply. After going back to the Apps Tab (and the wrong error shows up in the banner), click "Debugging" at the bottom left of CA's menu and upload the file here. (Then disable debugging) While it won't solve the problem for you, it will tell me why the wrong error is appearing as I still am unable to replicate it - I always get the correct error on my systems no matter how much I try and screw up my internet connection from the server..

As an aside, there is a docker container already available in Apps that is this precise thing.