Install and Configure Proxmox VE on a Dedicated Server
Install Proxmox VE 9 on a dedicated server through the KVM IP: ISO, repositories, firewall, two-factor authentication, storage, first Linux VM, updates and backups.
On this page
Your values
Enter them once and the commands in this guide update.
This guide takes you from installing Proxmox VE on a dedicated server through to your first Linux virtual machine: mounting the ISO, package repositories, protecting the administration interface, two-factor authentication, storage, updates and backups.
Proxmox VE is an open-source hypervisor based on Debian. It brings together KVM virtual machines, LXC containers and a web administration interface. At the time of writing (November 2026), the current version is 9.2, based on Debian 13 "Trixie".
Order a Server
The HostMyServers website lists Proxmox VE among the virtualization solutions that can be used on Eco Dedicated Servers. These plans include KVM IP access and ISO mounting from the client area, two tools that are essential for this installation.
This guide is aimed at a dedicated server. Proxmox VE needs the processor's hardware virtualization extensions: for any other type of plan, first check with support, from your client area, that they are available.
Prerequisites
- A dedicated server with KVM IP access and ISO mounting from the client area
- The server's public IP address, netmask, gateway and DNS servers
- A recent browser and an SSH client on your computer
- Your computer's public IP address, to restrict access to the administration interface
- A TOTP app for two-factor authentication (FreeOTP or equivalent)
Required Configuration
| Component | Minimum (evaluation) | Recommended |
|---|---|---|
| Processor | 64-bit with Intel VT or AMD-V | 64-bit Intel or AMD with VT or AMD-V |
| Memory | 1 GB, plus what the VMs need | 2 GB for the system and services, plus what the VMs need |
| Storage | One disk | SSDs with power-loss protection, hardware RAID with a protected cache, or non-RAID disks for ZFS |
| Network | One network card | Several multi-gigabit cards, depending on your needs |
With ZFS, plan for more memory: the Proxmox documentation advises 4 GB plus 1 GB per TB of raw disk.
Ports Used
| Port | Protocol | Usage | Recommended exposure |
|---|---|---|---|
| 8006 | TCP | Web interface and API (HTTPS) | Your administration IPs only |
| 22 | TCP | SSH, including between cluster nodes | Your administration IPs and the nodes |
| 5900-5999 | TCP | VNC console | Your administration IPs only |
| 3128 | TCP | SPICE proxy | Your administration IPs only |
| 111 | UDP | rpcbind | Do not expose |
| 5405-5412 | UDP | Corosync (cluster) | Between nodes only |
| 60000-60050 | TCP | Live migration | Between nodes only |
| 25 | TCP (outbound) | Sending notifications through sendmail | Outbound only |
Step 1: Note the Current Configuration
If a system is still running on the server, connect over SSH and write down the following information. You will need it in the installer.
ip -br addr
ip route show default
cat /etc/resolv.conf
ip -br link
lsblk -o NAME,SIZE,TYPE,MODEL,ROTA
grep -c -E 'vmx|svm' /proc/cpuinfo| What to note | Where to find it |
|---|---|
IP address and prefix (for example /24) |
ip -br addr |
| Gateway | ip route show default, after via |
| Active network interface and its MAC address | ip -br addr and ip -br link |
| DNS server | /etc/resolv.conf |
| Available disks | lsblk |
The last command must return a number greater than 0. If it returns 0, virtualization is either missing or disabled in the BIOS.
Step 2: Download and Mount the ISO
-
Download the latest Proxmox VE ISO Installer image from the official page. The SHA256 checksum is published there.
-
If you download the image to your computer, verify it:
Terminalsha256sum proxmox-ve_9.2-1.iso -
In your client area, mount the ISO on the server, then open the KVM IP.
-
Restart the server and boot from the virtual drive. If the server does not boot from it, open the boot menu or the BIOS from the KVM console.
Step 3: Install Proxmox VE
In the boot menu, choose Install Proxmox VE (Graphical). If the display stays black or freezes in the KVM console, restart and pick Install Proxmox VE (Terminal UI), which offers the same options.
Then follow the wizard:
-
License: accept the agreement (EULA).
-
Target disk: select the disk. The Options button lets you choose the file system.
Choice When to use it VM storage created ext4 (default) or xfs General case, single disk or hardware RAID local-lvmZFS (RAID1, RAIDZ…) Several disks without hardware RAID, enough memory local-zfs -
Location: country, time zone and keyboard layout.
-
Password: choose a long, unique
rootpassword (at least 12 characters) and an email address for notifications. -
Network: check each field against the values from step 1. The installer suggests what it obtained through DHCP, which may be different.
Field Value Management Interface The active interface noted in step 1 Hostname (FQDN) A fully qualified name, for example pve1.your-domain.comIP Address (CIDR) SERVER_IP/prefixGateway The gateway you noted DNS Server The DNS server you noted -
Summary: review everything. Uncheck
Automatically reboot after successful installationso that you can unmount the ISO before the reboot. -
Start Install and wait for the copy to finish.
-
Unmount the ISO from the client area, then restart.
Step 4: First Login
From the KVM console or over SSH, check the network and the web service:
ip -br addr
ip route show default
hostname --ip-address
systemctl status pveproxy --no-pagerhostname --ip-address must return the server's IP, not 127.0.0.1 or 127.0.1.1.
Then open https://SERVER_IP:8006 and log in:
- User name:
root - Realm:
Linux PAM standard authentication - Password: the one chosen during installation
The browser warns about an unrecognized certificate: this is the self-signed certificate created during installation. The No valid subscription message is informational and does not prevent you from using Proxmox VE.
Step 5: Restrict Access to the Administration Interface
After installation, port 8006 responds on the public address. Protect it before creating your first VMs. The built-in firewall is disabled by default.
First, schedule the firewall to be disabled automatically in 10 minutes, in case you lose access:
systemd-run --on-active=10min --unit=fw-rollback /usr/sbin/pve-firewall stopThen edit the configuration file:
nano /etc/pve/firewall/cluster.fw[OPTIONS]
enable: 1
[ALIASES]
local_network SERVER_IP
[IPSET management]
YOUR_IP| Item | Purpose |
|---|---|
enable: 1 |
Enables the firewall: incoming traffic to the host is then blocked by default |
local_network |
Limits the "local network" to the server's IP. Without this, the entire detected public subnet would be treated as local and allowed |
management |
List of IPs allowed to reach the web interface, SSH, VNC and SPICE |
Check the configuration, then open a new SSH session and reload the web interface from your computer:
pve-firewall status
pve-firewall localnetIf everything works, cancel the scheduled deactivation:
systemctl stop fw-rollback.timerIf your public IP changes regularly, add the corresponding range to management, or go through a VPN with a fixed address. After any IP change you have not declared, only the KVM IP will let you correct the list.
Do not install ufw on the host: it would conflict with the Proxmox firewall.
Secure SSH
On your computer, copy your public key:
ssh-copy-id root@SERVER_IPOnce you have confirmed that key-based login works, stop allowing root to log in with a password:
sed -i 's/^#\?PermitRootLogin.*/PermitRootLogin prohibit-password/' /etc/ssh/sshd_config
sshd -t && systemctl reload sshStep 6: Configure the Repositories
A new installation enables the Enterprise repository, which is reserved for servers with a subscription. Without a key, apt update fails with a 401 Unauthorized error.
| Repository | Usage |
|---|---|
pve-enterprise |
Recommended for production, requires a Proxmox subscription |
pve-no-subscription |
Accessible without a key. Proxmox intends it for testing and non-production use, as its packages are less thoroughly tested |
pve-test |
Reserved for trying out new features, avoid it here |
With a subscription, enter the key in Node → Subscription and leave the repositories unchanged.
Without a subscription, go to Node → Updates → Repositories: disable the enterprise entries, then add No-Subscription with Add. The command-line equivalent is:
for f in /etc/apt/sources.list.d/pve-enterprise.sources /etc/apt/sources.list.d/ceph.sources; do
[ -f "$f" ] && sed -i '/^Types:/i Enabled: no' "$f"
done
cat > /etc/apt/sources.list.d/proxmox.sources <<'EOF'
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOFThen update the system:
apt update
apt full-upgradeRestart if a new kernel was installed, then check the versions:
pveversion
uname -rStep 7: Enable Two-Factor Authentication
- Open Datacenter → Permissions → Two Factor, then Add → TOTP.
- Select
root@pam, click Randomize and scan the QR code with your app. - Enter the displayed code in Verification Code and confirm with Apply.
- Then use Add → Recovery Keys and store these single-use keys outside the server, for example in a password manager.
- Test the login in a private browsing window before closing your session.
After 8 incorrect TOTP codes, the user's TOTP factors are disabled. A recovery key unlocks them. From the KVM console or SSH, you can also clear the lock:
pveum user tfa unlock root@pamCreate a Named Administrator Account
To avoid using root day to day, create a dedicated account, then enable two-factor authentication for it as well:
pveum user add admin@pve --comment "Administrator"
pveum passwd admin@pve
pveum acl modify / --users admin@pve --roles AdministratorThis account logs in with the Proxmox VE authentication server realm.
Step 8 (Optional): Let's Encrypt Certificate
A trusted certificate removes the browser warning and makes WebAuthn easier to use. You need a domain name whose A record points to the server.
The http-01 validation uses a built-in web server on port 80, which must then be reachable from the Internet. Add this section to /etc/pve/firewall/cluster.fw:
[RULES]
IN ACCEPT -p tcp -dport 80Register the account, then order the certificate:
pvenode acme account register default admin@your-domain.com
pvenode config set --acme domains=pve1.your-domain.com
pvenode acme cert orderThe first command asks you to choose a service. Start with Let's Encrypt V2 Staging to validate the procedure without risking Let's Encrypt's limits. Once this trial succeeds, replace the account and order the final certificate by choosing Let's Encrypt V2:
pvenode acme account deactivate default
pvenode acme account register default admin@your-domain.com
pvenode acme cert order --forceRenewal is then handled by pve-daily-update.service.
If you do not want to open port 80, use dns-01 validation from Datacenter → ACME, with your DNS provider's plugin.
Step 9: Understand and Extend Storage
Display the available storage:
pvesm status| Storage | Location | Content |
|---|---|---|
local |
/var/lib/vz |
ISOs, container templates, backups |
local-lvm |
LVM-Thin volume pve/data (ext4 or xfs installation) |
VM and container disks |
local-zfs |
rpool/data (ZFS installation) |
VM and container disks |
To use an additional empty disk:
- Locate it in Node → Disks.
- If it contains old data you no longer need, select it and click Wipe Disk. This action is irreversible: double-check the model and size.
- Open Node → Disks → LVM-Thin → Create: Thinpool, choose the disk, give it a name and leave Add Storage checked.
Step 10: Create a First Linux VM
Prepare the VM Network
Get the ISO
In local → ISO Images → Download from URL, paste the link to the netinst image given on the Debian page, click Query URL, then Download.
Create the VM
Click Create VM and fill in the wizard:
| Tab | Recommended setting |
|---|---|
| General | VM ID 100, name debian-test |
| OS | Debian ISO, type Linux, version 6.x - 2.6 Kernel |
| System | SCSI Controller: VirtIO SCSI single, Qemu Agent checked |
| Disks | Bus SCSI, storage local-lvm, 32 GB, Discard and IO thread checked |
| CPU | 1 socket, 2 cores, type x86-64-v2-AES |
| Memory | 2048 MB |
| Network | Bridge: vmbr1, Model: VirtIO (paravirtualized) |
The same VM can be created from the command line. Replace the ISO name with that of the downloaded file:
qm create 100 --name debian-test --ostype l26 \
--cpu x86-64-v2-AES --sockets 1 --cores 2 --memory 2048 \
--scsihw virtio-scsi-single \
--scsi0 local-lvm:32,iothread=1,discard=on \
--ide2 local:iso/debian-netinst.iso,media=cdrom \
--net0 virtio,bridge=vmbr1 \
--agent enabled=1 \
--boot 'order=scsi0;ide2'Start the VM, open its Console and install Debian. The private network has no DHCP by default: configure the address manually, for example 10.10.10.10/24, with 10.10.10.1 as the gateway.
Finalize the VM
Inside the VM, install the guest agent:
apt update
apt install -y qemu-guest-agent
systemctl start qemu-guest-agentOn the host, remove the ISO, enable automatic startup and check the agent:
qm set 100 --ide2 none,media=cdrom
qm set 100 --onboot 1
qm status 100
qm guest cmd 100 ping
qm guest cmd 100 network-get-interfacesFinally, remember to secure the VM's system with the Secure your server guide.
Verify the Installation
| Check | Expected result |
|---|---|
pveversion |
Version 9.x displayed |
pve-firewall status |
Status: enabled/running |
Access to https://SERVER_IP:8006 from an unauthorized IP |
Blocked, no response from the server |
Login as root |
TOTP code requested |
apt update |
No 401 error |
pvesm status |
Storage shown as active |
qm guest cmd 100 ping |
No error |
Updates
Apply updates regularly, from Node → Updates or over SSH:
apt update
apt full-upgradeAfter a kernel update, shut down the VMs cleanly or let the host do it, then restart during a planned window. Compare uname -r with the versions listed by pveversion -v.
For a major version change, do not just run an ordinary update: follow the upgrade guide published by Proxmox and its checker script, for example the one from version 8 to version 9. Make a full backup first.
Backups
For a one-off backup:
vzdump 100 --storage local --mode snapshot --compress zstdFor regular backups, create a job in Datacenter → Backup → Add, choosing the storage, schedule, VMs and retention.
HostMyServers offers a managed Proxmox Backup Server service, detailed in these guides:
Also back up the host configuration and copy the archive off the server. It contains secrets: store it securely.
tar czf /root/pve-config-$(date +%F).tar.gz /etc/pve /etc/network/interfaces /etc/hosts /etc/apt/sources.list.dTo check that a backup is usable, restore it from time to time under a new ID:
qmrestore /var/lib/vz/dump/BACKUP_NAME.vma.zst 900Install on an Existing Debian 13 System
The ISO method remains the simplest. Proxmox reserves installation on top of Debian for advanced users. It applies only to Debian 13: Proxmox VE 8, based on Debian 12, has not been maintained since August 2026, and Ubuntu is not a supported base. On Debian 12, first migrate to Debian 13 or reinstall with the ISO.
The hostname must point to an address other than the loopback. Adjust /etc/hosts, removing the hostname from the 127.0.1.1 line if there is one:
127.0.0.1 localhost
SERVER_IP pve1.your-domain.com pve1hostname --ip-addressAdd the repository and its key:
cat > /etc/apt/sources.list.d/pve-install-repo.sources <<'EOF'
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF
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.gpgThe expected fingerprint is 136673be77aba35dcce385b28737689ad64fd785a797e57897589aed08db6e45. Continue only if it matches.
Install the Proxmox kernel, then restart:
apt update && apt full-upgrade
apt install proxmox-default-kernel
systemctl rebootThen install Proxmox VE. For Postfix, choose local only if you do not have a mail relay:
apt install proxmox-ve postfix open-iscsi chrony
apt install ifupdown2
apt remove linux-image-amd64 'linux-image-6.12*'
update-grub
apt remove os-proberCheck that the server is still reachable, then leave the public interface as it is and create only a private bridge, as explained in the network guide. Then resume this guide from step 4. In step 6, the repository is already declared in pve-install-repo.sources: do not create proxmox.sources as well. With a subscription, delete this file after registering your key.
Troubleshooting
401 Unauthorized During apt update
The Enterprise repository is still active without a valid key. Disable it as described in step 6, or register your subscription.
The Web Interface No Longer Responds on Port 8006
From the KVM IP or SSH:
systemctl status pveproxy --no-pager
ss -tlnp | grep 8006
pve-firewall statusIf your IP is no longer in management, stop the firewall, correct /etc/pve/firewall/cluster.fw, then start it again:
pve-firewall stop
nano /etc/pve/firewall/cluster.fw
pve-firewall startNo Network Access After Installation
Open the KVM IP and check /etc/network/interfaces: address, prefix, gateway and the interface name in bridge-ports. Correct them, then apply with ifreload -a. If you do not know the right settings, contact support from your client area.
ipcc_send_rec[1] failed: Connection refused
The hostname probably does not resolve to the server's IP. Check /etc/hosts and hostname --ip-address, then restart the services or the server.
KVM virtualisation configured, but not available
The virtualization extensions are disabled or missing. Enable Intel VT-x or AMD-V (SVM) in the BIOS from the KVM IP. If the option is not accessible, contact support.
The Installer Hangs or Shows a Black Screen
Start it again with Install Proxmox VE (Terminal UI). If the problem persists, highlight this entry, press e, add nomodeset to the end of the line starting with linux, then boot with Ctrl-X. During installation, Ctrl+Alt+F2 displays detailed errors.
The Server Restarts into the Installer
The ISO is still mounted or comes before the disk in the boot order. Unmount it from the client area and check the boot order in the BIOS.
TOTP Code Rejected
Check the time on your phone and on the server with timedatectl. Use a recovery key, or unlock the account with pveum user tfa unlock root@pam. As a last resort, pveum user tfa delete root@pam removes its factors from the console.
storage 'local-lvm' does not exist
Your installation probably uses ZFS. Replace local-lvm with local-zfs, or with the name shown by pvesm status.
References
- Proxmox VE Administration Guide
- System Requirements
- Package Repositories
- Install Proxmox VE on Debian 13
- Proxmox VE Firewall
To go further: create a Windows VM and build a cluster.