Squid

Now that everything is all back to normal, and I've got a couple of minutes, here's the low-down on the 21st's update Legacy mode was always only in there is a backup for the circumstance of if the primary application feed went down (since I was not in control of the feed). Due to the nature of the replacement appfeed system, if it goes down then Legacy mode will not work either. Hence the code was pointless. Now the vast majority of checks, fixes etc are performed by the application feed itself instead of by CA. Net result is that CA now only downloads a single processed file resulting in lower bandwidth and faster initialization. Previously, CA sent through to dockerMan when installing a template a watered down Overview that wouldn't have had any formatting etc within it. Now, CA sends through the unaltered overview for the user to see when installing a template. Note that the appfeed still applies certain checks to the unaltered overview, and malicious code results in automatic blacklisting. Hopefully these changes solve the weird case that pops up occasionally of where during an update the apps tab disappears completely. Now, whether or not you have unRaid checking for plugins, or on whatever frequency you may run it, CA will always let you know if it is out of date. This is grabbed straight from the appfeed itself, so you may see that CA knows that an update is available but the plugins tab shows that there is no update available (trust me: CA is right ) As usual, you can install the update for CA either directly from CA or the plugins tab (after checking for updates).

I don't believe that any testing / reconfiguring of the UI is done against IE / Edge. Everything is tested against Chrome / Firefox / Brave / Safari

k I'll add to a todo list

If it exists, delete /config/plugins/dynamix.plg on the flash drive and reboot

It doesn't Sent from my SM-A530W using Tapatalk

Settings - Identification - Management Access

Cache dirs has (or had?) an issue where it doesn't start up after a reboot. Go to its settings and toggle the enable function. Because the system looks for the file(s) on disk 1. If it doesn't find it, it goes to disk 2 etc...

It's part of the mover script Sent from my SM-A530W using Tapatalk

Up for me now... But GitHub's status still states that it'll be hit or miss

If you only have two disks, then you would assign the larger one as parity if they are different sizes or if they're the same size then it doesn't matter which is which. Logging off til the morning, but if something comes up as unmountable then wait for someone else to take over before you do anything else Sent from my SM-T560NU using Tapatalk

You can always do it manually Format a fresh USB ( less than 32G ) as FAT32. Name the drive UNRAID Extract the contents of the zip file downloaded from LT's website onto the flash Run as Administrator the make_bootable.bat script

Extremely unlikely. Make a new USB stick with LT's USB Creator Tool. It should at least get you to a webUI. If that works, then copy from the old flash to the new one the Basic.key file and boot again. It will either give you the ton of errors again or it will walk you through transferring the key. If it transfers, then reassign your drives. If it gives you all the errors again, then register the flash as a trial and contact Limetech to manually transfer the registration over to the new stick.

Can you still access the shares over the network as before? If so, whitelist your server in your ad-blocker running on your browser. If not, post your diagnostics

Try running Tools - New Permissions against the particular share. If in doubt about what you're doing, then run Tools - Docker Safe New Permissions if you have Fix Common Problems installed