What kind of problems do you catch with beszel?

Check out gatus. Super easy to get up and running depending on what type of monitoring you want to do.

You misspelled spyos.

Nothing requires kubetnetes. Can you scale with kubetnetes easier? Maybe, but then you’d have to learn kubetnetes. Even super scalers like Netflix ran for decades without kubetnetes and then for other reasons they moved. Self hosters only need kubetnetes if they want to learn it.

By your parents a computer and put it on their network and back up locally and remotely on their system. Bonus run immich for them also.

I get all my back up redundancy but helping others host.

Why not just straight wireguard?

Look at dmesg?

Look at the last boots:

journalctl -o short-precise -k -b -2

I run it in a container without problems. All you have you do is bind it to port 80 and 443. I prefer the container to running it directly within the host OS for ease of portability.

Also strongly recommend building it with support for DNS based validation. Using DNS validation you can have multiple instances running across the different servers you have to easily switch to or provide better local routing. For example please. I run one caddy frontend on a VPS that routes my traffic most of the time, but when I’m at home my DNS points me at a caddy instance that is running on my server on my home network avoiding the path of out to the internet and back home. Using http based validation would require me to sync certs around.

Check out caddy. Very straight forward syntax for a reverse proxy.