Squid

Maybe there's some miscommunication here You have an xfinity router that your landlord controls, but you have access to it. That router feeds your router which then feeds your server I suggested to put YOUR router into the xfinity's DMZ and do all of the port forwarding from YOUR router to YOUR server. Do not put YOUR server into YOUR router's DMZ. Doing any port forwarding on the xfinity isn't going to accomplish anything

Tools - Update OS, switch from "Stable" to "Next" to start using the RC series

Here's the problem. I most likely do not run the same containers etc as you do. And additionally I don't really have the time to start going through file by file in the various apps to determine what permission / ownership belongs to which file. You first have to determine what works and what doesn't with the trashed permissions. Your idea of installing to a separate appdata share is reasonable and as good a place as any to begin Something like this is best left on the forum where the most amount of eyes can get a hold of it. More eyes (including @JonathanM ) would be able to help you attempt the recovery. Personally, for my use case on the containers which I run it's easier just to start the appdata over again

In addition to what Trurl suggests, when ever I know that the subnet on the modem / router has changed due to a hardware change, I simply go to the router's settings and change the subnet that it uses to match how my previous setup was. Saves a ton of reconfiguring when you may have containers and/or other devices on the network that are accessing services via an IP address

Feb 24 17:38:09 NASHorn2 kernel: smpboot: CPU0: Intel(R) Core(TM) i3-10100 CPU @ 3.60GHz (family: 0x6, model: 0xa5, stepping: 0x3) Feb 24 17:38:09 NASHorn2 kernel: mce: [Hardware Error]: Machine check events logged Feb 24 17:38:09 NASHorn2 kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee2000000040110a Feb 24 17:38:09 NASHorn2 kernel: mce: [Hardware Error]: TSC 0 ADDR fef20080 MISC 3880000086 Feb 24 17:38:09 NASHorn2 kernel: mce: [Hardware Error]: PROCESSOR 0:a0653 TIME 1645720663 SOCKET 0 APIC 0 microcode e0 Feb 24 17:38:09 NASHorn2 kernel: Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver. First line is the start of initialization and the last line is where it's continuing on. Without a mce being issued, the entire middle section isn't present. No big deal, and happens (probably due to microcode updates taking place)

Each and every app's appdata may have it's own unique permission and ownership requirements within it's appdata share. Changing the ownership may adversely affect the ability of the app to operate. Your best bet would be on anything that doesn't work to set it's permissions on all files to be 0777 and hope for the best. If that doesn't work, you would have to ask in the individual app's support threads and hope for the best. Personally, I'd just start over again on setting up the app if possible as it may be faster at the end of the day. As an aside, this is the entire reason for the "Docker Safe New Permissions" tool being present with Fix Common Problems as it specifically excludes the appdata share

Yes, because you're not using Bridge anymore

