PVEmanager is a self-hosted web panel that provides a unified interface for managing multiple Proxmox VE servers and clusters. It covers the full VM/LXC lifecycle — from provisioning to monitoring — with role-based access control, notifications, and IP address management.

• Multi-server management — connect and manage multiple Proxmox servers and clusters from a single panel
• VM & LXC lifecycle — create, start, stop, restart, resize, delete virtual machines and containers
• Bulk operations — mass start / stop / restart / delete with queue and progress tracking
• Snapshot management — create, rollback, delete snapshots with an async queue system
• OS templates — deploy VMs from templates; cross-node replication handled automatically
• SDN support — manage Software-Defined Networking zones, VNets, and subnets; edit zones and VNets; auto-create IPAM networks for subnets
• Node networking — manage node-level network interfaces (bridges, bonds, VLANs); apply/revert pending config
• Networks page — unified UI for SDN and node interface management

• VNC console — in-browser console via noVNC, no client software required
• xterm.js terminal — full interactive shell directly in the browser for LXC containers
• Remote commands — execute bash commands via QEMU Guest Agent
• RBAC v2 — granular role-based access control with per-resource permissions
• Server assignment — directly assign specific Proxmox servers to users with workspace-conflict validation
• VM/LXC ownership — assign an owner user to any VM or LXC container
• Session management — active session list, remote session revocation, login protection
• Smart login redirect — users are automatically routed to the first page they have access to

• Real-time metrics — CPU, RAM, Disk, Network charts per node and per VM
• Background sync — automatic VM state synchronization from Proxmox API
• Notifications — In-App (bell icon), Email (SMTP), Telegram (Bot API)
• Audit log — full action log with user, timestamp, and details

• IPAM — IP Address Management with allocation history and orphan detection
• Multilingual — Russian and English interface
• Encrypted credentials — sensitive fields stored encrypted in the database

# 1. Clone
git clone https://git.tzim.uz/markmorado/pvemanager.git
cd pvemanager

# 2. Configure
cp .env.example .env
cp backend/.env.example backend/.env
# Edit .env — set POSTGRES_PASSWORD and TZ

# 3. Start
docker compose up -d

# 4. Open
# http://localhost:8000
# Default login: admin / admin123

Important: Change the default password immediately after first login.

# Database
POSTGRES_PASSWORD=your_secure_password

# Timezone (IANA format)
TZ=Europe/Moscow

# Update checks (for private repos — disable or provide a token)
DISABLE_UPDATE_CHECK=false
GITHUB_TOKEN=                     # optional, for private repo update checks

Configured via the web interface — Settings → Notifications:

• Email — SMTP server, port, login, password (Yandex, Gmail, Mail.ru and others)
• Telegram — Bot token and Chat ID via @BotFather

1. Fork the repository
2. Create a feature branch: git checkout -b feature/my-feature
3. Commit your changes: git commit -m 'feat: add my feature'
4. Push: git push origin feature/my-feature
5. Open a Pull Request

MIT — free to use, modify, and distribute.