Squid

What version of the OS is this on? I had the same thing happen once during testing on 6.10.0 but couldn't replicate it afterwards. Either way, you should be good to go -> just hit Tools/Unraid Patch

Über Google Translate: @ich777 Sie können dies gerne bearbeiten Nach der Installation des Plugins (und der Zustimmung zum Popup-Haftungsausschluss) läuft der aktuelle Vorgang folgendermaßen ab: Wöchentlich werden Patches geprüft. Wenn ein Patch verfügbar ist, werden Sie über die von Ihnen festgelegten Benachrichtigungseinstellungen benachrichtigt. Die Benachrichtigungen von „Häufige Probleme beheben“ informieren Sie derzeit nicht über die Verfügbarkeit weiterer Updates, aber das wird sich in Kürze ändern. Nach der Benachrichtigung können Sie die Patches entweder über „Tools/Unraid Patch“ anwenden, oder sie werden beim nächsten Start Ihres Servers automatisch installiert. Mit dem nächsten Update des Plugins wird es Änderungen geben, wie dies alles abläuft. Sie haben die Möglichkeit, das Plugin die Patches automatisch anwenden zu lassen, sobald sie verfügbar sind. Sie haben die Möglichkeit, das Plugin die Patches bei einem Neustart nicht automatisch anwenden zu lassen, wenn Sie sie nicht selbst manuell angewendet haben. Sie haben die Möglichkeit, das Plugin automatisch aktualisieren zu lassen, wenn ein Update für das Plugin verfügbar wird. Mit anderen Worten: Beim nächsten Update des Plugins geht es ausschließlich um die Wahl des Benutzers, wie und wann die Patches angewendet werden. Limetech empfiehlt dringend, dass jeder das Patch-Plugin installiert ----- Original English: Current operation is after the plugin is installed (and the popup disclaimer is agreed to) is that: Weekly checks are done for patches If a patch is available, you will be notified via however you have set your notification settings up. Fix Common Problems and it's notifications does not currently tell you that further updates are available, but this will change shortly. After the notification happens, you can either apply the patches by going to Tools / Unraid Patch or they will be automatically installed at the next boot of your server. Coming on the next update of the plugin there will be changes to how this is all done. You will have the option to have the plugin automatically apply the patches once they are available You will have the option to have the plugin not automatically apply the patches on a reboot if you have not applied them yourself manually You will have the option to have the plugin automatically update itself if an update to the plugin becomes available In other words, the next update of the plugin is all about user choice in how / when the patches are being applied. Limetech highly recommends that everyone install the patch plugin

Changes due next week regarding auto installations. This feature set got side tracked due to the unforeseen issues regarding what Mover Tuning is doing. We highly recommend that this patch plugin be installed and the patches being issued are applied

With mover tuning installed, installing the patch from the GUI will fail and a notice will display advising to reboot to apply the patches. Mover tuning actually replaces the mover script (why this patch fails), but there seems to be a fair amount of issues with Mover Tuning as of late even before this patch came into existence. Best to ask over in its support thread

Yeah, that was my bad. @ljm42 and myself went through a ton of testing yesterday via a different .plg file and when I did the release this morning, muscle memory dictated that I simply updated the changelog and MD5 in the "normal" plg file and not the one which we were testing -> hence the need for the quick second release.

On today's update the issue with mover tuning is mitigated. During a reboot of the server, the patch plugin will install first before any other plugin. This allows it to patch the files as set by the OS instead of attempting to patch a file which has been modified (or replaced) by another plugin (eg: Mover Tuning) If a patch fails to install via the GUI, then a reboot will be suggested to perform.

A reboot would have been necessary. We are popping out an update to the plugin in a couple of minutes

Because generally CA is how you install any applications, especially plugins. That way you only are able to install stuff that has been vetted, is compatible etc. After CA being in existence for almost 10 years, nobody really publishes any URLs for plugins, or for template repositories anymore.

correct

Paste this URL into Plugins, Install Plugin https://raw.githubusercontent.com/unraid/unraid.patch/refs/heads/main/plugins/unraid.patch.plg

The reason for the failure is because you have the mover tuning plugin installed which (against best practices) modifies one of those files that are being patched. We’re shortly going to release an update that will address this, but the failure is due to mover tuning and not the patch (or the plugin)

the pinned post at the top of every page lets you install CA on OS versions <6.12 and then the patch plugin

You should post the full diagnostics. And also update all the plugins

Not going to comment on the paths or redis (looks ok to me) as I don’t use the container, but to understand path mapping look at (I always search for dancing girls to find it)

FCP does not use the settings for docker notifications -> it uses it's own notifications on sending things (errors + warnings, warnings or none)

The just released update (2025.01.26) should fix the spurious background check returning on occasion a false positive notification

Thanks for finding. An update to the plugin will be released later today

It's just a link to a licence wording.

Looks like a symptom of bad / failing memory. Run Memtest from the boot menu for at least a couple of passes 看起来像是内存损坏/故障的症状。从启动菜单运行 Memtest 至少几次

Interesting. I'm going to be looking at some further logging relating to this in the next few days, but in the meantime can you go to plugins, install plugins and paste this URL in https://github.com/unraid/community.applications/blob/0ae07b41998cc1d12ebe14c4f51156885dfb2e9d/plugins/community.applications.plg and then see if it works. If it fails, there should be a more descriptive message appear - post a screenshot. If it works then I'll put on my thinking cap After you do that, then you can hit the update on the banner. (What you're doing here is going back a couple of versions of CA before a specific change was made)

What problem exactly? Popup saying failed to communicate? Or download failure?

That implies it was a stale browser tab from a previous boot. (Which could possibly also explain why clearing cookies solved the problem)

It can be ignored in FCP if that's what you decide

Installing the unraid patch plugin is recommended on every Unraid system. It will keep your system updated with any critical OS patches outside of full releases of the OS 建议在每个 Unraid 系统上安装 unraid 补丁插件。 它将让您的系统使用操作系统完整版本之外的任何关键操作系统补丁进行更新

Blue is what it's supposed to be. Do you have theme engine or something installed on the other server?