Squid

Hmm... Somehow I missed that

@alturismo, what's with the xteve? is the alturismo/xteve now deprecated in favour of bl0m1/xteve? Should it be removed from CA?

Personally, I'd be most worried about the guy from France

https://forums.unraid.net/topic/57181-docker-faq/page/2/?tab=comments#comment-566095

the libvirt image has some problems Dec 30 17:02:26 Tintin kernel: BTRFS info (device loop3): disk space caching is enabled Dec 30 17:02:26 Tintin kernel: BTRFS info (device loop3): has skinny extents Dec 30 17:02:26 Tintin kernel: BTRFS error (device loop3): bad tree block start, want 30539776 have 7795346113052941553 Dec 30 17:02:26 Tintin kernel: BTRFS error (device loop3): bad tree block start, want 30539776 have 113003311045498874 Dec 30 17:02:26 Tintin kernel: BTRFS warning (device loop3): failed to read tree root Dec 30 17:02:26 Tintin root: mount: /etc/libvirt: wrong fs type, bad option, bad superblock on /dev/loop3, missing codepage or helper program, or other error. Dec 30 17:02:26 Tintin kernel: BTRFS error (device loop3): open_ctree failed Dec 30 17:02:26 Tintin root: mount error Do you have a backup of it? Also, does the following mean anything to you, since this all happened in quick succession? Dec 30 17:05:31 Tintin sshd[2376]: Invalid user yamilet from 92.242.240.17 port 56708 Dec 30 17:05:31 Tintin sshd[2376]: Received disconnect from 92.242.240.17 port 56708:11: Bye Bye [preauth] Dec 30 17:05:31 Tintin sshd[2376]: Disconnected from invalid user yamilet 92.242.240.17 port 56708 [preauth] Dec 30 17:06:20 Tintin sshd[3862]: Received disconnect from 112.162.191.160 port 33264:11: Bye Bye [preauth] Dec 30 17:06:20 Tintin sshd[3862]: Disconnected from authenticating user root 112.162.191.160 port 33264 [preauth] Dec 30 17:06:43 Tintin sshd[4599]: Invalid user pascal from 164.132.57.16 port 40849 Dec 30 17:06:43 Tintin sshd[4599]: Received disconnect from 164.132.57.16 port 40849:11: Bye Bye [preauth] Dec 30 17:06:43 Tintin sshd[4599]: Disconnected from invalid user pascal 164.132.57.16 port 40849 [preauth] Dec 30 17:10:30 Tintin sshd[11798]: Received disconnect from 49.234.30.113 port 45073:11: Bye Bye [preauth] Dec 30 17:10:30 Tintin sshd[11798]: Disconnected from authenticating user mail 49.234.30.113 port 45073 [preauth] Dec 30 17:12:02 Tintin webGUI: Successful login user root from 192.168.88.109

What's going on with your UPS? Every 20 minutes is loosing connectivity? reseat the cabling?

I'm going to go with that FCP's comment is correct by omission 🤬

Preface the commands with /etc/rc.d/

Setting this app to be incompatible with 6.8 until this gets sorted out. Let me know...

Plugin tab

Is it actually off? That would imply either a power supply issue or the cpu is overheating

This is the same problem as your VM issue. As suggested in the other thread, what happens if you reboot into safe mode?

Uninstall it temporarily, reboot and try again...

Probably best to post in the UD support thread

Does it work in safe mode when you select that from the boot menu?

The entire diagnostics.zip file (Tools tab)

You'd have to add in appropriate tests to determine that in your scripts The plugin can handle that for you https://forums.unraid.net/topic/48286-plugin-ca-user-scripts/?tab=comments#comment-475625 All scripts are executed as root. Either start a sub-script running as a particular user, or issue the appropriate chmod / chown commands after you're done. Should be noted however that on occasion you may need to specify full paths to commands that you may not have to when executing from the shell. IE: environment variables that are set in the shell aren't utilized in the plugin.

Its basic, but the config file editor plugin will let you do that.

you should post your diagnostics

Sure it's not just Windows (assuming you're using that) taking its sweet time to populate it?

Fair enough. To be clear though, your vision is that any custom theme would be "based" upon one of the existing four? Interested because CA when it runs across a custom named theme utilizes it's black css as a fallback

It was all semantics. If I went into super details on when / why you need it it would just confuse people even more.

I gotta leave some work for you on the support threads

I was moderately surprised that the CSS changes didn't mess up CA at all. Personally I would submit a PR with the changes to LT to create a new theme say "Black(dim)", but I suppose that you should also create an appropriately modified white theme as that's like staring into a MagLight at night.