Appearance
Proxy LXC Setup
The proxy guest runs native Nginx Proxy Manager and OpenResty. It is a shared entry point for homelab HTTPS applications, so its maintenance affects multiple services.
Prepare the physical Proxmox host first. For host-specific accounts, scripted setup, and AI recovery procedures, see Proxy LXC · Internal Operations.
For another homelab, choose unused guest IDs and addresses, your own gateway and DNS, and storage sized for your workload. Confirm actual inventory and DHCP assignments before creation; a failed ping alone does not prove an address is free.
Guest configuration
| Setting | This homelab |
|---|---|
| Guest ID / hostname | 101 / npm |
| Type | Unprivileged Debian 13 LXC |
| CPU / RAM / swap | 2 vCPU / 2048 MB / 512 MB |
| Root disk | 10 GB on suitable local storage |
| Address / gateway | 10.120.40.101/24 / 10.120.40.1 |
| Features | keyctl and nesting |
| Startup | Start at boot |
Create the guest and native application
This homelab uses the Proxmox VE Community Scripts NPM installer, which creates the LXC and installs the native application. On the physical Proxmox host, download and inspect the current installer before running it:
sh
curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh -o /tmp/nginxproxymanager.sh
less /tmp/nginxproxymanager.sh
bash /tmp/nginxproxymanager.shChoose advanced settings matching the table. Confirm the summary's OS, unprivileged mode, guest ID, resources, network, and features before creation. The installer is maintained upstream and can change; use its supported settings rather than forcing an incompatible template. Do not create a second proxy with an existing address.
Set the bridge and VLAN behavior to the network actually presented by your Proxmox host. Enable only the required guest features. After creation, keep the Proxmox console open while bootstrapping administrative access.
Prepare the guest OS
Create your chosen normal administrative account with sudo access from the guest console, then perform routine administration through that account. Update Debian and install the necessary tools:
sh
sudo apt update
sudo apt full-upgrade
sudo apt install ca-certificates curl gnupg jq openssh-server sudoThis is an LXC: it uses the host kernel and does not need a VM's QEMU Guest Agent. Do not install Docker to follow these guides; this lab's NPM deployment uses native systemd units.
Configure administrative access
Create a normal sudo-capable administrator account during installation or from the initial console. Store its password securely. Install only your intended public SSH key while preserving existing keys, then prove a fresh key-authenticated session before disabling password and keyboard-interactive authentication. Inspect sshd -T, validate with sshd -t, and reload ssh.service while keeping the initial session and Proxmox console available.
For a new guest with a proven non-root administrative account, an early SSH drop-in can use:
text
PubkeyAuthentication yes
PasswordAuthentication no
KbdInteractiveAuthentication no
PermitRootLogin noVerify a new key login succeeds and password-based login is rejected. The exact lab usernames and reviewed policy files are internal. Do not apply a root-login restriction before a non-root administrator and recovery path work.
Verify listeners and storage
sh
systemctl is-active npm openresty ssh
sudo /usr/local/openresty/nginx/sbin/nginx -t
curl --fail --silent --show-error --output /dev/null http://10.120.40.101:81/Allow TCP 80/443 for intended proxy clients and TCP 81 only for trusted administration. Application state is in /data; certificates and renewal state are in /etc/letsencrypt. Back up both together. No in-guest NAS mount is required for normal proxy operation.
Continue with Nginx Proxy Manager configuration to initialize the administrator, DNS, certificates, proxy hosts, and access policies. Do not rely on the proxied administration hostname until the direct dashboard works.
Backups and startup checks
Set Start at boot deliberately and preserve the physical host's coordinated startup behavior. Configure a protected off-host Proxmox backup with a schedule and retention appropriate to the guest, then test restoration without creating a duplicate active address or identity.
After initial setup or a controlled reboot, confirm network configuration, DNS, key-only access, service health, and the application's primary function. Keep the Proxmox guest console as an out-of-band recovery path. Inspect active backup and storage tasks before maintenance; avoid hard power removal.