Squid

Getting Legacy Mode to work on a slow internet connection (where it takes more than 2 minutes to do its thing) is on the to-do list. It just doesn't come up very often that legacy mode is even required (but it is there for this eventuality), and combined with a slow internet. If it takes longer than two minutes, the "Updating" screen will never disappear, but it still does the thing in the background. Give it say 10 minutes, then just reload the page and you're in business

A button appears called Legacy Mode (top right) which will let you use CA (The note is there on the screen telling you the feed failed). Reason CA doesn't automatically fall back is the majority of times the problem is on the user's end (DNS settings, etc) and I'd far rather have them fix that than have Legacy active, since Legacy will take ~30-60 seconds ish to start up (and if you have a really crappy internet speed, then it could take minutes and after 2 minutes, mginx in 6.4+ will automatically time out). All vs appFeed mode which will take worst case ~10 seconds to get things running

Switch to "Legacy Mode" (top right) which will allow CA to limp along.

why?

Upshot is that the rare outages let me find out minor issues (mainly PHP warnings) that happen in this circumstance and fix them

The vdisk size has already been set (when you originally created the VM) To change the current size, you do it by clicking on the name of the VM and then you can change the size of the disk . (6.4 or 6.5-rc3+) You can (at least on a Windows setup) also create a VDisk that will enlarge and shrink according to the actual disk space used by editing the XML appropriately (see the VM FAQ)

Any limit on a vdisk size is the size of the disk.

There's currently an issue that affects a minority of users and the docker tab,dashboard, and apps tab. If you're affected you'll see nginx timeouts in your syslog. Upgrading to the latest "next" version of unRaid should hopefully fix

Remove the app from the docker page (click on it, then remove) and then do it again. Looks like even if you reinstall using defaults dockerMan still hits the file on the flash drive for some reason.

Have you tried ssh to the VM IP

Can't make out the URL on my phone. Are you reinstalling from previous apps. That will give the same result since it reads the same file. You need to reinstall from available apps

No just tautilli

Have you tried starting it from the GUI? Autostart is disabled on your server.

ok. Then the file itself is just plain trashed, but without filesystem corruption. The only real recourse here is to reinstall it from scratch and add in your appropriate path mappings

Put it in a windows machine, This PC, right click on the drive Properties, Tools - Check unRaid does a limited subset of checks during every boot, but the Win Tools are probably better

https://lime-technology.com/forums/topic/57181-real-docker-faq/?page=2#comment-566088

I'm on time See 2nd Post

The drivers are not installed in unRaid, so in order to do hardware transcoding, you would need to run Plex in a VM with a video card passed through.

Its a corrupted file on the flash drive. Take the flash, toss it into a baremetal box and run file system checks on it.

yup

2 totally different things accomplishing different tasks.

ok Started thinking about it today. Tomorrow ok for you? Easy to add an inline variable to the script (think I have them documented in the OP) to do just that. UI checkbox / whatnot would be in the same category as #1 https://www.youtube.com/watch?v=pUdhaDCvPWY

Exactly what I wanted to know. Helps out the helpers around here knowing the rules being applied since its not obvious

Yes, its windows based. I don't however have a lot of experience with it. BUT, pretty much anything you do to recover the files (especially since you're odds on going to be removing the drive from your server) is going to wind up effectively invalidating your parity information anyways. I'd see if @pwm or @johnnie.black have anything to say before doing anything.

Curious how this is being handled I purposely named my server to be incompliant (Server_A), and I see in the syslog that it's been automatically redone as Server-A (although the top right of the UI) still states Server_A. Server_A's webUI cannot be reached, but Server-A can be. Don't want the nitty gritty, but an overview of the rules which you're applying.