As soon as you take the container off of "bridge" mode (which you have), it uses whatever ports that it wants to (ie: what you've specified in the application itself. What it looks like you're seeing is a GUI anomaly where because the port is still defined in the template it's still trying to display the mappings. You can always just delete the port from the template screen.

This is the best I can offer you https://wiki.unraid.net/Manual/Security#Securing_webGui_connections_.28SSL.29 I myself know nothing about the subject at hand.

You've got a whack of general protection faults on a command that I've never seen issue one. I'd start with running a memtest from the bootmenu after you hard reboot

Appdata backup plugin will make all the backups of your entire appdata share. For changes to templates, the same plugin will also save them, but it's not a "dated" backup set

LSIO has changed the description they used to include. If you click on the ReadMe First either within CA (Support) or after it's installed by clicking on the icon, the same directions will show up

@ljm42

"Corrupt" being reported on btrfs implies (not necessarily though) a memory issue. Run through a pass or 2 of memtest from the boot menu (if you boot via UEFI, then you'll have to temporarily switch to legacy)

Yeah, it's all done via a browser How I would go about it would be to stick your router into the xfinity's DMZ to make life easiest and then do port forwarding from your router.

Forgetting about no answers to the OP's question, you need to post your diagnostics in order for anyone to begin to answer anything.

Community Applications - Your server requires internet access Community Applications requires a properly functioning internet access in order to operate. The most common solution for lack of internet access is to manually set up DNS addresses in your Server. Go To Settings - Network Settings and assign at least two of your favourite DNS providers. There are many DNS providers, but some commonly used addresses would be: 208.67.222.222 (Open DNS) 208.67.220.220 (Open DNS) 8.8.8.8 (Google) 8.8.4.4 (Google) This problem is ultimately caused by your router not properly recognizing the server and performing the DNS lookups for you, so assigning the addresses works around the router's bug. This error can also happen if the date and time on your server is significantly off. Ensure that your date and time (Settings - Date and Time) is correct. Assign ntp servers if necessary and reboot to apply the changes. Other possibilities for this issue can be that you are operating piHole (or similar) or pfSense and the URLs that CA is attempting to access are being blocked. These URLs include (but aren't limited to): github.com, amazonaws.com, docker.com etc You should white list those domains (or ideally whitelist the entire server). Note that running your server's internet access through piHole isn't recommended at all because Unraid OS has no ads whatsoever to block, and piHole just introduces a whole other layer of complexity to your network that can be troublesome to solve. Certain political jurisdictions (China) may also have further challenges involved in having CA gain access to those URLs. There is information within the various Chinese threads here that will offer up solutions. Lastly, if you are running your server and need a proxy for internet access, you would normally be modifying the "go" file on the flash drive to configure the system to access the proxy. Because of how Community Applications works however an additional file / modification needs to be made. See this post: https://forums.unraid.net/topic/38582-plug-in-community-applications/page/122/?tab=comments#comment-848436 for what file to change for the proxy setup. If all else fails, then you should create a new thread within General Support detailing your problems and also including your diagnostics so that other users may be able to help. (IE: your problems may be a general network problem or configuration issue)

Do you have a locally attached keyboard / mouse / monitor? Or from another computer on your network you can try ping whatEverIPaddressItIs to see if it even responds to the network.

There should be no issue with outgoing access. Incoming access (like to Plex) would be a challenge without the ability to do any port forwarding on the main router. Effectively you need to ability to gain access to the main router so that you can stick your router into the main's DMZ or individually forward the ports from the main to yours and then from yours to the server.

I can't replicate this with Firefox and 6.9.2 at all Your browser quite simply stopped executing the code as far as I can tell. CA did return what was supposed to be displayed, but then never went to where it was supposed to figure out what was supposed to be in the autocomplete search entries I would clear the browser cache, make sure that Firefox is up to date, disable any extensions, and try Edge or Chrome to see if it makes a difference.

Set an a power saving curve on the CPU fan in the BIOS. Undervolt the case fan to 5V instead of 12 depending upon how its connected. Not huge savings, but it'll add up over time. Depending upon how often in your use case the drives have to spin up, either set them to never spin down or add in a cache drive. If they wind up spinning up a lot, you're trading off the high spin up current required to instead be the low current required to keep them spinning. A cache drive would accomplish the same thing. Keeps the drives spun down for writes

Try a reboot You've got a lot of weird little errors happening in the server, but nothing directly "wrong" If the problems continue, go to Settings - Community Applications, enable Debugging then try the apps tab again. If it fails again then go back to Settings, Community Applications and download the debug file and post it here Also, you should never do this Feb 25 19:08:27 Cerebro emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/newperms /mnt/cache|/mnt/user/system Running the new permissions tool against a drive (cache) may impact your ability to have functioning docker containers because they may have their own unique permissions etc If you have Fix Common Problems installed, use the Docker Safe New Permissions instead

So you're running an ancient version of the OS (6.1.9) There were some issues with the file system on both the cache drive and disk 1 (most likely due to the power cut) To be safe, I would run the check filesystem against both of them. I would also seriously consider upgrading the OS to 6.9.2+ as there is a multitude of security and OS enhancements (not to mention diagnostic improvements that help with problems such as this) I'm not sure however if the files that disappeared due to the power cut will be recoverable. Every computer should have a UPS attached to it and set up to do a clean shutdown in case of a power failure, as this is where filesystem problems, corruption etc all come from

Thanks. The update is going to ignore anything that parses out correctly as JSON

Probably a misconfigured container somewhere along the way. Would be helpful if you could run this script and post the output https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/3/?tab=comments#comment-1090710