Edit and standardize the web server templates that power every hosted domain. This page appears only when a web server is installed (Apache or NGINX+Apache). Changes here influence how Apache behaves globally and how vhosts are generated.

Tabs

• httpd.conf Template — the core Apache configuration.
• VirtualHost Template — blueprint for standard domains served by Apache.
• Proxied VirtualHost Template — blueprint when Apache sits behind NGINX (reverse proxy).

httpd.conf Template

• What it is: the base server config controlling ports, server name, modules, security, and defaults.
• Variables: placeholders such as {{ public_http_port }}, {{ local_http_port }}, {{ httpd_server_name }} are auto-rendered by the system. Don’t hardcode their values in the template.
• Editor behavior: the template is loaded into a code editor (size capped to 1 MB). Saving creates a backup and runs a validation/apply step.
• Apply: “Validate & Apply Changes” rebuilds the live httpd.conf from this template and reloads Apache. On validation failure, the backup is restored and the error is shown.
• Impact: global. All sites inherit the server-wide behavior defined here.

VirtualHost Template (standard domains)

• Purpose: defines how new domains’ vhosts are built (document roots, logs, PHP handler, directives, etc.).
• Save Changes: updates the template for future domains only.
• Validate & Apply to all Domain accounts: pushes the updated template to all existing domains and rebuilds their vhosts.
• Progress: the bulk apply streams live notifications (started, processing, completed, or error) until all domains are done.
• Note: this bulk action is disruptive if you have many domains; plan a maintenance window.

Proxied VirtualHost Template (behind NGINX)

• Purpose: same as above but tailored for reverse-proxy deployments where NGINX fronts Apache.
• Save Changes vs Validate & Apply: identical behavior to the standard vhost template (future domains vs all domains).
• Use when: you offload TLS/HTTP/2, caching, or WAF to NGINX and pass app traffic to Apache.

Best practices

• Keep server-wide items (ports, core modules, security headers) in httpd.conf; put per-site behavior (root, logs, rewrites) in the vhost templates.
• Use variables/placeholders; avoid baking static hostnames, ports, or paths into templates.
• Test changes on a staging server or a single domain before bulk applying to all.
• Backups are created for critical templates; still keep your own version control for audit and rollback.

Troubleshooting

• “This page is not available…” — install/enable a web server component (Apache or NGINX+Apache) first.
• Validation failed on httpd.conf: the system restores the previous template. Fix the shown error and retry.
• Bulk apply halted: the live progress will report the failing domain. Correct the template or domain-specific data and rerun.
• Unexpected site behavior after apply: compare the generated vhost against the template changes; revert using your backup if needed.