Squid

Try setting typical idle current (or similar wording) in the BIOS to be "typical". If no option, then ensure that c states is also disabled You should also try running your memory at the SPD speed (probably 2133) instead of its xmp (overclocked) profile of 3200

I think you win the prize for the most plugins I've ever seen installed lol. But that wouldn't / shouldn't cause an issue Does the system work properly if you access locally without the reverse proxy? Have you allowed web sockets through the proxy? Also maybe related is Apr 26 12:47:41 SRV-NAS-01 root: PhotoPrism-Helper: Could not download icon https://raw.githubusercontent.com/aerilym/docker-templates/master/aerilym/images/photoprism-helper.png Apr 26 12:47:56 SRV-NAS-01 root: Firefly-III-Importer: Could not download icon https://raw.githubusercontent.com/SmartPhoneLover/unraid-docker-templates/main/templates/icons/firefly-iii-data-importer.png Apr 26 12:48:11 SRV-NAS-01 root: PhotoPrism-Helper: Could not download icon https://raw.githubusercontent.com/aerilym/docker-templates/master/aerilym/images/photoprism-helper.png Those urls definitely all resolve for the icon images, but something is stopping them from downloading. Your network configuration on a quick glance appears to be correct to me, so router issues? VPN issues?

So far as I know its always been like that. A session cookie saved. Either way, it would be by design

Today's update (among other items) has all of the Safari fixes. Please let me know if it doesn't fix things up (screenshots, what you were doing etc)

Try setting static DNS addresses in Settings - Network Settings. Set up #1 and #2 and 208.67.222.222 and 208.67.220.220 (openDNS)

Doesn't matter. You have to. No way around it. Doubtful

Try doing a force update in Advanced view and see if it clears things up after you recheck for updtes

Did you remake the flash drive? That happens if the template isn't within /config/plugins/dockerMan/templates-user on the flash drive (eg: you inadvertently deleted it), is corrupt etc

exit code from rc.docker stop is not zero in your case so the rest of the commands never execute (&& continues execution if previous return code was 0)

This is what you want to use for the repository entry ghcr.io/mdhiggins/plexautoskip-docker:latest This is the thread you want But it's rather old and most of the images are missing But effectively you add in the applicable ports / paths that the container uses (you garner that from the dockerfile listed) and add them into the template with appropriate host mappings. If you don't understand what path / port mappings actually are, then best to watch Otherwise it is an exercise in frustration on your part.

You need to post the entire diagnostics and the syslog that captured the crash

You're free to contact support as you choose (a link is at the bottom of every page here), and include a link to this post, your diagnostics etc, but answers are likely to be identical to what has already been itemized. Get rid of the zero byte files and reboot. And upgrade the OS version and not downgrade. I don't think so. No different than saying that there's a knocking sound coming from your car when you're talking to a mechanic. In terms of your specific issue, it appears to be actual corruption.

After deleting / renaming, you need to reboot. Won't change a thing. If anything, you should upgrade to 6.11.5

Probably because no drivers are installed for the card. (ie: Unraid does not have drivers for any audio device installed)

Is there anything pulled? Is the status in the docker tab showing an update available??

Orphans happen whenever you make a change to a template and the docker run cannot execute for some reason. It also happens due to a bug in the Apps tab if you update a container from within Apps (and not the docker tab). Orphans are harmless and take up no real space. (Hence why the CA bug isn't a high priority at the moment) Are either of these situations applicable to you?

Your data is all safe. As the banner says, you need to post your diagnostics

Safari issue that comes into play depending upon if certain settings have been changed in the OS. Fixed next rev

Different, but related, and also fixed. My testing on that did show that cookie clearing did fix.

I now have a profound appreciation of just how messed up Safari is Anyways, this should be fixed on the next rev of CA (Monday ish release)

The next revision of CA will fix the issue some users have with crashing when running Safari on a actual Mac. Release probably happening on Monday. Root cause: Safari operates differently than every other browser past, present and future if and only if you've made a change to the font-size (possibly other entries) in Settings - Font Size that the OS uses. Clearing history and cookies on Safari will also fix the issue in the meantime.

Have you tried setting a Trim Schedule (or Trim now) in Settings, Scheduler?

https://unraid.net/contact

Yeah. inadvertent change to the .plg that messed it up. If it was summer and I had a pool, you have permission to beat me with a wet noodle