Squid

The docker run command will tell you what's wrong. Post it back after following the linked directions

I've finished quick tests with CA and Big Sur w/ Safari 16.2 OK Catalina w/Safari 13.1.3 OK Catalina w/Safari 15.6.1 OK 8th Gen iPad OS 14.7.1 And there doesn't appear to be any issues per se. Only suggestion at this point is does it work without any extensions? Clear the cookies out? Reboot the server?

Settings, Community Applications. Enable Debugging Go back to Apps. Wait at least 120 seconds. Go back to Settings, Community Applications. Download debug log Post back the zip file here

An update restoring that was issued ~ 1 hour before your post

especially from mobile devices

docker.folder.plg - 2021.08.20 (Up to date) (Incompatible) NerdPack.plg - 2021.08.11 (Up to date) (Incompatible) Uninstall and reinstall the compatible forks available within Apps The implication however with your problem is that you may need to delete and recreate the docker.img file https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file

Try from a command prompt rm -rf /tmp/community.applications and then reload the Apps page If it still fails, Apps, Settings -> Enable Debugging. Get it to fail and then click "Debugging" and upload the resulting file here

are you having any issues? or just the errors being logged?

Dec 17 08:30:55 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 0 csum 0xdcd48dc8 expected csum 0xf80c5fc3 mirror 1 Run a memtest for a couple of passes But, your probable solution is to recreate the docker image

Start with running a memtest for at least a couple of complete passes

But that's not going to be the problem anyways. You should reboot and then try it again and if it still fails then post a clean set of diagnostics

You do have a bit to look at here Dec 11 04:57:28 Raza root: Fix Common Problems: Warning: Deprecated plugin ca.backup2.plg Dec 11 04:57:30 Raza root: Fix Common Problems: Error: Blacklisted plugin speedtest.plg Dec 11 04:57:32 Raza root: Fix Common Problems: Error: Unable to write to disk14 Dec 11 04:57:32 Raza root: Fix Common Problems: Error: Unable to write to disk15 Dec 11 04:57:32 Raza root: Fix Common Problems: Error: Unable to write to disk19 Dec 11 04:57:32 Raza root: Fix Common Problems: Error: Unable to write to tv_pool ** Ignored The disks are full, but I'm wondering if it's not due to misconfiguration as it would be rare (not impossible) to have 20K free space on any random drive

You won't find anything in them as logs are not persistent unless you explicitly enable the syslog server (mirror to flash), and that wouldn't explain anyways why the system wouldn't power back up (BIOS / power issue), but only why it powered off in the first place. Shutdown was clean however, so no unclean shutdown was done.

Try changing the size of the image to 20G. Possibly overhead etc involved in updating on the image

You should post your diagnostics

Keys get blacklisted when you transfer the registration (due to a failing flash drive). Transferring blacklists the original drive in favour of the replacement. Have you ever transferred the registration to a new device? If so, why did you not use the new flash drive but continued to use the original? You should contact Limetech support and show them all of the GUIDs (Tools - Registration) which you are currently using on all your systems so that it can be sorted all out. Their support staff works 7 days a week and I've heard that the average response time is an hour or two at most.

The USB creator program is supposed to work with most flash drives > 32G The Manual method of creating flash drives does not work with > 32G, without jumping through some major hoops (and yes its a FAT32 issue) Life is simpler though just staying within the FS limitations of 32G devices. (and an 8G is more than sufficient)

Some more details might be in order as to what you are referring to.

It works fine for me, so not something endemic To clarify, are you hitting "APPLY" or is there an actual "SAVE" button present?

You're also running multiple VMs As we all know, something like Windows can take quite a while to shut itself down. Even an open dialog window will prevent the Windows from shutting off, which will lead to the OS having to forcibly kill off the tasks and then having an unclean shutdown flagged, regardless of whatever times you set. Always set in VM Settings for the powerdown action to be hibernate and install the QEMU guest tools in the VM. Now when a poweroff gets issued, the VM will hibernate in a second or two instead of having to actually perform a shutdown.

Shouldn't have to pin the containers. Only reason OTOH a container would wind up running on an isolated core is if you've actually pinned the container to that isolated core.

Needs to be noted here before people go out and buy card readers is that those two readers were extremely rare in the fact that they did return unique GUIDs that were suitable for use. 99.99% of card readers are not suitable and do not return proper GUIDs and cannot be used. FWIW, my flash drives (all 10+ years old) have all outlasted all other component in the servers.

If the system generates diagnostics during an unclean shutdown (this happens during a normal request for a shutdown but the system is unable to cleanly unmount the drives), the diagnostics that are generated are automatically anonymized

Every file system will remount a device as read-only when corruption gets detected to prevent further corruption from occurring. Unraid when it reboots automatically does a correcting file system check on the flash which presumably fixed the issue.

The one thing I'd say is that you're getting a ton of attempted connects from pretty much every country in the world. If there's no real valid reason for you to open up the server to the world (and very rarely is there) it shouldn't be. Or at the very least invest in a real firewall for your network. For the other problem, I'd suggest to recreate the docker folder Other than that, docker.folder.plg - 2021.08.20 (Up to date) (Incompatible) - There is a compatible version within Apps usb_manager_usbip_addon.plg - 2022.07.21 (Unknown to Community Applications) - Probably shouldn't have this installed.