Skip to content

Deployment Overview of Proxmox 9 on Server

Prerequisites and Basic Requirements

To ensure a successful deployment, the following requirements must be met:

  • Operating System: Debian (versions 11 Bullseye, 12 Bookworm, or 13 Trixie).

  • Privileges: Root or sudo access is required for all installation steps.

  • Network Requirements:

  • Access to the internet to download packages and Docker images.

  • Port 8006 must be available for internal service communication.

  • Port 443 (HTTPS) must be open for external web access via the proxy.

FQDN of the final panel on the hostkey.in domain

The application is accessible via a specific subdomain template based on the server ID.

Parameter Value
Prefix proxmox
Domain hostkey.in
Full template proxmox{Server_ID_from_Invapi}.hostkey.in

File and Directory Structure

The deployment utilizes the following directory structure for configuration and data persistence:

  • /data/nginx/: Contains Nginx configuration files and environment variables.

  • /data/nginx/user_conf.d/: Stores custom Nginx server blocks (including SSL configurations).

  • /data/nginx/letsencrypt/: Stores ACME challenge files for SSL certificate validation.

  • /root/nginx/: Contains the Docker Compose deployment file for the proxy service.

Application installation process

The installation follows a multi-stage process involving system optimization, kernel updates, and containerized proxy setup:

  1. System Preparation:

  2. The GRUB bootloader is configured to target the correct root disk.

  3. Enterprise repositories are disabled in favor of community/no-subscription repositories to ensure package availability without a subscription.

  4. System packages are updated and upgraded to their latest versions.

  5. Kernel Installation:

  6. A Proxmox-optimized kernel is installed based on the detected Debian version (e.g., pve-kernel-5.15 for Debian 11 or proxmox-default-kernel for newer versions).

  7. Standard Debian kernels are removed to prevent boot conflicts.

  8. Proxmox VE Installation:

  9. The proxmox-ve package is installed along with necessary dependencies like postfix and open-iscsi.

  10. A system reboot is performed to initialize the new kernel.

  11. Proxy Setup:

  12. Docker is installed on the host.

  13. An Nginx container is deployed via Docker Compose to handle SSL termination and reverse proxying for the Proxmox web interface.

Access Rights and Security

  • Firewall: The system relies on standard Debian security practices.

  • User Access: Management of the Proxmox interface is handled through the secure HTTPS port provided by the Nginx proxy.

  • Service Isolation: The application runs behind a reverse proxy that handles SSL/TLS termination, isolating the internal service port from direct public exposure.

Databases

This deployment does not include or manage any local databases; it utilizes the Proxmox VE ecosystem for its primary functions.

Docker Containers and Their Deployment

The deployment includes one primary container used for managing SSL certificates and web proxying:

  • nginx-nginx-1

  • Image: jonasal/nginx-certbot:latest

  • Ports: Uses host network mode (accesses host ports directly).

  • Volumes:

  • nginx_secrets:/etc/letsencrypt

  • /data/nginx/user_conf.d:/etc/nginx/user_conf.d

  • /data/nginx/letsencrypt:/var/www/letsencrypt

  • Environment Variables:

  • [email protected]

  • Custom settings from /data/nginx/nginx-certbot.env (e.g., RENEWAL_INTERVAL=8d).

  • Restart Policy: unless-stopped

Application Update Instructions

To update the main application, perform a system upgrade to pull the latest Proxmox packages:

apt update && apt full-upgrade -y

For the Nginx proxy service, use the following command in the /root/nginx directory:

docker compose pull && docker compose up -d

Location of configuration files and data

Component Path
Nginx User Configs /data/nginx/user_conf.d/
SSL Certificates (ACME) /data/nginx/letsencrypt/.well-known/acme-challenge
Docker Compose File /root/nginx/compose.yml
Proxy Environment Variables /data/nginx/nginx-certbot.env

Available ports for connection

  • 443 (HTTPS): External access to the Proxmox management interface via the Nginx proxy.

  • 8006 (TCP): Internal service port used by the Nginx container to communicate with the Proxmox backend.

Starting and Stopping the application

The application relies on system services and Docker containers:

  • To manage the Proxy Service:

  • Start/Restart: docker compose up -d (within /root/nginx)

  • Stop: docker compose down (within /root/nginx)

  • To manage Proxmox Services:

  • Standard systemctl commands are used for underlying Proxmox services.

Proxy Servers

The deployment uses an Nginx container (jonasal/nginx-certbot) acting as a reverse proxy. It is configured to:

  1. Automatically handle SSL certificate renewal via Certbot.

  2. Route traffic from the standard HTTPS port to the internal Proxmox service on https://127.0.0.1:8006.

  3. Handle ACME challenges through a dedicated webroot location for seamless certificate updates.

question_mark
Is there anything I can help you with?
question_mark
AI Assistant ×