Apache2 & OpenLiteSpeed

Apache2 & OpenLiteSpeed

Besides Nginx, VinzaPanel can run Apache2 or OpenLiteSpeed as the server's web server. Both honour .htaccess files, which makes them the easy choice for PHP applications that ship their own rewrite rules (WordPress, Laravel, many CMSs). You pick the web server in the setup wizard at first login; only one runs at a time.

Apache2

Open Server → Apache2 (/apps/apache2/).

• Service control: start, stop, restart, reload, and a configuration test (apachectl configtest).
• Virtual hosts: list the sites in /etc/apache2/sites-available/ and see which are enabled.
• Modules: enable or disable Apache modules (a2enmod/a2dismod); Apache restarts afterwards. On install the panel enables rewrite, headers, proxy, proxy_fcgi, deflate and ssl.
• Logs: tail /var/log/apache2/error.log or access.log (up to 500 lines).

Website owners without administrator rights only see the running state and version; vhost and module lists are admin-only.

Where things live (Apache2)

OpenLiteSpeed

Open Server → OpenLiteSpeed (/apps/openlitespeed/). OpenLiteSpeed is event-driven, honours .htaccess and has a built-in cache. The service is called lshttpd.

• Service control and a configuration test (lshttpd -t).
• Server settings: a form for maxConnections, connTimeout, keepAliveTimeout, maxKeepAliveReq, maxReqBodySize, enableGzipCompress and showVersionNumber. After saving, the configuration is tested; if the test fails, the original file is restored, otherwise OpenLiteSpeed reloads gracefully.
• Virtual hosts: a read-only view of each site's vhconf.conf.
• Logs of the server.

Where things live (OpenLiteSpeed)

.htaccess and Web Rules

On Apache2 and OpenLiteSpeed, a site's .htaccess in its document root works as usual. The website's Web Rules (Websites → domain → Files & Logs → Web Rules) edits the same file through a guided form: force HTTPS, force www or non-www, redirects and rewrites, blocking dotfiles, .env files and IPs, password protection, static caching, security headers and PHP values. Only the panel's own block is changed — the rest of your .htaccess is kept. PHP values are written to the site's .user.ini, which PHP-FPM reads.

Switching web server

Open the Vinza Store, find the web server you want and click Replace (or Install (replaces active app) on its page). Before it starts, the panel tells you which app is removed and how many sites will be moved. Then:

1. the new web server is installed and the old one is removed, together with its configuration directory;
2. every website on this server is rewritten for the new web server from the panel template (hand-edited vhosts are lost);
3. sites on remote nodes are not affected.

The install log lists each migrated site. If a site fails to migrate, fix it from Websites.