• 0 posts
  • 20 comments
Joined 6 months ago
Cake day: December 24th, 2025
  • It’s pretty simple if you don’t own the router you don’t own the Wi-Fi. You can treat your home Wi-Fi a little bit like a public Wi-Fi and just make sure all of your devices are secure using encrypted DNS and encrypted traffic and overall not open on any unsecured ports and you should be fine.

    Personally, all of my services on my home server are only available through my WireGuard VPN, so it doesn’t matter what Wi-Fi I’m using, it’s always going to be encrypted peer-to-peer.

  • My personal journey:

    • arch is annoying to maintain and whil it is mostly stable, you do get some breaking updates here and there. It’s not a bad choice, it just doesn’t makeuch sense for a headless server.
    • Ubuntu server, just why? Works fine but why?
    • a not headless fedora, worked fine but still annoyed me sometimes
    • proxmox (debian based) works great, annoyed me to manage vm resources.
    • headless debian. Just works, I rarely if ever encounter OS issues. The only downside is that not everything can be found in the debian repos, but there is almost always an option to add a repo for whatever you want.

    My setup is mostly dockers so keep that in mind.

    But really, if something works for you go with it. If you are looking to change, I would recommend debian.

  • My setup is easy and reliable:

    Bash script that runs restic to backup to backblaze with a 90 day retention snapshot policy and a systemd service + timer.

    It runs everyday, everything is backedup to b2, and I don’t need to bother with it.

    Pros:

    • easy
    • quick
    • reliable
    • private (restic encrypts before sending)
    • don’t need to worry about multiple backups as backblaze does it for me (3-2-1 system)

    Cons:

    • costs (very little) money (backblaze is basically the cheapest provider)
    • long restore time as it would be slow to download
    • restore costs (pay per gb downloaded)