What is Proxmox VE?

Proxmox Virtual Environment (Proxmox VE) is an open-source 서버 virtualization platform that combines KVM-based virtual machines and LXC-based containers under a single web 인터페이스. Built on Debian Linux, it integrates enterprise 기능 such as live migration, high availability, software-defined storage, and a built-in firewall. Its agentless design and central management 인터페이스 make it a popular choice for homelabs, small businesses, and data centers alike.

The platform supports ZFS, Ceph, and LVM for storage, and includes a RESTful API for automation. The 설치 process is straightforward, but proper configuration immediately after setup is critical for a stable and secure environment.

Downloading the ISO and Creating 설치 Media

다운로드 the latest Proxmox VE ISO from the official Proxmox website. The ISO is a hybrid image that fits on a standard USB drive. Use a tool such as Rufus (Windows), Balena Etcher (cross-platform), or dd (Linux) to write the image.

# Linux: write ISO to USB drive (replace /dev/sdX with your device)
sudo dd if=proxmox-ve_*.iso of=/dev/sdX bs=1M status=progress

The ISO includes the Proxmox VE installer and a bootable Debian base system. On first boot, you are greeted by the installer menu with options for graphical or terminal-based 설치. The graphical installer is recommended for most users.

설치 Walkthrough

Partitioning

The installer presents several partitioning schemes. For most deployments, choose ext4 with LVM or ZFS if you want advanced 기능 such as snapshots, compression, and checksums.

ZFS is strongly recommended for the root filesystem if you have enough RAM (8 GB minimum). It enables instantaneous snapshots through the Proxmox backup mechanism and transparent compression with lz4.

네트워크 Configuration

Assign a static IP address during 설치. Do not rely on DHCP for a production 서버. The installer asks for the following:

• IP address (CIDR): e.g., 192.168.1.100/24
• Gateway: e.g., 192.168.1.1
• DNS 서버: e.g., 1.1.1.1 or your local DNS

Root 비밀번호 and Email

Set a strong root 비밀번호. Proxmox uses the root 계정 for web UI 인증 and SSH access. You also configure a system email address — this is where Proxmox sends alerts about hardware issues, backup failures, and certificate expiration.

First 로그인 to the Web UI

Once 설치 completes, reboot and note the IP address shown in the 콘솔. Open a browser and navigate to:

https://<YOUR_IP>:8006

Accept the self-signed certificate warning. Log in with username root and the 비밀번호 you set during 설치. The dashboard shows summary graphs for CPU, memory, 네트워크, and storage usage.

Removing the Enterprise Repository

Proxmox ships with the enterprise repository enabled by default, which requires a paid subscription to access. For non-production or homelab use, replace it with the no-subscription repository.

# Remove enterprise repo
rm /etc/apt/sources.list.d/pve-enterprise.list

# Add no-subscription repo
echo "deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription" > /etc/apt/sources.list.d/pve-no-subscription.list

Then 업데이트 the system:

apt update && apt full-upgrade -y

A pop-up about a missing subscription appears on 로그인. To suppress it:

sed -i 's/^/#/' /etc/apt/sources.list.d/ceph.list

System Updates and Kernel Management

Keeping Proxmox updated is essential for security and stability. The platform uses Proxmox-kernel (a custom kernel) rather than the stock Debian kernel. After updates, reboot to activate the new kernel.

apt update && apt dist-upgrade -y
reboot

Check the installed kernel 버전 with:

uname -r

Proxmox retains the previous kernel so you can boot into it if the new kernel causes issues. Use proxmox-boot-tool to manage kernel 버전.

네트워크 Bridge Configuration

Proxmox creates a bridge 인터페이스 vmbr0 during 설치. This bridge connects your VMs to the physical 네트워크. The configuration lives in /etc/network/interfaces.

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
    address 192.168.1.100/24
    gateway 192.168.1.1
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0

To add a second bridge for a separate 네트워크 (e.g., isolated lab 네트워크), duplicate the block with a different subnet and omit the bridge-ports line for an isolated bridge.

Hostname and DNS Configuration

Verify the hostname and /etc/hosts are correctly configured. Proxmox requires that the hostname resolves to the primary IP address.

# /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.1.100 proxmox.example.com proxmox

The file /etc/hostname should contain just the short hostname:

proxmox

Test 해상도 with:

hostname --ip-address

If this returns the wrong address, Proxmox services may fail to start.

Firewall Basics

Proxmox includes a built-in firewall managed through the web UI or via pve-firewall. Enable 데이터센터-level firewall first:

Datacenter → Firewall → Options → Enable: Yes

Then configure rules per node or per VM. At minimum, allow HTTPS (8006) and SSH (22) from your management 네트워크. The firewall is stateful and applies rules in order — place the most specific rules first.

Generate and apply firewall rules from the CLI as well:

pve-firewall compile
pve-firewall restart

Creating the First User

It is good practice not to use root for daily operations. Create a separate user with administrator privileges.

pveum user add admin@pve --password <password>
pveum acl modify / --user admin@pve --role Administrator

Log out of the root session and log in as the new user. Assign roles more granularly if needed — for example, create users with the PVEVMAdmin role who can only manage VMs.

Enabling Two-Factor 인증 for Admin

Proxmox supports TOTP-based two-factor 인증. Enable it in the web UI under 데이터센터 → Two-Factor 인증.

1. Select TOTP as the provider.
2. Scan the QR code with an authenticator app (Authy, Google Authenticator, or Bitwarden).
3. Enter the current code to verify setup.

For the root 계정, configure 2FA via the CLI if the web UI is inaccessible:

pveum user tfa add root@pam --type totp

Store the recovery codes printed during setup in a secure location. Without them, losing the authenticator device means losing access to the root 계정.

Backing Up /etc/pve

The directory /etc/pve is a special FUSE-backed filesystem that stores all Proxmox cluster configuration. It exists on every node but changes are synchronized cluster-wide. Regular backup of this directory is critical for disaster recovery.

tar czf /root/pve-backup-$(date +%Y%m%d).tar.gz /etc/pve

For a more structured approach, use proxmox-backup-client if you have a Proxmox Backup 서버. Otherwise, schedule a cron job:

0 3 * * * tar czf /root/pve-backup-$(date +\%Y\%m\%d).tar.gz /etc/pve

Test your backup by extracting it to a temporary directory and verifying the files are readable.

Post-Install Checklist

Run through this checklist after every Proxmox 설치:

• Enterprise repositories disabled, no-subscription repo enabled
• System fully upgraded
• Static IP confirmed in /etc/network/interfaces
• Hostname resolves correctly
• Firewall enabled with minimal allow rules
• Non-root admin user created
• Two-factor 인증 configured
• /etc/pve backup scheduled
• NTP time synchronization verified
• SSH key-based 인증 set up for root/admin