Squid

Wrong support thread. But, what it's saying there is that an app you named jellyseer-1 was using .../appdata/jellyseer What is the appdata (/config) path for what the container is you currently have installed?

Nothing to think about. It's there. IE: Can't fix what ain't broke.

FWIW, readability as a whole along with general aesthetics was better previously than now currently. While it is usable, I definitely prefer how it was.

Effectively unlimited compared to the size of drives you can buy. While there may be some limitations somewhere over what the theory is on file system maximums (eg: XFS supports a maximum 8 exobyte drive size), not currently available hard drive even remotely comes close to this size.

Your server is unable to reach either GitHub.com or Limetech's mirror of the application feed. Fix Common Problems, and diagnostics also shows this behaviour. Assuming that there is normally no issues with reaching them due to your geographic location, a complete reboot of your network system (modem, router, all switches) would be the first thing I'd try. Also, if you're using jumbo frames (probably not) then disable them

Does the update work if you switch to English?

If only to rule it out, you should run memtest from the boot menu for a minimum of a couple passes (ideally 24 hours) Hope you mean "new to you". The CPU was introduced in 2012, and long discontinued.

Wrong thread lol

Dashboard considers I/O wait in it's displays. Next time it happens, reply back with your diagnostics before you reboot

You need to contact support. Include a copy & paste (no screenshots) of what shows up within Tools - Registration

Version that you're running is from the new dev.

/mnt/user is a unified view of all the shares. Every share exists within there, along with /mnt/diskX (or /mnt/cache)

Because appdata also exists on disk3. Set the secondary storage to be array with mover action of array --> cache, stop the docker service in Settings -> docker and run mover.

And on a reboot the patch shows as not being installed in the plugins tab (don't worry about the install errors one)

Long standing issue (fixed I believe in 6.13). It also has the net result of whenever you go to the VMs tab it's a given that all/most of your drives will spin up

Fixed next release. Thanks

You can admit it. Annoying me is also one of your goals 💋

You're probably also seeing a banner that's warning about CA and PHP errors being set to display on the screen. Unlike the rest of the GUI, CA's server side executables only send JSON responses. So any PHP error (when set to display), results in the browser receiving the JSON and the error which results in a JSON syntax error, which then results in more or less a fatal error as the above. But, thanks for finding In this case, someone listed the same Branch Tag in a template multiple times. No clue who did that mistake on a template, but CA will now drop the duplicate tag altogether in that circumstance.

Since the language you're using is Chinese, have you installed the Chinese Proxy Manager? Your server is unable to reach either GitHub or the Limetech hosted alternate feed quite possibly due to the Great Firewall

When you install When you install it does an error show up in the popup window? You can always post your diagnostics too.

Check every docker container you have and see if there's a direct reference on one or more of them to /mnt/cache. Likely need to hit the "down caret" to see all the path mappings for some of them.

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.