Skip to content

Servers ​

The homelab uses a dedicated media server and a Proxmox server to run applications and core infrastructure services.

For installation and configuration, see Host Setup. For the software running on this hardware, see Services.

Fixed IP addresses

Physical servers and Proxmox guests use stable addresses through static host configuration and UniFi reservations. Active reservations associate an address with a device's MAC address and prevent DHCP from assigning it to another client. Keep static host addresses coordinated with the DHCP pool.

Consistent addresses keep DNS records, reverse proxy destinations, firewall rules, NAS mounts, and monitoring checks pointing to the correct system after reboots. They also make SSH access and troubleshooting more predictable.

Media Server ​

The media server runs Jellyfin and the Servarr applications for streaming, downloading, and organizing the media library. It runs these applications in Docker on a dedicated Ubuntu host, with media files stored on the NAS.

Hardware Specs ​

  • OS: Ubuntu 24.04.4 LTS
  • CPU: Intel Core Ultra 9 185H (16 cores, 22 threads)
  • RAM: 16 GB DDR5
  • Internal Storage: 1 TB NVMe SSD
  • VLAN: Home Lab (40)
  • IP Address: 10.120.40.105

Service Hierarchy ​

Each leaf under Docker represents a separate container. The labels use the container names running on the server.

  • Media ServerUbuntu
    • Docker
      • jellyfinMedia streaming
      • jellyseerrMedia requests · Seerr image
      • streamystatsStreaming analytics
      • sonarrTV library management
      • radarrMovie library management
      • prowlarrIndexer management
      • bazarrSubtitle downloads
      • subgenSubtitle generation
      • sabnzbdUsenet downloads
      • qbittorrentTorrent downloads
      • unpackerrArchive extraction
      • flaresolverrIndexer challenge handling
      • gluetunVPN connectivity
      • deunhealthUnhealthy container recovery
      • kopiaBackups

Proxmox Server ​

The Proxmox server hosts the homelab's virtual machines and Linux containers. It runs core services including Pi-hole, Nginx Proxy Manager, Tailscale, Syncthing, and the operations tools, keeping each workload in its own guest environment.

Hardware Specs ​

  • OS: Proxmox VE 9.0.11
  • CPU: AMD Ryzen 7 6800H (8 cores, 16 threads)
  • RAM: 32 GB LPDDR5
  • Internal Storage: 512 GB NVMe SSD and an additional 2 TB WD Blue SN5000 NVMe SSD
  • VLAN: Home Lab (40)
  • IP Address: 10.120.40.5

Service Hierarchy ​

Proxmox hosts virtual machines (VMs) and Linux containers (LXCs). Docker containers run inside the guests shown below; native services run directly in their guest. Routine operating system services are omitted.

Guest setup guides: Operations, Proxy, VPN, Pi-hole, and Syncthing.

Guest IDs and IP addresses

In this homelab, a Proxmox guest's ID typically matches the last octet of its IP address. For example, VM 100 uses 10.120.40.100, and LXC 101 uses 10.120.40.101. This is an addressing convention, rather than an automatic Proxmox assignment.

  • Proxmox ServerProxmox VE
    • OperationsVM 100
      • Docker
        • uptime-kumaService monitoring
        • unifi-toolkitUniFi tools
        • librespeedLocal speed tests
        • speedtest-trackerInternet speed monitoring
        • speedtest-tracker-dbPostgreSQL database
        • it-toolsUtility tools
        • rackpadRack inventory
    • Nginx Proxy ManagerLXC 101
      • Nginx Proxy ManagerNative service · proxy management
      • OpenRestyNative service · reverse proxy
    • VPNLXC 102
      • TailscaleNative service · remote access
    • Pi-holeVM 103
      • Docker
        • piholeDNS and ad blocking
    • SyncthingVM 104
      • SyncthingNative service · file synchronization