Squid

You're running Brave as a container, and there's an error within it. Nothing you can do about it. You'd have to ideally post in the Unassigned Devices thread with your diagnostics showing that behavior

The board is 11+ years old. The driver being used (RTL-8111 et al) is quite common, so I'd surmise that Realtek dropped support for the actual chipset being used in latter versions of the Kernel. Spend $30 and grab an add-on Intel card. (Although, there is an update to the BIOS available which states "Support Upgraded LAN")

no

2021.11.13 Added support for screenshots, videos and more. Maintainers: See these posts: https://forums.unraid.net/topic/38619-docker-template-xml-schema/page/4/?tab=comments#comment-1051850 https://forums.unraid.net/topic/115672-ca-developer-profiles/?tab=comments#comment-950547 Can be added to plugins, docker containers, and ca profiles For an example of what you can do, look at the MyServers plugin in CA Template errors will now display on every app's information sidebar On every app information display, you may see something akin to This will show the user exactly what CA is modifying from the maintainer submitted template so that the user has an easier time installing / using the app, or if CA was unable to automatically fix what to look for. Hopefully by making these errors more visible (rather than being buried in the Statistics section) the maintainers will be more likely to fix them. Various other fixes and tweaks.

Buy a bigger house. Problem solved

Yeah. IIRC that got fixed in and around 6.7.0 Nothing I can do about that though as it's an OS thing.

Best to post in the applicable support thread or the Project page for the container (click on the icon)

Nov 12 04:14:36 WOPR kernel: BTRFS error (device sdd1): bdev /dev/sdd1 errs: wr 0, rd 0, flush 0, corrupt 14092, gen 0 Looks like the root cause is the cache drive itself. Wait for @JorgeB to pipe in.

Are you in a geographical locale that may be interfering? eg: China?

You're booting via UEFI. Temporarily switch to boot via Legacy / Normal in the BIOS

Looking through the code, it's the only way I can see that it's possible for this to happen, (or if an adblocker or the like is blocking certain cookies from being saved - always whitelist your server in your adblocker's settings)

I'll think about it

If no light ever pops up, maybe the port itself is dead But, you can always post your diagnostics here

That makes sense as to why there's an issue, but it always implies that the apps aren't friendly to a docker system. Absolutely.

Admittedly I've always been a little bit confused over what the actual issue here is. Just because a port exists in the template does not mean that it's exposed to the WAN. And, if you're using custom networks (eg BR0) or host, then any and all port mappings are ignored anyways. (ie: install the default cAdvisor template from CA - You'll hit the webUI on port 8081. Delete the port and you can't hit the webUI. Now move the container to br0 and you'll hit the webUI on port 8080 even though the port doesn't exist in the template) Whether or not the port exists in the template (or the docker run command) does not stop the container from opening the port. All it does is tell the docker system what to do when it's attempted to be accessed from outside the container. And in the case of host / br0 the mappings are ignored by design from docker itself. It's why if you install any of the Plex Containers they do not have any port mappings in the template, yet they work as Host / br0, but if you switch the template to bridge they will fail) Because @ich777 told me that there could be issues (once again I do not understand why), provisions were put into place to prevent the template from being updated if the container updates. Note that simply stopping and restarting a container will NOT ever update the template. Only an update to the container itself (not to the app within) will also have the template updated. This provision is not a work-around, but is a by-design feature. It's just not accessible via the GUI to prevent users from inadvertently changing the entry to something that doesn't work (80% of the maintainers can't figure out the proper URL to put in there, so CA's appfeed fills it in automatically) As mentioned, there is no real way to determine if a port was deleted and you don't want it added again during an update or if the port isn't existing in the first place and needs to be added. All in all, the update system solves far far more problems than it creates and if (once again "if") there are issues with ports being deleted and causing an actual issue with the container if it gets re-added, then the provisions exist for the maintainer of the template (or the user) to be able to easily flag the template as "do not update this"

Did the name of the pool change from the SSD to the NVME?

The only way I could see that this was possible was if you have cookies completely disabled on your system(s), which the next release will handle this situation.

https://askubuntu.com/questions/14444/how-do-i-blacklist-certain-directories-in-samba

Nov 6 01:11:46 Tower kernel: mce: [Hardware Error]: Machine check events logged Nov 6 01:11:46 Tower kernel: [Hardware Error]: Corrected error, no action required. Nov 6 01:11:46 Tower kernel: [Hardware Error]: CPU:2 (10:2:2) MC2_STATUS[-|CE|-|AddrV|-|CECC]: 0x940040000000018a Nov 6 01:11:46 Tower kernel: [Hardware Error]: Error Addr: 0x000000013ceba980 Nov 6 01:11:46 Tower kernel: [Hardware Error]: MC2 Error: : SNP error during data copyback. Nov 6 01:11:46 Tower kernel: [Hardware Error]: cache level: L2, tx: GEN, mem-tx: SNP Not sure what to make of it...

Probably convenience. Edit the file on the flash drive using directly instead.

AMD video card passed through?

Public IPs are not in the diagnostics.

Are you running some other script that's changing the permissions?

Any adblockers / extensions that may be interfering? Try setting static DNS addresses in network settings of 208.67.222.222 / 208.67.220.220 And while you're at it, check the date / time on your server

Moved