Proxmox: The OS You Put on Your Homelab Servers
A practical walkthrough of installing Proxmox VE on a home server and running your first virtual machines — Ubuntu Server, Nextcloud, and a self-hosted AI agent — without exposing anything to the public internet.
The first decision in building a homelab is not which service to run. It is what sits underneath all of them. Install a hypervisor first and every later project becomes a virtual machine you can snapshot, break, and rebuild without touching the host.
This is the walkthrough Rob Braxman gives in his video: a Dell PowerEdge R640 1U server as the target, a Dell XPS 13 as the machine used to prepare installation media, and Proxmox Virtual Environment as the layer everything else runs on. The same steps work on a spare desktop or a laptop if you are not ready for rack hardware.
Why a hypervisor instead of just installing Linux
A plain Linux install gives you one operating system to maintain. A hypervisor gives you many, isolated from each other and from the host. That has three practical consequences:
- Containment. A misconfigured Nextcloud instance cannot take down your DNS resolver or your AI agent.
- Snapshots before upgrades. Take a snapshot, upgrade, roll back in seconds if it breaks.
- Rebuilds instead of repairs. A VM that gets messy can be deleted and recreated from a template.
Proxmox VE is a Debian-based distribution that bundles KVM virtual machines, LXC containers, and a browser-based management interface. It is free to use, and the whole thing is administered from another device.
What you need
- An x86-64 machine with virtualization enabled in the BIOS/UEFI, wired to your network.
- A USB stick you do not mind erasing (8 GB is plenty).
- A second computer to write the installer.
- A static IP address reserved for the host, either on the router or configured during install.
- Optionally, a monitor and keyboard for the initial install. After that you will not need them.
A wired connection matters more than it sounds. Proxmox's management interface is a web app, and installing over Wi-Fi is a common source of first-boot confusion.
Step 1: Write the installer
Download the Proxmox VE ISO from proxmox.com, then write it to the USB stick. On Linux or macOS:
sudo dd if=proxmox-ve_*.iso of=/dev/sdX bs=4M status=progress oflag=sync
Replace /dev/sdX with the USB device — check carefully with lsblk, because dd does not ask for confirmation. A graphical writer such as balenaEtcher works equally well.
Step 2: Install Proxmox VE
Boot the server from the USB stick and choose Install Proxmox VE (Graphical). The installer is short:
- Accept the license agreement.
- Choose the target disk. This erases the disk; on a used server, confirm there is nothing on it you need.
- Set country, time zone, and keyboard layout.
- Set the root password and a notification email address.
- Configure the management interface: hostname as a fully qualified name such as
pve.home.arpa, the static IP in CIDR form (for example192.168.1.50/24), gateway, and DNS server.
Then reboot and remove the USB stick. The host is now reachable at https://<ip>:8006 from any browser on your network. Log in as root with the password you set.
Two notes that save time later. The certificate is self-signed, so the browser will warn you — that is expected. And if you are not buying a subscription, the interface shows a subscription nag and updates come from the no-subscription repository; both are normal for homelab use.
Step 3: Create your first VM
Before creating a VM you need an operating system image. Upload the Ubuntu Server ISO to the host's local storage under ISO Images, either through the web interface or by copying it to /var/lib/vz/template/iso/ over SCP.
Then:
- Click Create VM, give it a name, and select the Ubuntu ISO.
- Set the guest OS type to Linux with the 6.x kernel.
- Give it a disk — 32 GB is a reasonable starting point for a general-purpose VM.
- Allocate 2 CPU cores and 2–4 GB of RAM.
- Attach the network to the default bridge,
vmbr0. - Start the VM and open its console to run the Ubuntu installer.
Inside the Ubuntu installer, enable OpenSSH server when offered. It is one checkbox and it saves you from console-only administration forever.
One detail worth knowing: after installation, remove the ISO from the VM's hardware list. If the VM still has the installer attached and the boot order prefers it, the machine will boot the installer again instead of the disk you just installed to.
Step 4: Reach it safely with Tailscale
The temptation is to forward a port on the router so you can reach Proxmox and your VMs from anywhere. Do not. The management interface on port 8006 is exactly the kind of service that gets found by scanners within hours.
Install Tailscale inside the VM (and optionally on the Proxmox host), authenticate it, and use the 100.x tailnet address to connect. You get remote access from any of your devices, and nothing is exposed to the public internet. If you later need to share a service with someone outside your tailnet, use Tailscale's sharing features rather than opening a port.
Step 5: First services
With a working VM and private networking, the homelab becomes a sequence of small projects. The two Braxman demonstrates are a good starting pair:
Nextcloud gives you file sync and sharing on hardware you control. The simplest reliable route on Ubuntu Server is the snap package, which bundles the web server, PHP, and database. Point a browser at the VM's Tailscale address and complete the setup wizard. Access over Tailscale means your files are never served directly from a public IP.
A self-hosted AI agent. The video installs Hermes, an agent that connects to a chat interface — in this case a Telegram bot created through BotFather. Installation is a single curl command, then you supply an API key from a model provider (Braxman uses Ollama). Once the bot token and model credentials are in place, you message the agent from your phone and it runs tasks on the server.
The follow-on demonstration is the useful one: telling the agent to install Home Assistant in a new VM. That is the real argument for a hypervisor. Provisioning a new service becomes a request, not an evening.
Homelab habits worth adopting early
- Snapshots are not backups. They live on the same disk. Back up VMs to separate storage on a schedule.
- Patch the host, not just the guests. Proxmox updates carry kernel and hypervisor fixes.
- One service per VM or container. It keeps failure domains small and rebuilds cheap.
- Label your IPs. Static addresses and a hosts file will save you more time than any dashboard.
- Monitor the things you cannot see. Disk health, SMART status, and backup success are the failures that hurt.
The point of the exercise
A homelab is a way to stop renting every capability. Files, automation, media, and now AI assistants can all run on hardware you own, behind a private network, with data that never leaves the house.
The trade is that you become the operator. That means watching for updates and outages, which is easier when the signals arrive as feeds rather than as things you remember to check. RSSFlux can turn vendor status pages and release notes into feeds that land in your reader or chat — see how it works.
Source: Proxmox - The OS You Put on Your Homelab Servers — Rob Braxman Tech.
Frequently asked questions
- Do I need a rack server to run Proxmox?
- No. Proxmox runs on any x86-64 machine with virtualization enabled in the firmware. A spare desktop, a small form-factor PC, or even a laptop works for learning. Rack hardware matters when you want ECC memory, multiple drives, and always-on reliability.
- Is Proxmox free?
- Proxmox VE is open source and free to use, including the enterprise repository if you buy a subscription. Without a subscription the web interface shows a nag screen, and updates come from the no-subscription repository instead.
- What is the first thing to install on a new Proxmox host?
- A general-purpose Linux VM you can reach over SSH, then a private network layer such as Tailscale so you can administer the host and its guests without opening ports to the internet.