PROPER INSTRUCTIONS

Turn an old laptop into a home server: proper instructions

An unused laptop is a capable first server: it includes a screen, storage, low-power hardware and a battery that can bridge a brief outage. It is not automatically reliable. A swollen battery is hazardous, Wi-Fi is a poor server uplink, and sleep or lid-close settings can make a host vanish. This guide creates a small Debian server for private LAN services. It deliberately does not publish anything to the internet.

Plan and prerequisites

Choose one initial job, such as an internal web app, media library or household file area. Do not begin by exposing SSH or an unfinished application. Back up all laptop files because installation erases the drive. Prefer a 64-bit machine with 4 GB RAM, a healthy SSD, a working charger, Ethernet and an 8 GB USB installer. Use a reputable USB-to-Gigabit-Ethernet adaptor if necessary.

Record the router address, LAN subnet, existing DNS servers and a name for this host.
Arrange a router login and another computer for downloading the Debian installer.
Plan a backup destination outside the laptop: another disk, another machine or encrypted off-site storage.
Use a hard, ventilated surface. Do not operate in a cupboard, on bedding or on fabric.

Prepare the hardware and network

Inspect the charger, casing and battery. If the battery is swollen, stop using it; have it professionally removed or recycled. Do not puncture it. A healthy battery is short-duration power protection, not a replacement for backups.
In firmware setup, temporarily enable USB boot. Set a firmware password if the laptop is in a shared location, and put the internal disk first in boot order after installation. Apply only manufacturer firmware updates that match the exact model.
Connect Ethernet. In the router, reserve an address for the laptop’s Ethernet MAC address and name it homeserver. A DHCP reservation is preferable to an unplanned static address because the router still supplies correct gateway and DNS details.
Keep a screen and keyboard available until remote access and restart behaviour have been tested. Leave the lid open initially; closed-lid operation must be verified rather than assumed.

Install Debian

Download the current Debian stable netinst image from the official Debian site and write it to USB with an imaging tool. Boot from it using Ethernet.
Select a minimal installation. Create an ordinary administrator account with a unique long password, and select the SSH server. Do not install a graphical desktop unless a service actually needs it.
Choose disk encryption knowingly. It protects a stolen device, but after a power outage a headless machine cannot boot until somebody enters the passphrase. For an unattended first server, this availability cost may outweigh the benefit; backups still need protection either way.

After first boot, update and restart:

sudo apt update
sudo apt full-upgrade
sudo reboot

Find the reserved address with the router or run
```
ip -br address
ip route
```
. From another LAN device, connect over SSH. Check the presented host-key fingerprint locally before accepting it:
```
ssh your-admin-user@SERVER_IP
```
.

Install one harmless test service, nginx:

sudo apt install nginx
sudo systemctl enable --now nginx
curl -I http://127.0.0.1

Test before relying on it

Verify routing and name resolution on the host:
```
ping -c 3 1.1.1.1
getent hosts deb.debian.org
```
.
From a different LAN device, open http://SERVER_IP/. Seeing nginx’s response proves local reachability only; it does not justify opening a router port.
Inspect expected listeners and services:
```
sudo ss -tulpn
systemctl --type=service --state=running
```
. Investigate any listener you did not deliberately install.
Reboot once, then repeat SSH and web checks. This catches services started only manually and missed network configuration.

Security and operations

Keep administration and services on the LAN. Do not create port-forwards or use a DMZ to get remote access. If remote access becomes necessary, use a maintained VPN or overlay VPN with named accounts and multi-factor authentication where supported. Use SSH keys; after successful key login in a second terminal, disable password SSH login in an SSH drop-in. Do not SSH as root. Patch Debian regularly and install only services that have a clear owner, storage path, update method and backup.

Back up application data and configuration outside the laptop, then restore a test file to a new location. A copy on the same internal disk is not a backup. Record the reserved address, services and recovery steps in a household note.

Rollback

To retire the test service, stop it, disable it and remove it only after copying any required data:

sudo systemctl disable --now nginx
sudo apt purge nginx nginx-common

. Remove the DHCP reservation only after checking no client depends on it. To retire the host, verify external backups, revoke its SSH keys and credentials, then erase the disk using a suitable installer or sanitisation process. If an update breaks networking, use the local console, check Ethernet and ip -br address, and undo the last intentional change rather than reinstalling before data is recovered.

Capacity and reliability checks

Before adding another application, measure ordinary behaviour for a few days. Check available space with

df -h
df -i

and look for recurring hardware or file-system warnings with

sudo journalctl -p warning --since "7 days ago"

Warnings need interpretation: a single failed Wi-Fi message does not matter on a wired server, while repeated disk I/O errors do. Check CPU temperature using the laptop’s supported sensor tooling if heat is a concern, and make sure the charger does not become excessively hot. Schedule a short maintenance period for updates and reboots. If the machine is unexpectedly noisy, hot or unstable, reduce workloads, copy current data to the external backup, and repair or replace the hardware rather than trying to conceal symptoms with software settings.