10-11-2026, 05:39 AM
Quick answer
aaPanel offers Multi-WebServer Hosting for choosing a web engine per website. Prepare backups and a clean configuration before enabling it. This article covers the requirements, not a completed multi-server installation.
What it changes
According to aaPanel’s documentation, enabling the feature installs Nginx, Apache and OpenLiteSpeed and manages their port conflicts. It supports individual engines and Nginx proxy combinations. Nginx normally fronts the proxy setups on ports 80/443; the other engines use separate backend ports.
Where the setting is
In our aaPanel Free Edition 8.0.6 lab: Website → Nginx version button → Web server → Multi-WebServer Hosting. The screenshot shows the actual switch turned OFF.
![[Image: attachment.php?aid=29]](https://adminsforum.com/attachment.php?aid=29)
Prepare before enabling
1. Back up website files, databases, certificates and server/site configuration. Keep a copy outside the VPS.
2. Record the current site’s PHP version, extensions, redirects and rewrite rules.
3. Review aaPanel’s warning about manually changed configuration. A custom working Nginx rule is not automatically compatible with another engine. Test the change in a separate lab before migrating an active website.
4. Check for conflicting listeners on the ports listed in the panel. Do not expose backend or management ports publicly just to satisfy the installer.
5. Plan a maintenance window and a tested way back to the current setup.
PHP needs a separate check
Nginx/Apache PHP is managed through the PHP app. OpenLiteSpeed uses lsphp, managed separately; existing PHP extensions may need to be installed there too. Verify the website’s actual runtime after changing engines.
Our verification
On 11 October 2026 we confirmed the setting is available in the Free Edition lab. We did not enable it: the existing WordPress subfolder has custom Nginx rewrite rules. We are keeping that working environment intact until the migration prerequisites are satisfied. No multi-webserver performance or successful migration is claimed here.
Related tested guides
Back up and restore website files
Back up and restore a database
Official reference
aaPanel Multi-WebServer Hosting documentation
aaPanel offers Multi-WebServer Hosting for choosing a web engine per website. Prepare backups and a clean configuration before enabling it. This article covers the requirements, not a completed multi-server installation.
What it changes
According to aaPanel’s documentation, enabling the feature installs Nginx, Apache and OpenLiteSpeed and manages their port conflicts. It supports individual engines and Nginx proxy combinations. Nginx normally fronts the proxy setups on ports 80/443; the other engines use separate backend ports.
Where the setting is
In our aaPanel Free Edition 8.0.6 lab: Website → Nginx version button → Web server → Multi-WebServer Hosting. The screenshot shows the actual switch turned OFF.
Prepare before enabling
1. Back up website files, databases, certificates and server/site configuration. Keep a copy outside the VPS.
2. Record the current site’s PHP version, extensions, redirects and rewrite rules.
3. Review aaPanel’s warning about manually changed configuration. A custom working Nginx rule is not automatically compatible with another engine. Test the change in a separate lab before migrating an active website.
4. Check for conflicting listeners on the ports listed in the panel. Do not expose backend or management ports publicly just to satisfy the installer.
5. Plan a maintenance window and a tested way back to the current setup.
PHP needs a separate check
Nginx/Apache PHP is managed through the PHP app. OpenLiteSpeed uses lsphp, managed separately; existing PHP extensions may need to be installed there too. Verify the website’s actual runtime after changing engines.
Our verification
On 11 October 2026 we confirmed the setting is available in the Free Edition lab. We did not enable it: the existing WordPress subfolder has custom Nginx rewrite rules. We are keeping that working environment intact until the migration prerequisites are satisfied. No multi-webserver performance or successful migration is claimed here.
Related tested guides
Back up and restore website files
Back up and restore a database
Official reference
aaPanel Multi-WebServer Hosting documentation