Before you start
- Proxmox VE installed and reachable at https://IP:8006 (see installing Proxmox VE step by step)
- The root account's password
- Internet access from the server
In plain words
Once Proxmox VE is installed, the house is built but not yet ready to live in: the system fetches its updates from an address reserved for subscribers, everyone comes in with the owner's key (root), no alarm is connected and nothing is backed up. This guide goes through, in order, the settings to make before creating your first virtual machines. Allow about three quarters of an hour.
The plan
| Step | Why | Time |
|---|---|---|
| 1. Update repositories | Without a subscription, the default repository returns an error: no updates arrive | 5 min |
| 2. System update | Fix the vulnerabilities and bugs published since the ISO was released | 5 to 15 min |
| 3. Named administrator account | Stop working as root day to day |
5 min |
| 4. Two-factor authentication | Protect access to the whole server | 5 min |
| 5. Firewall | Filter access to the interface and the VMs | 10 min |
| 6. Notifications | Be told about backup failures and faults | 5 min |
| 7. ISOs and templates | Have what you need to create VMs and containers | 5 min |
| 8. Backups | Be able to roll back | 10 min |
1. Choose the update repository
Proxmox VE offers several package repositories:
| Repository | For whom | Note |
|---|---|---|
| pve-enterprise | Servers with a subscription | Enabled by default; without a subscription, apt update returns a 401 Unauthorized error |
| pve-no-subscription | Homelab, testing, use without a subscription | Free; updates slightly less battle-tested than "enterprise". Proxmox advises against it in production |
| pve-test | Testing future versions | Never on a machine you depend on |
Without a subscription, disable the enterprise repository and add the no-subscription repository.
Through the web interface
- Select the server (
pve1) in the tree, then Updates > Repositories. - Select the pve-enterprise line, then click Disable.
- If there's a ceph line with the
enterprisecomponent, disable it too. - Click Add, choose No-Subscription, then Add.
The panel should state at the top that updates are available from a no-subscription repository.
Or on the command line
Proxmox VE 9 is based on Debian 13 and uses the deb822 repository format (.sources files). Open Shell on the server.
Disable the enterprise repository:
echo "Enabled: no" >> /etc/apt/sources.list.d/pve-enterprise.sources
Create the no-subscription repository file:
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
EOF
If the file /etc/apt/sources.list.d/ceph.sources exists and points to enterprise.proxmox.com, add the line Enabled: no to it as well.
Why http and not https?
The packages are signed: apt checks their signature with the key named on the Signed-By line. A package modified in transit would be rejected, even downloaded over HTTP.
2. Update the system
In the interface: Updates > Refresh, then Upgrade (a console opens). Or in the Shell:
apt update
apt full-upgrade
Always full-upgrade, never apt upgrade
Proxmox's documentation is explicit: apt upgrade can leave the system partially updated, because it refuses to add or remove packages. apt full-upgrade (or the equivalent apt dist-upgrade) resolves dependencies correctly.
If the update installs a new kernel, restart (the Reboot button at the top right, on the server). Then check the versions:
pveversion
While you're at it, install the processor fixes (microcode), which correct hardware vulnerabilities. Debian's non-free-firmware component, which they need, is enabled by default on Proxmox VE 9:
apt install intel-microcode
Or, for an AMD processor:
apt install amd64-microcode
Restart after installing.
3. Create a named administrator account
Working as root day to day is like using the master key for everything: the slightest mistake or password leak gives everything away. Create an account in your name and keep root for emergencies.
Proxmox offers two authentication realms:
| Realm | Where the account lives | Access to the Linux Shell and SSH |
|---|---|---|
Linux PAM (@pam) |
Linux account on the server | Yes, with its Linux rights |
Proxmox VE (@pve) |
Proxmox's own user database, specific to the cluster | No: web interface and API only |
To manage VMs from the web interface, a @pve account is enough and exposes the system less. It's the recommended choice.
Through the web interface
- Datacenter > Permissions > Groups > Create: name
admins. - Datacenter > Permissions > Users > Add:
- User name:
spo - Realm: Proxmox VE authentication server
- Group:
admins - Password: a long password, different from
root's - E-Mail: your address
- User name:
- Datacenter > Permissions > Add > Group Permission:
- Path:
/(the whole datacenter) - Group:
admins - Role: Administrator
- Path:
Or on the command line
pveum group add admins --comment "Administrators"
pveum acl modify / --groups admins --roles Administrator
pveum user add spo@pve --groups admins --email spo@example.com
pveum passwd spo@pve
Log out, then log back in with the user spo, realm Proxmox VE authentication server.
| Predefined role | Rights | For whom |
|---|---|---|
| Administrator | Everything | You, to administer the server |
| PVEAdmin | Almost everything, except some system settings | A delegated administrator |
| PVEVMAdmin | Full management of VMs | Someone who manages their VMs without touching the server |
| PVEVMUser | Using VMs: console, start, stop | A VM user |
| PVEAuditor | Read-only | Monitoring, viewing |
To give limited rights to a single VM, set the Path to /vms/100 (100 being the VM's number).
4. Enable two-factor authentication
Enable it at least for root@pam and for your administrator account.
- Logged in with the account concerned, click its name at the top right, then TFA (or Datacenter > Permissions > Two Factor > Add).
- Choose TOTP: scan the QR code with an authenticator app (Ente Auth, Aegis, or the one in your password manager), then enter the code shown to confirm.
- Add Recovery Keys: print them or keep them in your password manager.
WebAuthn (physical security key, such as a YubiKey) is also available; it requires the interface to be reached by a domain name with a valid certificate, set in Datacenter > Options > WebAuthn Settings.
Keep an emergency exit
If you lose the phone and the recovery keys for root@pam, you'll need console access to the server (screen and keyboard) to remove two-factor authentication. Test logging in with two-factor authentication in a private browsing window before closing your current session.
5. Enable the firewall
The Proxmox VE firewall works at three levels: datacenter (common rules), server (node) and VM or container. It is disabled by default.
- Datacenter > Firewall > Options: check that Input Policy =
DROP(block whatever isn't allowed). - Datacenter > Firewall > Add, to explicitly allow administration from your local network:
| Direction | Action | Source | Protocol | Destination port | Comment |
|---|---|---|---|---|---|
| in | ACCEPT | 192.168.1.0/24 |
tcp | 8006 |
Web interface |
| in | ACCEPT | 192.168.1.0/24 |
tcp | 22 |
SSH |
| in | ACCEPT | 192.168.1.0/24 |
icmp | Ping |
- Only then: Datacenter > Firewall > Options > Firewall = Yes.
Proxmox allows the web interface and SSH from the server's local network anyway, so you don't lock yourself out; explicit rules make the policy readable and serve as a basis if you later restrict the source (for example to a single administration computer or a dedicated VLAN).
The VM firewall is separate
Enabling the firewall at datacenter level does not filter the VMs' traffic. To filter a VM, enable Firewall on its network card (Hardware tab, Firewall box ticked by default) and in the VM's Firewall > Options tab, then add its rules.
Check the status from the Shell:
pve-firewall status
Status: enabled/running
6. Configure notifications
Proxmox sends notifications for backups, available updates, replication and disk failures. By default, they go out through sendmail to the address of root@pam, which often fails: most email providers reject messages sent directly by a home server.
- Check the address of
root@pam: Datacenter > Permissions > Users, double-clickroot, E-Mail field. - Datacenter > Notifications > Add > SMTP:
| Field | Example |
|---|---|
| Endpoint Name | smtp-alerts |
| Server | Your email provider's SMTP server, for example smtp.example.com |
| Encryption | TLS (port 465) or STARTTLS (port 587) |
| Authenticate | Ticked, with the sending account's username and password (preferably an app password) |
| From Address | pve1@example.com or the sending account's address |
| Recipient(s) | root@pam (and possibly other users) |
- Select the new target, then Test. Check that it arrives.
- In Notification Matchers, edit
default-matcherso that it sends tosmtp-alerts.
Other targets exist: Gotify, Webhook (for ntfy, Discord, Slack, Teams…), useful if you don't want to depend on email.
7. Prepare ISO images and container templates
The local storage holds ISO images, container templates and, by default, backups.
Add an ISO image
local > ISO Images, then:
- Upload to send an ISO from your computer;
- Download from URL to have the server download it itself: paste the ISO's address, click Query URL, then enter the SHA-256 checksum published by the vendor (Advanced) to verify it.
Download LXC container templates
local > CT Templates > Templates: the list of official templates (Debian, Ubuntu, Alpine, Rocky, etc.). Or on the command line:
pveam update
pveam available --section system
pveam download local debian-13-standard_13.1-2_amd64.tar.zst
Replace the template name with the one shown by pveam available, as versions change regularly.
8. Schedule the first backups
A backup stored on the same disk as the VMs only protects against mistakes: if the disk dies, everything disappears. For real protection, back up to another medium: a second disk, an NFS or SMB share on a NAS, or better, a Proxmox Backup Server (open source, with deduplication and encryption).
Add a backup storage (example: NFS share on a NAS)
Datacenter > Storage > Add > NFS:
| Field | Example |
|---|---|
| ID | nas-backups |
| Server | 192.168.1.20 |
| Export | /volume1/proxmox (chosen from the list) |
| Content | Backup |
Create the backup job
Datacenter > Backup > Add:
| Tab / field | Recommended value |
|---|---|
| Storage | nas-backups |
| Schedule | 21:00 or mon..sat 02:30 (Proxmox calendar format) |
| Selection mode | All: every VM and container, including those created later |
| Mode | Snapshot: backup without stopping the VM |
| Compression | ZSTD: fast and efficient |
| Notification | Always, or only on failure |
| Retention | For example Keep Daily 7, Keep Weekly 4, Keep Monthly 3 |
Once the job is created, select it and click Run now for a first try. Then test a restore: a backup that has never been restored is only a hope. For the overall strategy, see the 3-2-1 rule.
Install the guest agent in your VMs
With the QEMU Guest Agent installed in the VM (qemu-guest-agent package on Linux, VirtIO drivers on Windows) and enabled in Options > QEMU Guest Agent, Proxmox cleanly freezes the VM's files during backup and shows its IP address.
9. What about "post-install" scripts?
Community scripts automate some of these settings in a single command, and often offer to hide the No valid subscription window.
Read before running
A script run as root on the hypervisor can do anything. If you use one, read it, prefer well-known, maintained projects, and be aware that interface changes (such as removing the subscription window) are overwritten every time the package concerned is updated. Making the settings by hand, as above, also helps you understand your server.
10. Final check
| Check | How | Expected result |
|---|---|---|
| Updates | Updates > Refresh | No 401 error, empty list after updating |
| Version | pveversion |
Up-to-date 9.x version |
| Time | chronyc tracking |
Leap status : Normal, offset of a few milliseconds |
| Named account | Log in with spo@pve and the TOTP code |
Full access |
| Firewall | pve-firewall status |
enabled/running |
| Notifications | Test on the SMTP target | Email received |
| Backup | Run now then a test restore | Job OK, restored VM that boots |
Key points
- Without a subscription: disable
pve-enterprise, addpve-no-subscription, thenapt updateandapt full-upgrade. - Create a named account (
spo@pve, Administrator role) and enable two-factor authentication with recovery keys. - Add the firewall rules before enabling it; the VMs' firewall is set separately.
- Set up an SMTP target and test it: an alert that never arrives is useless.
- Back up to a medium other than the VMs' disk, and test a restore.