Squid

Those settings are for the built-in notifications. The plugin doesn't care about those two settings, and as a general rule you would have those two options disabled so that you don't get a notification that an update is available and when it was installed -> only when it's installed

And if you change the playback settings to force a different resolution does it work? The browser is reporting that it will work with the direct stream

Nope. Every single search brings up the link. No options exist to enable or disable

What share, and what version did you upgrade from? Does downgrading (Tools - UpdateOS, Restore) bring back access?

That's how br0 works. You're giving the container its own dedicated IP address and port mapping is ignored (and makes no sense) in that situation. You need to change the port within the application itself (it's own internal settings)

Feb 18 22:56:57 Tower root: rmdir: failed to remove '/mnt/user': Device or resource busy Could be as simple as a terminal with its current working directory within /mnt/user

No. I'm tired of answering the same questions about why update checks show up as unavailable so put a test into FCP to see if the plugin is installed and point you to it in Apps if it isn't

So far as Safari compatibility is concerned, I have no problems with it. On occasion I spin up a Mac VM to test and it always passes no problems. Could it be an add-on to Safari thats giving you issues? By and large users have no problems with Safari at all. Best suggestion is to grab CA's diagnostics and upload them here. Settings - Community Applications. Enable Debugging Apps - Wait up to 5 minutes then go back to Settings, Community Applications. Download the debug log and upload it here.

It's by design. You are putting the container onto it's own dedicated IP address and all port mappings if you try to change them are ignored by the docker system itself. If you need to change the port for some reason, you need to do it within the application itself (if it allows you to) so that it will listen on a different port. It cannot be done via the template

Actually a bug in the system and fixed next rev

Post your diagnostics after this happens.

Yeah, its not the plugin.

You have what appears to be a docker container that is continually restarting. The docker image is in the system share which is currently on the cache drive and disk 3. Impossible to tell from diagnostics where the docker.img file is on which of those two drives, but if its on disk 3 then what you're seeing would be expected. Go to Shares, next to system hit calculate. If you see 100G (which may be overkill) on disk 3 then that's your issue. Stop the entire docker service in settings - docker and run mover from the main tab

Via 2 methods: Method 1: Prior to the drive finally getting kicked out and btrfs having a conniption there is all of this very many times in the syslog Feb 17 12:47:03 Tower kernel: ata5: hard resetting link Feb 17 12:47:05 Tower kernel: ata5: SATA link down (SStatus 1 SControl 310) Searching back in the syslog for ata5 you wind up with Feb 17 12:43:36 Tower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 17 12:43:36 Tower kernel: ata5.00: ATA-10: WDC WD10SPZX-21Z10T0, WD-WX61A7852UTZ, 02.01A02, max UDMA/133 Cross reference that drive in the SMART section of the diagnostics and it doesn't exist at all (ie: no drive is connected) But it was connected originally as the cache drive Feb 17 12:43:39 Tower emhttpd: import 30 cache device: (sdb) WDC_WD10SPZX-21Z10T0_WD-WX61A7852UTZ Which leads to But, personally I think it was mostly method #2:

Check the connections to the cache drive. It dropped completely offline

Can you connect via navigating to the IP address?

Feb 16 22:24:35 Tower mcelog: failed to prefill DIMM database from DMI data Feb 16 22:24:35 Tower mcelog: Kernel does not support page offline interface BIOS update might fix if available, but otherwise harmless

Not a bug. You can find out what's going on by looking at the error returned by the docker run command

Your disk 4 I'd say is shot 197 Current_Pending_Sector -O--C- 001 001 000 - 28288 Also, what I'm assuming to be parity 2 ST8000DM004-2CX188_ZCT2X75X-20230217-1149 probably had it's SATA connection disturbed when you played with the RAM. Reseat both ends (and power)

Use the manual method of creating the flash drive instead https://wiki.unraid.net/USB_Flash_Drive_Preparation#Windows_Vista_and_Windows_7 (Easiest to use a drive that's 32G or less with this)

Enable Host Access To Docker Networks in Settings - Docker (Advanced View) with the service stopped

Logs are basically full because it appears that you have the ssh port forwarded to the internet at large (or the server in the router's DMZ). Script kiddies from around the world are constantly attempting to log in, so we can't really even see what's going on. If you need remote access use MyServers or a VPN solution

I don't see where any user names are showing up anywhere. But I put in a feature req for anonymizing VM names