February 12, 2026•2 min read••
Tags ▼
- ubuntu
- self hosting
- security
- home server
Most self-hosting guides show you how to install things.
Very few show you how to keep those things safe over time.
If you are running Ubuntu at home, this baseline is what I consider the minimum.
Not enterprise-perfect.
Just practical and repeatable.
I lock this down before installing anything else:
If I need remote access, I prefer private network access (Tailscale) over exposing SSH publicly.
Random updates are where mistakes happen.
I use a boring cadence:
Consistency makes maintenance calmer.
The baseline:
Open by exception, not by habit.
I run services in containers whenever possible.
This gives me:
I monitor a small set of signals:
And I treat backups as incomplete until restore is tested.
Daily backup without a restore drill is false confidence.
Hardening is not one command. It is a routine.
If your server feels boring in production, you are doing it right.
Lock down SSH access first (keys only, no root login, strong user policy). It reduces immediate exposure.
Apply security updates regularly, ideally on a weekly schedule, with a quick restart and health check routine.
Not by themselves. Backups matter only if restore tests are part of your routine.
Follow on your preferred channel for new articles, notes, and experiments.