Squid

Tried the following: Chrome (Windows & Mac) Firefox (Mac) Safari (Mac) Brave (Windows) Edge (Windows) Internet Explorer (Windows) Everything worked on editing a script except for Internet Explorer, but since Unraid doesn't support it to begin with (and the GUI won't even load on it) I'm not worried about IE Is it an ad blocker or something?

But that's wrong behaviour and a bug IMO @ljm42 update_cron should be run regardless if user shares are enabled or not. The mover script should be intelligent enough to figure out that user shares are not enabled. update_cron is an integral part of the OS, and many plugins rely upon it. User Scripts, Parity Check Tuning, SSD Trim, CA, FCP etc etc. None of those require user shares to be enabled. It isn't mover related per se, but rather scans all .cron files within /config/plugins and adds them in unless the system runs in safe mode.

@dlandon What are you having trouble with? Editing an existing script works fine.... And adding a new script and editing it also works for me...

update_cron is part of the OS itself, and is supposed to run every boot unless you're in safe mode. Can you reply back with your diagnostics. FWIW, my custom stuff gets added no problems on every boot....

Sep 4 12:29:35 DeathStar kernel: BTRFS info (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 5, gen 0 First thing to do is to run a memtest from the boot menu for at least a couple of passes. Most causes of "Corrupt" is due to bad memory. If you're booting via UEFI, then you will need to temporarily switch to legacy boot or set up a new memtest stick via https://www.memtest86.com

Its either GitHub (they were having some problems yesterday) or your server is unable to reach github itself. Not much difference except that plugin installs may fail and some icons for various apps may be missing.

CA pulls the stats off of dockerHub, so it is across the board -> not unraid specific. Until the container reaches a certain threshhold of pulls, CA doesn't show the counts or keep graphs etc on it.

No problems here. You should reply back with your diagnostics after trying it again.

Enable debugging in Settings - Community Applications Go back to Apps. After the error re-appears, click on Debugging at bottom left and upload the zip file here. (But update the plugin via the Plugins Tab first)

yes

So reapplying the settings re-adds the cron schedule to /etc/cron.d/root? Next time you reboot, before you fix the settings, see if /config/plugins/user.scripts/customSchedule.cron exists on the flash drive. and if it does will update_cron fix the issue?

Enabling CA's debugging (Settings - Community Applications) and then going to Apps, waiting for the error and finally hitting "Debugging" and uploading the file might shed some light. I would however also try running your browser in incognito mode / no extensions whatsoever and see if that makes a difference. (There are some extensions that hijack communications which CA / Unraid (and many other websites) do not play nice with.

Unraid starts fresh with every reboot, so you need to save the changes on the flash drive somewhere and then re-apply them via the go file (/config/go) or user scripts when the system starts up.

On the docker tab if you switch to advanced view is there any orphaned images -> delete them

powerdown -r

Not following. FCP is telling you that there are updates available for some container and you don't want to see them and you don't want to tell FCP to ignore them. Your message is not coming from the OS and notification settings. It's coming from FCP which allows you to ignore (ie not send) any specific notification.

Yes. Because of the 404, every app in that repository is now removed from Apps

Have you hit "Ignore" on the specific warnings you're getting within Fix Common Problems...

Unfortunately that error is hard to determine on 6.11 what its from (far easier on 6.12 to figure that out) but, it does appear that you *might* have memory issues (run Memtest from the boot menu) and the appdata plugin seems to run about twice a day for an hour or so and it does try and stop everything from running.

You'll need to post your diagnostics

Aug 10 16:29:44 Stark kernel: BTRFS critical (device sdd1): corrupt leaf: block=5451645927424 slot=57 extent bytenr=5341179084800 len=16384 unknown inline ref type: 255 First thing to do is run Memtest from the boot menu for at least a couple of passes as corruption is usually caused by bad memory. If you're currently booting via UEFI you will have to temporarily switch to legacy boot or setup a new flash drive from https://www.memtest86.com/

Looks like you removed a bunch of files / folders from the diagnostics. We need them all. Assuming though that you are using a docker image (Settings - Docker) then what you are seeing is correct. You've set the image size to be 72G (bit large for 99% of users but besides the point) and the graph shows what is in use within that 72G Docker image is pre-allocated to the size you set (and there is also overhead, which is why you're seeing more than 10% on the graph

Click the Search Icon top right. (Or CMD-K / CTRL-K)

Does it make any difference if you (in Sab's settings) have it pause downloads while it's unpacking?