HappyHarvester

I think this is more of a terminology/Googling the wrong thing issue, but I’m having some related issues: Rebooting usually means that all my Docker apps have new addresses, I don’t know if these are subnet address or subdomains or something else, but the address for app A might change from https://192.168.0.116/ to https://192.168.0.118 or something like that. This means that when I login via WireGuard, I usually play a guessing game to get to a given app. The Overseer + *arr apps also all completely break since all of the urls I give them swap every reboot. This seems like a standard enough issue, but I can’t figure out how others handle it so that you don’t have to RE tweak *arr settings every time or you can do something so you can consistently get to your apps without the bookmarks changing each time.

The Gigabyte PDF was exactly what I needed, thanks! For other's future reference, "advanced CPU options" was under "advanced frequency settings" in the M.I.T. menu pane.

I'm something of an Unraid newbie, but have mostly muddled through OK. As background, my PC was originally a dedicated Windows 11 machine, with Windows on an NVME solid state drive. I got Unraid up and running on other drives and could swap back and forth between them without too much issues, but then tried using the SpaceInvaderOne guide to run the Windows 11 install as a virtual machine. to the same error as this thread, and it looks like I have the same B450 BIOS (I think?), but can't find "advanced CPU options" or any references to "SVM." I may be missing something incredibly obvious but can't figure out what.

Aw awesome, thank you! This was exactly what I was looking for.

Unraid has been working mostly perfectly, to the point that I don't log in to the console unless I'm messing around with something which is my ideal. But Then I realized I wouldn't necessarily notice if I started seeing a bunch of parity failures or other non-catastrophic issues, so I'm curious if anyone has a good, simple set up for having their Unraid install send them alerts for Parity errors or other errors I should be keeping an eye out? If the entire server goes down, I'll notice that, but nots sure (beyond parity errors) what kinds of things are worth keeping an eye on. None of the data is super critical or time sensitive, but would hate for issues to crop up and become permanent losses because I didn't notice something broken for a few weeks.