Squid

Every plugin, no exceptions, are checked for security issues. This doesn't mean that there isn't going to be security flaws caused by libraries utilized, but you do know that any random plugin is not going to go ahead and outright delete your media etc. Every single plugin available via Apps gets installed on my production server, with no exceptions, and a code audit is done on what is actually present instead of what may be showing on GitHub. Every single update to every plugin I am notified about (within 2 hours), and with plugins which are not maintained by a contractor of Limetech is then code audited again. Every update. And with only a few exceptions, this happens on an actual production server not on a test server. If something ever fails the checks, then everything else gets dropped (including the 9-5 job) to handle the issue. Whether that means simply getting the application out of apps temporarily and asking the maintainer / author "WTF? You can't do this", or notifying everyone with it installed via FCP about any issue, or preventing the Auto Update plugin from installing any update to the plugin, or even taken more drastic measures, provisions are in place to protect the user.. Closed source applications, whether they are plugins or containers, may be frowned upon, but are not necessarily disallowed. With plugins, the standard for open-source vs closed-source is more strict, but it is not 100% a requirement that only open source be present.

Any path in the template that has either a share (/mnt/user/shareName or the direct disk equivalent /mnt/cache/shareName) which has a container path on any template of /config is automatically excluded as it is an appdata storage location by convention. Also, the default appdata location (Settings - Docker) is also automatically excluded and the script will never allow you to run on it.

Does this file exist on the flash drive: /config/share.cfg ? If it does then it's empty which is technically corrupted. Not sure how it would get into that state, but if you're not having any issues then delete the file

Error 8 usually means the URL isn't correct. On older keys if something changed (name, email address etc), then the original URL might have changed. Either way, you need to contact support and also show them a copy & paste (no screenshots) of what is appearing within Tools - Registration and they'll get it all worked out for you.

There's fan settings. You can run it normal, silent or full speed. You can't however use temperature controls in the BIOS to increase / decrease the speed.

Are you able to install any new containers? It taking forever (and timing out) would imply that your system is unable to hit dockerHub / ghcr to check for updates.

The logging of the startup has nothing to do with the plugin and happen whenever you stop / start a container. IE: no

Memtest is an option on the boot menu you select memory speed you change in your bios

Don't know much about NFS. SMB should mount however

shareExport="-" Checking your Media share, it's not exported. You need to export it on the SMB settings for it to be available on the network

Is the array started? Post your diagnostics

Look on the calendar?

Have you tried not running unmanic? OTOH it would be a memory pig. Alternatively, limit the memory available to the various containers via ExtraParameters --memory=4G

6.10. 6.12.8+ was a revamp of the settings for TimeMachine. Prior to 6.12.8 you could get TM to fail on Unraid no problem, and it would intermittently fail for apparently no reason at all. 6.12.8+ I was completely unable to manage to get TM to ever fail, no matter what I did

First thing I'd do is run memtest from the boot menu for at least a couple of passes. You've got a ton of general protection faults which a lot of times is caused by bad memory. You should also be running the memory at its actual speed of 2133 (SPD) instead of the overclocked XMP speed of 3200. All overclocks introduce instability.

Where's that file from? It's not corrupted, but FCP considers any .cfg file in /config to be a valid ini file, which it technically isn't because of the quotes and brackets in the comments

Because I never expected for the OS to reach 6.12.10 so it was marked as the maximum version allowed of 6.12.9 Fixed. Should reappear in Apps shortly

Fixed

I have nothing to do with this plugin anymore. You want @hugenbdd

Agree with what I've been doing for the last 5 years or not. I'm good with everyone's opinion and can understand both sides of the argument. But, know that like everything else in CA, these things get tested to death to ensure that they are completely harmless, and functionality isn't impeded, and watch like a hawk every posting to ensure that nothing has gone awry. CA is a passion project. Last year's tribute to the bat if you chose to continue with the homage didn't affect anything (unless you were unable to do a handstand). This year, even if you didn't "revert" to the author dictated images upon installations the author's images would appear in the docker tab, and in all cases it's a simple one click to restore that's clearly communicated. My personal opinion regarding this stuff is that it shows that I actually do care about CA, it's security, and this community. I'm not the type of person (probably few are) who could survive long in a coding factory fashioned after a sweatshop. (Pretty sure that no one else in a space invader one interview inadvertently dropped a dick joke that made it through the sensors) But, everyone did miss the biggest joke of all. While every app had a randomly selected photo (changed every 2 hours), right on the home page (Spotlight section), the "unbalanced" app had a specific picture pinned to it for the duration of the day. While Tom et al did give a go ahead for this, any and all blame / anger / misgivings should get thrown my way. I am glad however that my original idea / planning for this year I did ultimately decide against. It was going to leverage a coding change which is being put into place for a different legitimate reason, but after looking at how the end result turned out I figured it would completely mess everyone up. Either way, as far as I'm concerned, debate about yesterday's event should now be over. What's done is done and let's all get back to business.

Can you enable the syslog server (mirror to flash) and after the next crash, reply back with the syslog that'll be stored in /logs on the flash drive

FWIW, I've been gradually simplifying things on the servers in the house to handle that scenario. To make them easier to run / maintain with little if any management from the better half. But, I also worry that upon my passing no one would be able to change the input on the TV either.

Delete that file (Larry) on the flash drive

rm /boot/config/plugins/community.applications/larry lol

Also, does fix common problems say anything?