Back to blog
GuidesNovember 20, 2026·8 min read

How to Install Proxmox VE on a Bare Metal Server

How to Install Proxmox VE on a Bare Metal Server

You can install Proxmox on a bare metal server in two ways: boot the official ISO installer, or put Debian 13 on the machine first and add Proxmox VE afterwards. For a Proxmox bare metal setup on a rented dedicated server, the Debian route is often the easier one, since you can order the server with Debian ready to go and do the rest over SSH. Both methods are covered below, followed by the two things that catch most people out on hosted servers: package repositories and VM networking.

The latest version is Proxmox VE 9.2, released on 21 May 2026. It is based on Debian 13 "trixie" and uses the 7.0 kernel by default.

What you need

Proxmox VE will install on nearly any x86 server, but a few points decide how well it runs:

  • CPU: 64-bit Intel or AMD with hardware virtualization (Intel VT or AMD-V) enabled in the BIOS. AMD EPYC and other server chips include it.

  • Memory: the official guidance is 2GB or more for Proxmox and its services, plus everything assigned to guests. ZFS and Ceph want roughly 1GB of additional RAM for each TB of storage.

  • Storage: SSDs perform best. Proxmox favours drives with power loss protection and steers people away from consumer SSDs.

  • No hardware RAID under ZFS. A hardware RAID controller is incompatible with both ZFS and Ceph; pass the disks through untouched.

  • Console access. The ISO method needs the server's screen, and when the network config goes wrong it's your way back in. Dedicated servers provide that through IPMI/KVM.

Method 1: install Proxmox from the ISO

Go this way if the server's IPMI/KVM console can present an ISO image as virtual media, or if a USB stick can be plugged in and booted.

  1. Get the installer. The Proxmox website offers the Proxmox VE 9.2 ISO installer for download; compare its SHA256 checksum with the published one.

  2. Boot from it. Load the ISO through the IPMI/KVM virtual media feature, start the machine from that drive, and pick "Install Proxmox VE (Graphical)" in the menu.

  3. Select where it goes. Out of the box the filesystem is ext4 on LVM; the Options button lets you switch to ZFS, such as a ZFS RAID1 mirror over two disks. Be aware that the installer wipes the entire target disk by default.

  4. Check region settings. Country, time zone and keyboard are filled in for you, and the country also picks the download mirror.

  5. Choose credentials. Proxmox wants a root password of 8 characters or more and suggests at least 12, plus an email address for alerts from the system.

  6. Fill in the management network. Select the interface, enter a fully qualified hostname like pve1.example.com, and type in the IP address, gateway and DNS server your provider assigned, without changes. Only one of IPv4 or IPv6 can be set here; the second family can be added once Proxmox is running.

  7. Let it install, then restart. Eject the virtual ISO first so the machine boots from disk.

When it's back up, visit https://your-server-ip:8006 and log in with root and the realm "Linux PAM".

Method 2: install Proxmox on top of Debian 13

Take this route when the server comes with Debian 13 already installed, or when you want your own partition layout. Proxmox prefers the ISO where it's an option, but this method is officially documented. Run all commands as root over SSH.

1. Make the hostname resolve to the server's IP

The hostname has to resolve to the server's public IP rather than 127.0.1.1. Add a line like the one below to /etc/hosts, using your own IP and names:

203.0.113.10   pve1.example.com pve1

Check it:

hostname --ip-address

It must print the server's IP address.

2. Add the Proxmox VE 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

wget https://enterprise.proxmox.com/debian/proxmox-archive-keyring-trixie.gpg \
  -O /usr/share/keyrings/proxmox-archive-keyring.gpg
sha256sum /usr/share/keyrings/proxmox-archive-keyring.gpg

The checksum must be 136673be77aba35dcce385b28737689ad64fd785a797e57897589aed08db6e45.

3. Update and install the Proxmox kernel

apt update && apt full-upgrade
apt install proxmox-default-kernel
systemctl reboot

4. Install the Proxmox VE packages

apt install proxmox-ve postfix open-iscsi chrony

Postfix will ask how mail should be handled. Pick "Local only" unless you have a relay to send through.

5. Remove the Debian kernel and os-prober

apt remove linux-image-amd64 'linux-image-6.12*'
update-grub
apt remove os-prober

Proxmox's guide says the Debian kernel has to go, so that the server always starts the Proxmox kernel. Reboot again, then sign in at https://your-server-ip:8006 as root with the realm "Linux PAM".

On a Debian-based install, check that ifupdown2 is present as well, since Proxmox relies on it to apply network changes:

apt install ifupdown2

Set up the package repositories

