basforge

Search titles, text and the “If it doesn’t work” cases.

    RU

    Installing Proxmox VE 9: USB stick, installer, no-subscription repository and the first update

    Nine steps from ISO to a host ready for guests: write the USB stick, enable virtualization in the BIOS, install the system, connect the no-subscription repository, update, add an SSH key and check that notifications arrive. The installer wipes the selected disk completely.

    What you’ll end up with

    host      Proxmox VE 9.2 on Debian 13, kernel 7.0
    address   https://10.0.0.2:8006, login root, Realm — Linux PAM
    disk      ext4: local (ISOs, templates) and local-lvm (guest disks); or ZFS
    network   the vmbr0 bridge on the network card, guests on the home network
    packages  from pve-no-subscription, system up to date
    SSH       root — key only
    mail      notifications arrive: checked with the Test button

    Addresses in the example: home network 10.0.0.0/24, router 10.0.0.1, host 10.0.0.2. Substitute your own from the router settings. The host address is permanent and outside the range the router’s DHCP hands out, or one day the router will give it to a phone.

    You’ll need a USB stick of 2 GB or more, a monitor and keyboard for the install, and a cable from the host to the router or switch. Wi-Fi won’t do for the host: guests on a bridge over Wi-Fi are left without network (Proxmox networking).

    Steps

    1. Download the ISO and write the USB stick

      The Proxmox VE 9.2 ISO is on proxmox.com, under Downloads. Next to the file is its SHA256 sum; compare:

      sha256sum proxmox-ve_9.2-*.iso       # Linux
      certutil -hashfile proxmox-ve_9.2-1.iso SHA256      # Windows, use your file name

      Write the stick byte for byte. On Windows — balenaEtcher or Rufus: when asked about the write mode, pick DD. On Linux — dd; check the stick’s device name in lsblk twice, since dd will overwrite any disk:

      lsblk                                         # the stick — e.g. /dev/sdX, its size
      dd bs=1M conv=fdatasync if=./proxmox-ve_9.2-1.iso of=/dev/sdX
    2. Enable virtualization in the BIOS

      In the BIOS find Intel Virtualization Technology (VT-x), or SVM Mode on AMD, and enable it. In the same place, VT-d (IOMMU on AMD): without it you can’t pass a GPU or a disk controller into a VM. Boot mode — UEFI. Secure Boot can stay on: since 8.1 Proxmox boots with it.

      If the BIOS has a setting for what to do after power loss (Restore on AC Power Loss), set it to Power On: after a power cut the host comes back up by itself, and so do guests set to autostart.

    3. Pick the disk and file system

      Boot from the stick, pick Install Proxmox VE (Graphical), accept the license. On the Target Harddisk screen pick the disk for the system.

      The Options button sets the file system:

      • ext4 — the default. One disk, holding the host’s root and the local-lvm thin pool for guest disks.
      • zfs (RAID1) — if you have two identical disks: a mirror, and the host survives one of them dying. Here too is the ARC max size field — how much memory ZFS takes for its cache; the installer offers 10 % of memory, no more than 16 GiB.
      • zfs (RAID0) on one disk — ZFS snapshots and compression without a mirror.

      How they differ and what to pick — Proxmox storage. Leave the other Options fields (root, swap and pool sizes) as they are: the installer computes them from the disk size.

    4. Country, password and network

      Location and Time Zone — country, your own time zone, keyboard layout.

      Administration Password and Email — the root password and an email: Proxmox sends messages about backups and disk errors to it. Whether they arrive depends on outgoing mail, which we check in the last step. Make the root password long: it’s also the web UI login.

      Management Network Configuration:

      Field Example Why
      Management Interface enp1s0 the card the cable is plugged into; its MAC and link state are shown next to it
      Pin network interface names (since 9.1) on after install the card becomes nic0, and the name won’t change after a kernel update
      Hostname (FQDN) pve1.home.arpa host name and domain; without a domain of your own, use home.arpa, reserved for home networks
      IP Address (CIDR) 10.0.0.2/24 a permanent address outside the router’s DHCP range
      Gateway 10.0.0.1 the router
      DNS Server 10.0.0.1 the router or your own DNS

      Pick the name and address right away: they can be changed later, but in several places (Node name and address).

      On the Summary screen check everything once more, leave the Automatically reboot after successful installation checkbox on and press Install. In a few minutes the host goes into a reboot — pull the stick out at that moment, or it may boot from it again, into the installer.

    5. Log in to the web UI

      The host console shows the address above the login prompt: https://10.0.0.2:8006/. Open it in a browser on a computer on the same network — https only, the port doesn’t answer http. The browser warns about the certificate: it’s self-signed, accept it.

      Login: User name root, the password from the install, and Linux PAM standard authentication in the list under the password. A No valid subscription pop-up appears — close it with OK. It will show at every login and doesn’t affect anything. Only a subscription key removes it for good; scripts that patch proxmoxlib.js work until the next update of the proxmox-widget-toolkit package.

    6. Connect the no-subscription repository

      After install the enterprise repositories are enabled, and they open only with a subscription key: apt update fails with 401 Unauthorized. Switch to pve-no-subscription:

      1. The node (in the tree on the left, pve1) › Updates › Repositories.
      2. The pve-enterprise line — Disable. The Ceph line with the enterprise component — Disable too.
      3. Add › No-Subscription › Add.

      A yellow warning that no-subscription isn’t recommended for production stays at the top of the page. For home and a lab it’s a normal choice: the same packages that will reach enterprise, only earlier. What it looks like in the .sources files — No-subscription repository.

    7. Update

      Node › Updates › Refresh, then Upgrade — a console with the update opens. Or in the node’s Shell:

      apt update
      apt full-upgrade

      Only full-upgrade (or dist-upgrade), as in the Proxmox FAQ: a Proxmox update brings new packages and changes dependencies, and apt upgrade leaves some packages half-updated.

      If the kernel was updated (proxmox-kernel-… packages), reboot: node › Reboot. Which kernel is running and which is installed — pveversion -v | head -3.

    8. Add an SSH key and close password login

      From a computer that already has a key (SSH keys):

      ssh-copy-id [email protected]
      ssh [email protected] 'hostname'          # logs in without a password, prints pve1

      Once key login works, forbid root from logging in over SSH with a password — the password stays for the console and the web UI:

      echo 'PermitRootLogin prohibit-password' > /etc/ssh/sshd_config.d/10-root-key.conf
      sshd -t && systemctl reload ssh

      A file in sshd_config.d is read before the main sshd_config, and in sshd the first value found wins. Keep a second session open before reload (Keep the old session open).

    9. Check notifications

      Datacenter › Notifications. There’s already a mail-to-root target — the email from the install. Select it and press Test. If the message doesn’t arrive within a couple of minutes, spam folder included, add Add › SMTP: the mail service’s server, login and app password — and test with that. Without working mail you’ll learn about a failed backup or a dying disk when it’s too late.

    If it doesn’t work

    A black screen after picking the installer entry

    Cause
    The graphical installer didn’t get along with the video driver: it happens with brand-new and with server graphics cards.
    Fix
    In the boot menu pick Install Proxmox VE (Terminal UI): the same installer in text mode, which needs no graphics.

    The USB stick doesn’t boot, or the installer can’t find the installation medium

    Cause
    Rufus wrote the image in ISO mode, while byte-for-byte DD mode is needed. Or the stick was made with UNetbootin — the Proxmox documentation says outright that the image doesn’t work with it — or with Ventoy.
    Fix
    Write it again: Rufus choosing DD when asked about the mode, balenaEtcher, or dd on Linux.

    The installer warns that there’s no KVM hardware support

    Cause
    Intel VT-x or AMD SVM is disabled in the BIOS. Proxmox will install, but virtual machines won’t start.
    Fix
    Reboot into the BIOS, enable virtualization (step 2) and run the install again.

    The install finished, but https://10.0.0.2:8006 doesn’t open

    Cause
    The host’s address or gateway isn’t from the home network, the address is taken by another device, or the cable is plugged into a different card than the one picked in the installer.
    Fix
    On the host console: ip -br addr shows the address on vmbr0, ping 10.0.0.1 gets a reply from the router. If not, fix /etc/network/interfaces and /etc/hosts (Node name and address), then ifreload -a.

    apt update: 401 Unauthorized from enterprise.proxmox.com

    Cause
    One of the enterprise repositories is still enabled: Proxmox VE or Ceph.
    Fix
    Node › Updates › Repositories — Disable on both (No-subscription repository).

    Emails about backups and updates don’t arrive

    Cause
    By default notifications go through the local postfix straight to the recipient’s server. Mail services reject such messages from a home address or put them in spam.
    Fix
    Datacenter › Notifications › Add › SMTP — through a mailbox with an app password; or Gotify, or a webhook. The Test button checks right away.

    How to check

    In the node’s Shell:

    pveversion
    # pve-manager/9.2.21/4f6e0ac86f9e8c7f (running kernel: 7.0.14-25-pve)
    pvesm status            # local and local-lvm (or local-zfs) — active
    apt update              # not a single line with 401 or Err
    apt list --upgradable   # empty: everything is up to date
    ip -br addr show vmbr0  # vmbr0  UP  10.0.0.2/24

    From a computer: ssh [email protected] logs in with the key, while ssh -o PubkeyAuthentication=no [email protected] gets Permission denied — password login is closed. Next — the first VM from a template (VM template with cloud-init) or a container (First LXC container).