Appearance
Proxmox Host Setup
The physical Proxmox server runs the homelab's virtual machines and Linux containers. Applications run inside those guests; the dedicated media server runs Ubuntu separately.
For host-specific access and AI operating procedures, see Proxmox · Internal Operations.
Configuration
| Setting | This homelab | For another installation |
|---|---|---|
| Node name | beelink | Choose a permanent, unique node name |
| Host address | 10.120.40.5/24 | A reserved address on your management network |
| Gateway | 10.120.40.1 | Your management network's router |
| Direct console | https://10.120.40.5:8006 | HTTPS on your host's port 8006 |
| Proxied console | https://pve.home.rwk.me | A dedicated hostname you control |
| Local guest storage | flash | Storage supporting VM disks and container volumes |
| NAS backup storage | unas-pro-pve | Your independent backup destination |
Hardware specifications are in Servers. This is a single-node setup guide; clustering and shared-storage migrations require a separate plan.
Prepare the hardware and installer
- Enable CPU virtualization in firmware. Enable IOMMU only if your planned device passthrough requires it.
- Connect the management Ethernet port and a local keyboard and monitor. Confirm the switch port's untagged network or VLAN settings match your intended management address.
- Download the Proxmox VE installer ISO from Proxmox, verify its published checksum, and write it to a USB installer.
- Identify the installation disk by model and capacity. Back up existing data before proceeding: installation repartitions the selected disk.
The host has a 512 GB system SSD and an additional 2 TB NVMe SSD. Select storage based on actual disks and recovery requirements. Do not assume two different-capacity drives form a mirror or that the installer creates this lab's flash storage automatically.
Install Proxmox VE
Boot the USB installer and choose the graphical or terminal installer. Set the installation disk, filesystem, locale, timezone, administrator password, and notification email. Store credentials in a password manager.
Set a fully qualified hostname whose short node name is beelink for this lab; on another installation, choose your own hostname. Configure the management address and gateway from the table. Choose a DNS resolver reachable during recovery, including when DNS guests are stopped. A resolver hosted only on this node introduces a boot dependency.
Complete installation, remove the USB drive, and reboot. Connect to the direct console URL from a trusted management client. Validate the initial certificate through your trusted local setup before accepting its self-signed certificate. See the official installation guide for installer and filesystem choices.
Configure updates
In the node's Updates → Repositories panel, select the repository appropriate to your subscription. Use the enterprise repository with a valid subscription, or the matching no-subscription repository for a lab without one. Disable inaccessible enterprise entries and avoid mixing repositories from different Debian or Proxmox releases. See Proxmox package repositories.
Refresh package metadata and review available updates through the web interface. Apply updates before creating production guests, then reboot if required. Confirm the direct console and storage still work afterward.
Configure the network bridge
The installer normally puts management networking on a Linux bridge such as vmbr0, with the physical Ethernet interface attached as a bridge port. Guests connect to that bridge to reach the network.
In Node → System → Network, verify the selected physical port, bridge address, prefix, and default gateway. Use the actual detected interface name. Keep one intended default gateway and avoid assigning the same host address to both the bridge and its physical port.
This lab places most server guests on Home Lab VLAN 40, while the VPN guest uses VLAN 5. When guests need tagged VLANs, configure the switch trunk and a VLAN-aware bridge together, then set each guest's VLAN tag. Do not add a host VLAN tag simply because a guest uses one. Keep the local console available when applying network changes. Refer to Proxmox networking for bridge and VLAN configurations.
Configure local guest storage
Inspect Node → Disks and Datacenter → Storage before initializing a disk. Choose a supported backend appropriate to the disks, such as ZFS, LVM-thin, or directory storage. Disk initialization and pool creation can erase data.
For this lab, guest provisioning scripts expect an active storage ID named flash with support for their VM disks and container volumes. Create or restore that storage mapping to the intended local backend before running those scripts. The ID is a Proxmox configuration name; it does not identify a particular physical disk by itself.
Confirm storage status from the host shell:
sh
lsblk -o NAME,SIZE,MODEL,FSTYPE,MOUNTPOINTS
pvesm statusDo not initialize an existing data disk during a rebuild until its contents and import options have been inspected.
Add NAS backup storage
In Datacenter → Storage → Add → SMB/CIFS, configure:
| Field | This homelab |
|---|---|
| ID | unas-pro-pve |
| Server | 10.120.40.6 |
| Share | Proxmox |
| Content | VZDump backup files; enable other types only if needed |
| Nodes | The intended Proxmox node |
Enter a NAS account with access to the share and retain its credentials in your password manager. Proxmox mounts this storage at /mnt/pve/unas-pro-pve; backup archives are under its dump directory. For another NAS, replace the address, share, and storage ID consistently.
Verify that the storage is active and backed by the expected CIFS share:
sh
pvesm status
findmnt -T /mnt/pve/unas-pro-pveCreate a backup job under Datacenter → Backup, selecting the guests, destination, schedule, and retention you actually require. Test a restore with an isolated guest before treating the policy as recoverable. A local snapshot does not protect against loss of the physical host.
Configure HTTPS access
First confirm the direct port-8006 console works. For the lab hostname, make pve.home.rwk.me resolve to Nginx Proxy Manager at 10.120.40.101. Create a proxy host forwarding to HTTPS, address 10.120.40.5, port 8006; enable WebSocket support, select the certificate covering the public-facing hostname, and force HTTPS.
Keep the direct URL available as a recovery path because the proxy runs in a guest on this host. Test console access through both paths. Proxy TLS termination does not automatically establish certificate validation for a self-signed upstream; configure upstream trust deliberately if enabling verification.
Secure access and configure guests
Install your chosen administrative public SSH key, preserve existing authorized keys, and prove a fresh key login before disabling password authentication. Keep working local-console access. The lab has a host-specific SSH policy; its administrative username and exceptions are in the internal runbook.
Use Servers to plan guest placement and the service guides for application configuration. Set guest start-at-boot behavior deliberately and install the QEMU Guest Agent in supported VMs. Verify graceful guest shutdown before enabling unattended host power management.
This lab coordinates UPS shutdown and NAS readiness from the physical Proxmox host. Restore that integration before relying on automatic outage recovery; guest startup must respect storage dependencies. Installation assets and power scripts remain in the homelab repository.
Maintenance checks
Run in the Proxmox host shell:
sh
pveversion -v
pvesm status
qm list
pct list
systemctl is-active pveproxy pvedaemonCheck guest consoles, backup jobs, storage availability, and the direct management URL after host changes. Inspect active backup, migration, restore, and storage tasks before a reboot. Stop or migrate guests through an orderly maintenance procedure rather than cutting power.