Ubuntu Server LTS Pro 24.04.4 | Webmin 2.641 | Virtualmin 8.1.0 GPL | Apache Webserver 2.4.58 | BIND DNS Server 9.18.39 | MariaDB Database Server 10.11.14 | PHP-FPM Server 8.5.6 | Postfix Mail Server 3.8.6 | Dovecot IMAP / POP3 Server 2.3.21 | Cyrus SASL Authentication Server 2.1.28 | ConfigServer Security & Firewall (CSF) 15.10 | ClamAV Virus Scanning Server 1.4.4 | SSH Server (OpenSSH) 9.6 | OpenSSL 3.0.13 | Certbot 2.9.0
I’m opening this as a feature request for the developers’ awareness rather than expecting an immediate implementation — I fully understand the complexity involved.
Background
The Nextcloud community recently published a comprehensive, well-tested guide (March 2026) on enabling HTTP/3 alongside Apache using a hybrid Apache + Nginx architecture. While written around Nextcloud, the pattern applies equally to any application managed by Virtualmin — WordPress, OpenCart, or any standard LAMP stack:
The architecture in brief
Since Apache has no native HTTP/3 support (architectural limitation, not a missing module), the hybrid approach keeps Apache handling all TCP traffic unchanged, while Nginx (≥ 1.25.0) is added exclusively for UDP/443 (QUIC), forwarding requests to Apache on 127.0.0.1:8080. TCP and UDP do not conflict on the same port. Nothing in the existing Apache configuration changes.
Why this matters for Virtualmin
The manual steps are well-documented. The problem in a Virtualmin environment is that every new Virtual Server automatically gets an Apache VirtualHost — but there is no corresponding automation for the Nginx QUIC config, SSL cert sync, or the internal loopback listener. Every domain requires manual intervention, which defeats the purpose of Virtualmin.
What this proposes
An optional feature that, when enabled, automates per-VirtualHost:
- Nginx QUIC-only config generation
- Internal Apache listener on 127.0.0.1:8080
- SSL certificate path synchronization
Alt-Svcheader in the Apache VirtualHost
Acknowledged complexity
This is not a quick win — it requires Nginx mainline package management, lifecycle hooks (create, delete, SSL renew), and a system-wide kernel UDP tuning. I’m raising it primarily so it’s on the radar, with the Nextcloud guide as a solid reference implementation.
Thank you for considering it.
Finally, a personal note: Virtualmin has been an exceptional learning experience. The way it is designed — transparent, structured, and exposing the underlying system rather than hiding it — has taught me more about server administration than any other tool I have used. That is rare, and genuinely appreciated. Thank you for building something this good.