Guide complet du serveur domestique pour débutants
De zéro à un serveur opérationnel : choisir le matériel, l'OS, déployer vos premières apps et tout sécuriser et sauvegarder.
This guide takes you from complete beginner to a working home server, one clear step at a time. No prior experience required, but you will get more out of it if you are comfortable following instructions in a terminal. Plan an afternoon for the first working setup and a few more evenings to harden and back it up.
A home server is simply a computer that stays on and provides services to the other devices in your home: file storage, media streaming, ad blocking, photo backup, smart home control and more. If you want the plain-English definition first, read What is a home server?.
Step 1: Decide what you want to run
Your goals determine everything else, so start with a short list. Pick one or two to begin, and add more later.
- A file server / NAS for documents, backups and shared folders.
- A media server (Plex or Jellyfin) for your movies, shows and music.
- Network-wide ad blocking with Pi-hole or AdGuard Home.
- A private cloud (Nextcloud, Immich) to replace Google Drive and Google Photos.
- Smart home control with Home Assistant.
A common mistake is buying hardware first and finding uses later. Doing it the other way around saves money and avoids a machine that is too weak or far too large.
Step 2: Choose your hardware
For most beginners, a mini PC with an Intel N100/N150 and 8–16 GB of RAM is the sweet spot: efficient, quiet and capable. A Raspberry Pi is enough for lighter tasks such as DNS filtering or a VPN. An old laptop is a great free way to learn, and its battery even acts as a small built-in UPS.
Things that matter more than raw speed:
- Idle power use, because the machine runs 24/7 (see how to reduce power consumption).
- Upgradeable RAM and storage.
- A wired Ethernet port. Avoid running a server on Wi-Fi.
- Quiet operation, if it will live in a living space.
Our in-depth hardware buying guide and best mini PCs explain each of these in detail.
Step 3: Pick an operating system
You do not need a special "server" operating system, but a few are designed for the job.
| Option | Best for | Learning curve |
|---|---|---|
| CasaOS / Umbrel | A graphical app store; the friendliest first choice | Low |
| Ubuntu Server / Debian | Flexibility and the widest documentation; pair with Docker | Medium |
| TrueNAS | Storage, ZFS and snapshots as the main goal | Medium |
| Proxmox VE | Running several virtual machines and containers | Medium to high |
If you are unsure, choose Ubuntu Server or Debian with Docker. Almost every tutorial on the internet works on it, and the skills transfer everywhere. Read how to choose a home server OS, and compare options like TrueNAS vs OpenMediaVault or Proxmox vs VMware.
Step 4: Install the operating system and give the server a fixed address
Write the installer to a USB stick, boot the machine from it and follow the prompts. Choose the minimal / SSH server options and enable the OpenSSH server so you can manage the machine remotely from your laptop instead of using a monitor.
Then give the server a stable address on your network so its services never move:
- Find the server's MAC address with
ip link. - In your router's settings, create a DHCP reservation that always assigns the same IP to that MAC address.
- Write the address down. Later guides assume you can reach
http://<server-ip>:<port>.
A reservation on the router is simpler and safer than configuring a static IP on the server itself. Our home server networking guide explains why.
Step 5: Install Docker
Docker is how you will run most apps. Each application lives in its own container, so installing, updating and removing things is clean and repeatable. Follow our tutorial to install Docker on Ubuntu, then learn the essentials in Docker basics and the Docker Compose best practices.
Step 6: Deploy your first app
Start with something rewarding and low-risk, like Pi-hole or a Jellyfin media server. Use Docker Compose so your setup is reproducible and easy to back up:
services:
jellyfin:
image: jellyfin/jellyfin
ports:
- "8096:8096"
volumes:
- ./config:/config
- /mnt/media:/media:ro
restart: unless-stoppedSave it as compose.yaml in its own folder, run docker compose up -d, then open the app in a browser. Keep each app in its own folder with its own Compose file so you can find and back up everything later.
Step 7: Access it safely from outside
You will eventually want to reach your services away from home. The safest approach is not to open ports on your router at all. Use a VPN such as Tailscale or WireGuard, which lets your phone and laptop reach the server as if they were at home. Read the secure remote access guide for the trade-offs.
If you later want clean names like media.home.example, add a reverse proxy such as Caddy or Nginx Proxy Manager.
Step 8: Secure it
Before you depend on the server, work through the security checklist. The highest-value basics are:
- Use SSH keys and turn off password logins.
- Keep the operating system and containers updated.
- Run a firewall and allow only what you need.
- Use strong, unique passwords and a password manager.
- Never expose admin panels to the internet.
Tools like Fail2ban add automatic protection against repeated login attempts.
Step 9: Back up everything
A server without backups is a loss waiting to happen. Follow the 3-2-1 rule: three copies of your data, on two different types of storage, with one copy offsite. A NAS or RAID array is not a backup, because it will faithfully mirror a deleted file or ransomware. See the backup strategy guide and test a restore at least once.
Step 10: Monitor and maintain
Once things work, keep them working. Set up Uptime Kuma to alert you when a service stops, and consider Grafana and Prometheus for graphs. A simple monthly routine is enough:
- Install operating system updates and reboot if needed.
- Pull new container images and recreate containers.
- Check disk health and free space.
- Confirm the last backup succeeded.
Common beginner mistakes
- Exposing services directly to the internet without a VPN or strong authentication.
- Using
latestimage tags everywhere and being surprised when an update breaks something. Pin versions for important apps. - Skipping backups because "it is just a hobby".
- Putting all data in container storage instead of mapped folders you can back up.
- Buying too much hardware before understanding your real workload.
You are up and running
From here, grow at your own pace: add apps, learn networking, build a media automation stack and explore the resource directory. Welcome to self-hosting.
Articles connexes
Guide de démarrage à l'auto-hébergement
Découvrez quels services cloud remplacer par des alternatives auto-hébergées et comment commencer.
Qu'est-ce qu'un serveur domestique ? Introduction simple
Une explication pour débutants : ce qu'est un serveur domestique, ce que vous pouvez en faire et comment décider si vous devez en construire un.
Nextcloud vs ownCloud
Comparez les deux forks cloud privé : fonctionnalités, apps, licences et lequel convient à votre homelab.