Then you deal with it when you get back. Easy as that. If it is non-critical enough to turn off when you leave the house, then it is non-critical enough fix it later when you have time. Fixing software/bios/program errors are not time-sensitive.
Hardware now is EXTREMELY safe and it has to be tested against electrical surges, ESD events, and depending in the device, different temps in order to get CE conformity and UL ratings. There is a near-zero chance that it would cause a fire or something critical, especiallly because home servers typically are not under load most of the time.
I bought a Portable Power Station (e.g. Anker SOLIX C300) to use as an Uninterruptible Power Supply (UPS) for my homeserver (~ 40 Watt) to buy me - or better my utility company - a few hours in case the power fails.
I don't have one. It's just a tiny single board computer and an HDD running reasonably stable scripts every few hours and a couple of small server programs. Nothing it's doing is critical, so in the rare case when something breaks, it stays broken until I fix it.
You didn't mention it directly, but if you want to access any of your hosted services remotely, you will almost certainly want some kind of VPN solution. I host a few things over HTTPS,, but there's no way I'm exposing anything critical directly to the internet.
Server is running the password manager for myself and family, and that needs to stay on while gone (there are ways of handling local copies and they sync later, but when ive accidentally had to troubleshoot that it sucks).
Then ive got nextcloud, which while i don't normally need things on there i do enough that it is nice to have.
stuff on ulv soc hardware i just leave on 24/7. those are < 10w or so each with a load, so nbd.
anything i want to be able to get at remotely also stays on, obviously, as does anything required for the internet access and routing to get to it.
everything else is stuff that even gets shut down at bedtime unless it's "doing something".
everything gets shutdown and unplugged if i am going out of town for more than a weekend and have no need for anything to be on. which has happened a whole one time in the last 25 years.
So if you need to have access to files or containers but will be gone more than a weekend would you shut it down and take files with you, forget the container servers, or leave them going?
if that ever happens, i'd cross the bridge then. but i'd probably shut everything down. if i'm in 'vacay' mode and not at home, i wouldn't care about connecting to stuff at home. if i'm in 'work' mode, i'm taking shit with me i might need or putting it on space at the office before i leave.
i don't have what some would consider 'vital' services running. like alert notifications systems for various 'detectors' (co, power, flood, fire, etc), security cam recordings, and what not.
I suppose it depends on your use case, but I would disagree with points 1 and 2. Network connectivity has an effect on your entire network and is absolutely crucial. Pfsense/OPNSense, DNS, etc should always be on server-class hardware. I run these as VM, but I would argue that best practice is to have them on their own bare-metal server-class hardware. File storage is also incredibly important, and even with backups, I don't want my NAS going down. It also runs on server class-hardware.
The two items you mentioned are the two items I would be least comfortable running on consumer-grade hardware.
The server stays on, always. I have like ten people using the services on there over tailscale. There's a kvm, should something really unexpected happen.
My server rack gets shut off in only two cases: I lose power and am too slow in firing up the generator before the UPS shuts the servers down, or I need to do major maintenance (like replacing a PCIe card). So, virtually never for the most part.
Too many important sevices need to stay running, even when I'm not at home.
I do it if I'll be away more than just couple of days. Some of my hardware is pretty old at this point and I'm just a little paranoid about the possible fire hazard. I'm sure it would be fine to leave everything running but no real harm in shutting it down either.