Welcome Guest to Defaut site!

Virtualmin/Proxmox/Starman Coexistence

Potential Conflict Areas

Component Virtualmin Default Manual Setup Risk
Web Services Apache + Nginx proxy Port collision if Starman uses 80/443 directly
Firewall Webmin Firewall Module UFW rules may override Virtualmin's config
SSL Certificates Let's Encrypt via Webmin Manual certs might break auto-renewal
User Accounts Virtualmin-managed users Manual system users won't appear in Virtualmin

Safe Configuration Zones

  1. Starman as Backend Server 
    # Use high ports outside Virtualmin's range
--listen :5000  # Safe (Virtualmin uses 80/443/21/etc)
  2. Proxmox Network Isolation 
    qm set <VMID> -net0 virtio,bridge=vmbr2  # Separate from Virtualmin's vmbr0
  3. Virtualmin Proxy Integration 
    # In Virtualmin: Services → Configure Website → Proxy to URL
http://localhost:5000/  # Reverse proxy setup

Integration Best Practices

File System Layout

/home/
├── virtualmin/  # Virtualmin-managed
│   └── domains/
└── starman/     # Manual installations
    └── apps/

Service User Isolation

# Virtualmin users: web_*
# Manual users: starman_*
sudo useradd --system --shell /usr/sbin/nologin starman_svc

Backup Coordination

  1. Virtualmin Backup: 
    Exclude /home/starman/
  2. Proxmox Backup: 
    Include /home/starman/ in VM backups

Conflict Recovery Steps

  1. Port Conflict Resolution 
    sudo ss -tulpn | grep '80\|443'
sudo systemctl stop starman  # If conflicting
  2. Firewall Reset 
    sudo ufw disable
sudo webmin-firewall --reset
sudo ufw enable
  3. User Permission Repair 
    sudo virtualmin fix-permissions --all-domains
sudo chown -R starman_svc:starman_svc /home/starman

Emergency Rollback Procedure

# Restore Virtualmin core services
sudo virtualmin restore-backup --all-features --force

# Preserve manual configurations
mv /home/starman /home/starman.bak
# Restore from Proxmox backup

Back to top