Installing Proxmox VE 9 on Debian 13 “Trixie” for Your Home Lab

Direct Answer

You can install Proxmox VE 9 on Debian 13 “Trixie” by starting with a minimal Debian server, giving it a static address and fully qualified hostname, adding the Proxmox Trixie repository and signing key, installing the Proxmox kernel, then installing proxmox-ve, postfix, open-iscsi, and chrony. After reboot, manage the host at https://your-host:8006.

Why Install on Debian Instead of the ISO?

The Proxmox ISO is usually easiest, especially for a fresh machine. Installing on Debian is useful when you need more control over partitioning, firmware, remote console workflows, or a provider that only offers Debian images. Home lab builders also choose this path when repurposing an existing Debian box, standardizing automation, or learning exactly what Proxmox adds.

Do not use it to “upgrade” a messy workstation. Treat the host as infrastructure: simple, documented, and easy to rebuild.

Prerequisites and Hardware Notes

• A 64-bit CPU with virtualization extensions enabled in firmware.
• Enough RAM for Proxmox plus guests; 16 GB is a practical lab starting point.
• Reliable SSD or NVMe storage; mirrored disks are better for always-on labs.
• One Ethernet interface, preferably wired, with switch access for VLAN experiments.
• Console access, because network mistakes can temporarily lock you out.

Before installing, update your router reservation plan and decide the host name, domain, gateway, DNS servers, and bridge address. Proxmox is sensitive to hostname consistency, so avoid changing it casually later.

Install a Minimal Debian 13 System

Use the Debian 13 netinst or your normal unattended method. Select SSH server and standard system utilities only; skip desktop environments. Use simple partitions unless you already know you want ZFS, LVM, or separate boot disks.

After reboot, log in as root or use sudo consistently. A clean package state reduces confusing dependency errors.

Set a Static IP and Correct Hostname

Proxmox expects a stable management address. In Debian, configure your interface or bridge using your preferred networking method, then verify /etc/hostname and /etc/hosts. Example values below use pve1.lab.example and 192.168.10.20.

Confirm name resolution returns the management IP, not 127.0.1.1. If it does not, fix it before continuing.

Add the Proxmox VE 9 Repository and Key

The official Proxmox instructions for Trixie use the Proxmox no-subscription repository for community labs. Production systems should evaluate subscription repositories, but most home labs start here.

This is modified from the Proxmox Offiical Documentation. During installation testing I ran into problems. and made corrections based on the community suggestions.

Echo in the Sources for the PVE Install Repository.

cat > /etc/apt/sources.list.d/pve-install-repo.sources << EOL
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOL

Download the Keys for the repository.

Update the Repositories to use the Modern sources.

And finally update the software and perform a Distribution Upgrade.

If apt reports signature or suite errors, stop and compare your commands with the official wiki before forcing anything.

Install the Proxmox Kernel and Packages

Install the Proxmox kernel first, reboot into it, then install the main stack. This keeps troubleshooting clear if the machine has unusual storage or network hardware.

During Postfix setup, “local only” is fine for many labs unless you plan to send alerts through a relay. Open-iSCSI supports shared storage scenarios, and chrony keeps cluster time accurate.

Access the Proxmox Web UI

Browse to the management address on port 8006:

Accept the self-signed certificate warning, then sign in as root using PAM authentication. Immediately check node status, repositories, updates, DNS, and time. If the web UI does not load, test ping, SSH, firewall rules, and whether pveproxy is running.

Optional Cleanup: Remove the Debian Kernel

After confirming the Proxmox kernel boots reliably, you may remove the standard Debian kernel to avoid accidental boot selection. Keep at least one known-good Proxmox kernel available.

Reboot once more and verify the selected kernel with uname -r.

Home Lab Post-Install Tips

• Create storage intentionally: directory storage is simple, LVM is flexible, and ZFS is excellent when you understand memory and disk requirements.
• Schedule backups before building important VMs. Test a restore, not just a backup job.
• Use VLAN-aware bridges when your switch and router support tagged networks.
• Document VM IDs, IPs, storage pools, and pass-through devices in a simple notes file.
• Common workloads include Home Assistant, Pi-hole, Linux test servers, Kubernetes nodes, NAS services, and Windows evaluation VMs.

Quick Troubleshooting Checks

If networking breaks after bridge changes, use local console access and inspect /etc/network/interfaces, ip addr, and journalctl -xe. If package installation fails, remove unrelated third-party repositories and run apt update again. For clustering, confirm all nodes have unique hostnames, synchronized time, and reliable DNS or hosts-file entries.

References

Reference: Based on Proxmox’s official Debian 13 Trixie installation documentation: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie. Next, create one test VM and verify backups before migrating services to this host.