Squid

Can you reply back with your diagnostics

Sorry for the late reply. You'd have to post your diagnostics

If anyone receives an unknown plugin installed (specifically with regards to TailScale) there’s an update for FCP to handle this. Additionally there is also an update for TailScale available

Why are you running such an old version?

Error 5 implies that the date & time is significantly off on your system. Go to Settings, Date & Time

Turn off template authoring mode in Settings - Docker with the docker service stopped

Post your diagnostics

Likely created by a docker container where it included that path within the template.

Which beta 2? Current version is 2.10 FWIW, works perfectly for me

Shouldn’t show as blacklisted. I’ll check it out. Thanks

Forgot all about it TBH

At any point did the drives come up as uncountable and you formatted them?

Try disabling any extensions in chrome

@Schwiing You ran into a weird edge case in CA which I was able to replicate, but the chain of events that led up to this on your server probably started years ago. Rather complicated to explain, and I'm quite sure that what I posted on an internal bug task list that other developers from LT also see makes no sense to them at all. Either way, I know what's happened (or at least partially what's happened on your installed containers) and can fix what you're seeing. Net result is that you do have a container installed that is either blacklisted or deprecated. Fix Common Problems will tell you which. Your GUI issue in CA will be fixed in next release of CA.

Easiest to restart when convenient. Logs will stop growing, and you're good for awhile before the size actually causes problems

Apps Depends upon how the app is being marked as incompatible. If it's marked by myself as incompatible, then the following will work: Apps, Settings - Enable Show Incompatible Apps If it's marked by the author itself as being incompatible, then you have to manually edit the .plg and remove the constraints (eg: Max in the .plg entities) and then once saved onto your flash drive somewhere, install the locally saved version. IE: This is a pain to do, and if you're not following what I'm basically saying of how to accomplish in this circumstance then its a safe assumption that you shouldn't be doing this in the first place. Either way, incompatibilities are usually set for good reasons and aren't recommended to be overridden

Looks like you've got a container which is restarting itself every 5-10 seconds. The uptime on the docker tab should tell you which one is having problems starting up

Actually, just run Fix Common Problems and it'll show exactly which

Thanks. I swear I've fixed this before (could be wrong), and am sorting it out. What you've got is a container installed that is also blacklisted for some reason. While I'm sorting this out (might not be for a couple of weeks as going on vacation in a couple days), comparing what you've got installed (docker tab) vs what appears within Apps, Statistics, Blacklisted Apps will tell you what is triggering it and the sidebar will likely tell you why

I'm going to wind up deprecating this plugin on Unraid 7.0.0 stable I have no time to maintain the packages within this, (not to mention that I don't agree with what this plugin actually does). Thus far, there has been zero interest from anyone in picking up the maintenance of this, so because many of the packages will need to be updated to work in 7.x+, it's time to let it go and save everyone the aggravation. If anyone want to pick up the maintenance of this plugin (and fork it), then drop me a line here via PM

^^^ this. Containers are by definition "sandboxed" and only have rights to the files / services that you give to them. That being said, things like common miner software executing are one of the checks of Fix Common Problems, and if there is ever any malware that is within Apps, that has been missed, then please PM me. Plugins though are a different story and every update issued to them tends to be code reviewed looking for malware etc. Additionally, Apps also has the ability (if enabled in its settings) to handle major stuff like alerting everyone who might have container "X" installed if "X" proves to be a big danger.

Aug 30 10:08:51 Beancloud kernel: mce: [Hardware Error]: Machine check events logged Aug 30 10:08:51 Beancloud kernel: [Hardware Error]: Corrected error, no action required. Aug 30 10:08:51 Beancloud kernel: [Hardware Error]: CPU:2 (17:71:0) MC3_STATUS[-|CE|MiscV|-|-|-|SyndV|-|-|-]: 0x9820000000010150 Aug 30 10:08:51 Beancloud kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000001a001e04 Aug 30 10:08:51 Beancloud kernel: [Hardware Error]: Decode Unit Ext. Error Code: 1, Micro-op cache data parity error. Aug 30 10:08:51 Beancloud kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD On die cache error in the CPU. Corrected for now, but may (or may not) get worse and require CPU replacement

Best to post here

Reports that it doesn't work. Deprecation doesn't do anything other than it won't show up in searching for it unless within CA settings you enable show deprecated apps