Deployment Overview of Proxmox Backup Server on Server¶
Prerequisites and Basic Requirements¶
To ensure a successful deployment, the following requirements must be met:
-
Operating System: Debian 12 (Bookworm) is required.
-
Privileges: Root or sudo access is necessary for package installation and service management.
-
Architecture: amd64.
-
Network Ports:
-
8007: Internal application port. -
443: External HTTPS port (managed via Nginx).
FQDN of the final panel on the hostkey.in domain¶
The application is accessible via a specific subdomain template within the hostkey.in zone.
| Parameter | Value |
|---|---|
| Prefix | proxmox-backup-server |
| Domain | hostkey.in |
| Full template | proxmox-backup-server{Server_ID_from_Invapi}.hostkey.in |
File and Directory Structure¶
The following directories are used for configuration, proxy management, and SSL certificates:
-
/etc/apt/sources.list.d/pbs.list: Repository configuration file for Proxmox Backup Server. -
/etc/apt/trusted.gpg.d/proxmox-release.gpg: GPG key for the Proxmox repository. -
/root/nginx: Directory containing the Nginx Docker Compose configuration. -
/data/nginx/user_conf.d/: Directory containing Nginx site configurations and proxy settings. -
/data/nginx/nginx-certbot.env: Environment file for the Nginx container.
Application installation process¶
The installation of Proxmox Backup Server is performed through a series of system configuration steps:
-
System Preparation: The system updates the package cache, upgrades existing packages to their latest versions, and ensures
curl,wget,ca-certificates, andgnupgare installed. -
Repository Configuration:
-
The Proxmox Backup Server GPG key is downloaded to
/etc/apt/trusted.gpg.d/proxmox-release.gpg. -
The non-subscription repository (
deb http://download.proxmox.com/debian/pbs bookworm pbs-no-subscription) is added to/etc/apt/sources.list.d/pbs.list. -
Package Installation: The
proxmox-backup-servermeta-package is installed via the package manager. -
Kernel Headers: For Debian 12,
linux-headers-amd64is installed to support system requirements.
Access Rights and Security¶
Security is managed through several layers:
-
Repository Security: Enterprise repositories are removed to prevent unauthorized access attempts or version conflicts, ensuring the use of the official no-subscription repository.
-
SSL/TLS: SSL certificates are managed via a Dockerized Nginx container using Certbot for automated certificate acquisition and management.
-
Service Management: The
proxmox-backupservice is enabled to start automatically on system boot.
Databases¶
This application does not utilize an external database; it relies on the local filesystem for data storage and internal mechanisms for metadata management.
Docker Containers and Their Deployment¶
The deployment includes a proxy container to handle SSL termination and web traffic:
-
nginx
-
Image:
jonasal/nginx-certbot:latest -
Ports: Uses
hostnetwork mode. -
Volumes:
-
nginx_secrets:/etc/letsencrypt(External volume for SSL certificates) -
/data/nginx/user_conf.d:/etc/nginx/user_conf.d(Custom Nginx configurations) -
Environment Variables:
[email protected] -
Restart Policy:
unless-stopped
Custom Scripts and Additional Setup¶
The deployment includes a configuration step for the Nginx proxy:
-
Nginx Configuration Generation: A
compose.ymlfile is generated in/root/nginx. -
Reverse Proxy Setup: The system automatically modifies the Nginx site configuration located in
/data/nginx/user_conf.d/proxmox-backup-server{Server_ID_from_Invapi}.hostkey.in.confto include aproxy_passdirective pointing tohttp://127.0.0.1:8007.
Application Update Instructions¶
To update the Proxmox Backup Server application, perform the following steps:
-
Synchronize package lists:
-
Upgrade the installed packages:
Location of configuration files and data¶
-
Application Configuration: Managed internally by Proxmox Backup Server.
-
Nginx Site Configs:
/data/nginx/user_conf.d/ -
Docker Compose File:
/root/nginx/compose.yml
Available ports for connection¶
| Port | Service | Description |
|---|---|---|
443 | HTTPS (Nginx) | External access via web browser |
8007 | Proxmox Backup Server | Internal application service |
Starting and Stopping the application¶
The main application is managed via systemd:
-
Start the service:
-
Stop the service:
-
Check status:
Proxy Servers (Nginx, Traefik, SSL, custom domains)¶
The application uses an Nginx container (jonasal/nginx-certbot) to provide SSL termination. The proxy is configured as a reverse proxy that forwards traffic from the domain proxmox-backup-server{Server_ID_from_Invapi}.hostkey.in on port 443 to the internal application service running on port 8007.