"Web Server Tab"
The Web Server tab decides how a domain is served: which server mode runs it, whether full-page caching is on, and what custom configuration is layered on top. The cards you see depend on your permissions and on the current mode.
Domain Editor → Web Serverhttps://YOUR-SERVER-IP:8443/domains/edit/DOMAIN-ID#webserverFastest static serving Recommended
.htaccess compatibility Recommended
Serve whole pages from Nginx cache OFF
.system/conf/vhost_nginx.conf · Apply & Reload Nginx
ROOT only · edits the live vhost file
Server mode
Two modes, presented as selectable cards:
| Mode | When to use it |
|---|---|
| Nginx Only | Pure Nginx serving; the leanest and fastest option for most modern apps |
| Nginx + Apache | Nginx in front, Apache behind it; needed when a site relies on .htaccess rules or Apache-specific modules |
Picking a different mode opens a confirmation dialog immediately, warning about the impact before anything changes. On confirm the panel rewrites the domain's server configuration and the page reflects the new mode; switching to Nginx + Apache reveals the Apache cards below, switching away hides them. A "Current Configuration" box always shows the active mode and its state. Note that the Security tab depends on this choice: ModSecurity features need the Nginx + Apache mode.
Full-page Cache
A single switch that turns Nginx full-page caching (FastCGI cache) on or off for this domain. When enabled, whole page responses are served straight from Nginx's cache, which can absorb large traffic spikes without touching PHP. The card's hint explains the behavior; the switch applies immediately.
Custom configuration: Nginx and Apache
These editors add your own directives on top of the panel-generated configuration; they do not expose the main vhost file. Each card shows the include file it writes (~/.system/conf/vhost_nginx.conf or vhost_apache.conf), a monospace editor, and a Show Examples toggle with ready-made snippets fitting that layer: the Nginx card offers headers, IP blocks, redirects and proxying examples, while the Apache card covers error pages, IP restrictions and headers (proxying stays on the Nginx side, as its note explains). The Apache editor exists only while the domain runs in Nginx + Apache mode.
Apply & Reload sends the configuration to the server, which validates and applies it; errors come back as a visible message on the card. An unsaved-changes hint appears while you type, and Reset returns the editor to the last saved content.
Vhost editors (ROOT only)
For the rare case where the include file is not enough, ROOT can open the Vhost Editor: a collapsed, red-flagged card per server that loads and edits the domain's actual live vhost file. The card opens with a HIGH RISK warning list reminding you that a wrong edit can take the whole site down and that the custom configuration cards above are the safer route. The Apache variant appears only in Nginx + Apache mode.
Permissions
Each card has its own permission: changing the server mode, editing Nginx custom configuration, editing Apache custom configuration and editing vhost files are separate keys, and the vhost editors additionally require the ROOT role. Cards you lack simply do not appear. The Full-page Cache switch is available to anyone who can see the tab.