An ISO install has the enterprise repository switched on, and that repository needs a paid subscription key. Without a key, apt update errors out on it. There are two ways forward:

  • Buy a subscription and add the key. For production servers, Proxmox recommends the enterprise repository.

  • Switch to the no-subscription repository. Put Enabled: no in the entry inside /etc/apt/sources.list.d/pve-enterprise.sources, then add the pve-no-subscription repository the way Method 2 does. Proxmox doesn't recommend this repository for production.

After a Debian-based install, remove the temporary /etc/apt/sources.list.d/pve-install-repo.sources file once your final repositories are configured, so the same repository doesn't appear twice.

Networking for VMs on a hosted server

Rented servers trip up here more than anywhere else. At home, VMs share a bridge (vmbr0) with the physical network card, and every VM appears on the network with a MAC address of its own. Proxmox's documentation warns that most hosting providers cut off networking once they see several MAC addresses on one interface. Find out what your provider supports before you start any VMs. Proxmox documents three setups:

SetupWhen to use itHow VMs reach the internet
BridgedYour provider allows extra MAC addresses, or lets you register themEach VM uses its own public IP directly
RoutedYour provider routes an extra IP block to your serverThe host routes traffic for the VMs' public IPs
Masquerading (NAT)You have a single public IPVMs use private IPs and share the host's IP; forward ports for inbound traffic

If you only have one IP address, start with NAT. Add a private bridge to /etc/network/interfaces, and replace eno1 with the name of your server's network interface:

auto vmbr0
iface vmbr0 inet static
    address 10.10.10.1/24
    bridge-ports none
    bridge-stp off
    bridge-fd 0
    post-up   echo 1 > /proc/sys/net/ipv4/ip_forward
    post-up   iptables -t nat -A POSTROUTING -s '10.10.10.0/24' -o eno1 -j MASQUERADE
    post-down iptables -t nat -D POSTROUTING -s '10.10.10.0/24' -o eno1 -j MASQUERADE

Load the change with ifreload -a, then give each VM an address in 10.10.10.0/24 and set 10.10.10.1 as its gateway. Keep the IPMI/KVM console open while you work on networking, so one typo can't lock you out.

Secure the web interface

Anyone who reaches port 8006 can control the host and all of its VMs. Don't expose it to the whole internet: in the Proxmox firewall, allow it only from your own IP addresses, or connect through an SSH tunnel or a VPN. Also enable two-factor authentication for root under Datacenter, Permissions, Two Factor.

Pick the right server for Proxmox

Cores, memory and storage speed count for more on a hypervisor than raw clock speed. The OrbitServers EPYC 7763 server pairs 64 cores at 2.45GHz with 512GB ECC RAM and 2×4TB NVMe + 2×480GB NVMe, costs $799.99/mo in Frankfurt and handles 50+ VMs. You get one IPv4 address with it; more cost $2.50 per IP, and a /64 IPv6 subnet is available. On top of that, any bare metal server of ours includes IPMI/KVM and full root access. Other builds are on the virtualization servers page, and for just a handful of VMs without Proxmox, our walkthrough on installing KVM on Ubuntu may be enough.

Troubleshooting

  • "hostname --ip-address" shows 127.0.1.1. Your hosts file is wrong. Edit /etc/hosts as in step 1, and only then install proxmox-ve.

  • Name resolution fails after installing. Two packages, resolvconf and rdnssd, are known to rewrite /etc/resolv.conf. Take them off and put your DNS servers back.

  • Boot stops at "bad shim signature". Secure Boot is getting in the way; switch it off in the firmware.

  • Guests have no connectivity on a hosted server. Extra MAC addresses are probably being filtered upstream. Use the routed or NAT model instead.

  • A 401 error during "apt update". That's the enterprise repository without a subscription key behind it. Disable it or buy a key.

Frequently asked questions

Is Proxmox free?

Yes. Proxmox VE is open source and costs nothing to use. A paid subscription adds the enterprise repository and support.

Can I install Proxmox on a rented dedicated server?

Yes. Boot the installer through IPMI/KVM, or have the machine delivered with Debian 13 and layer Proxmox onto it. Before the first VM, clarify with the provider how additional IPs and MACs work.

How much RAM does Proxmox need?

Plan on at least 2GB for Proxmox, plus the memory for every VM and container. If you use ZFS, add about 1GB per TB of storage.

Should I use ZFS or ext4 for Proxmox?

ZFS brings snapshots, checksums and software RAID across disks, but it uses more RAM. Go with ext4 on LVM for a simple one-disk server, and pick ZFS when you have at least two disks and memory to spare.

Get started with Orbit Servers

Low-latency VPS, bare metal, and colocation across the US, EU, and APAC - provisioned instantly and built for performance-critical workloads.

Get started
Julius

Written by

Julius

Product Manager

Julius is a product-minded builder who cares about making technology simpler and more useful for the people who rely on it. He’s always looking for ways to improve things, one small step at a time, and enjoys turning good ideas into products that work.

Related posts