Apache2 VirtualHost & Vhost Builder

Apache Virtual Host Generator

Generate production-ready Apache HTTP (port 80) VirtualHost files for sites-available without SSL. Pick your backend architecture (PHP-FPM, Reverse Proxy, or Static), customize directives, and copy commands to test and reload Apache seamlessly.

PHP-FPMArchitecture

80VirtualHost Port

AllAllowOverride

59Lines of Conf

Backend Architecture

Domain Name (ServerName)Includes ServerAlias www.example.com automatically

ServerAdmin EmailDisplayed on server error pages

DocumentRootAbsolute server path to document root

PHP-FPM Socket Version

Directory AllowOverride

Security & Performance Directives

Security Headers (mod_headers)Block .git & .env (FilesMatch)Gzip / Deflate CompressionStatic Asset Caching (mod_expires)

/etc/apache2/sites-available/example.com.conf

<VirtualHost *:80>
    ServerName example.com
    ServerAlias www.example.com
    ServerAdmin webmaster@example.com

    DocumentRoot /var/www/example.com/public

    <Directory /var/www/example.com/public>
        Options -Indexes +FollowSymLinks
        AllowOverride All
        Require all granted

        # Front-Controller Fallback (Laravel / Symfony / WordPress)
        <IfModule mod_rewrite.c>
            RewriteEngine On
            RewriteCond %{REQUEST_FILENAME} !-f
            RewriteCond %{REQUEST_FILENAME} !-d
            RewriteRule ^ index.php [L]
        </IfModule>
    </Directory>

    # PHP-FPM Handler (mod_proxy_fcgi)
    <FilesMatch \.php$>
        SetHandler "proxy:unix:/run/php/php8.3-fpm.sock|fcgi://localhost/"
    </FilesMatch>

    # Security Headers (requires mod_headers)
    <IfModule mod_headers.c>
        Header always set X-Content-Type-Options "nosniff"
        Header always set X-Frame-Options "SAMEORIGIN"
        Header always set X-XSS-Protection "1; mode=block"
        Header always set Referrer-Policy "strict-origin-when-cross-origin"
    </IfModule>

    # Gzip / Deflate Compression (requires mod_deflate)
    <IfModule mod_deflate.c>
        AddOutputFilterByType DEFLATE text/plain text/html text/xml text/css application/xml application/xhtml+xml application/json application/javascript image/svg+xml
    </IfModule>

    # Browser Caching for Static Assets (requires mod_expires)
    <IfModule mod_expires.c>
        ExpiresActive On
        ExpiresDefault "access plus 1 month"
        ExpiresByType image/jpeg "access plus 1 year"
        ExpiresByType image/png "access plus 1 year"
        ExpiresByType image/webp "access plus 1 year"
        ExpiresByType text/css "access plus 1 month"
        ExpiresByType application/javascript "access plus 1 month"
    </IfModule>

    # Protect Sensitive and Hidden Files (.git, .env, .htaccess)
    <FilesMatch "^\.(?!well-known)">
        Require all denied
    </FilesMatch>

    # Logging Directives
    ErrorLog ${APACHE_LOG_DIR}/example.com_error.log
    CustomLog ${APACHE_LOG_DIR}/example.com_access.log combined
</VirtualHost>

Activate, Test & Reload Apache

Run these commands on your Ubuntu / Debian server to enable required modules, link the virtual host via a2ensite, verify configuration syntax, and reload Apache.

# 1. Enable required Apache modules
sudo a2enmod rewrite headers proxy proxy_fcgi

# 2. Create and write the VirtualHost config in sites-available
sudo nano /etc/apache2/sites-available/example.com.conf

# 3. Enable the newly created VirtualHost site
sudo a2ensite example.com.conf

# 4. Validate Apache configuration syntax (Crucial Step)
sudo apache2ctl configtest

# 5. If output shows "Syntax OK", safely reload Apache without downtime
sudo systemctl reload apache2

Tool Overview & Best Practices

Apache HTTP Server Virtual Hosts & Security Hardening

I won’t explain what an Apache server is here, as you’ll already know once you’ve explored this page. Apache server configuration is typically required when hosting a website on a root-access, unmanaged VPS, where you must configure the web server manually. However, managed VPS hosting with cPanel or other hosting control panels simplifies this process. These panels can automatically generate and manage Apache configurations based on your selected settings, reducing the need for manual configuration.

Managed VPS hosting panels consume some system resources. If you want to maximize the resources available for your websites, an unmanaged VPS configured directly through Linux commands can be a better option.

However, configuring Apache manually on an unmanaged server can be time-consuming, especially when you need to write configuration files from scratch.

To simplify this process and save developers' time, we developed this tool. It guides you through a series of questions and configuration options based on your VPS setup and hosting requirements. Once you provide the necessary details, the tool generates a customized Apache configuration file that you can use to configure your server.

Apache HTTP Server is a popular, open-source web server that provides full control over your server configuration. As mentioned earlier, you can manage your VPS directly through Linux commands without requiring a resource-intensive hosting control panel. Apache also allows you to host multiple domains on a single server using virtual hosts.

Our tool simplifies Apache configuration by providing flexible PHP version management, custom path selection, and advanced configuration options. It helps you generate configurations tailored to your server and application requirements, making deployment easier and reducing manual setup time.

Below is an in-depth breakdown of essential directives, security hardening strategies, and performance tuning techniques incorporated into our automated generator.

1. ServerName & ServerAlias Best Practices

Defining both the primary ServerName and ServerAlias www.domain.com ensures that search engine crawlers (Googlebot, Bingbot) do not index duplicate content variants under non-www and www URLs simultaneously, protecting your organic search rankings and canonical equity.

2. Directory Options & Security Hardening

Disabling directory indexes (-Indexes) stops malicious actors from browsing raw server directories and downloading unexposed file assets. Furthermore, restricting AllowOverride based on application requirements prevents unauthorized .htaccess overrides that could introduce security vulnerabilities.

3. Protecting Sensitive Config Files (.env, .git)

Modern web apps built on Laravel, Node.js, or Symfony store database credentials and API keys in hidden environment files (.env). Our generator includes strict FilesMatch directives to deny public web access to hidden files, blocking potential data breaches.

4. Performance Optimization via Caching & Compression

Enabling mod_deflate reduces payload transfer sizes for CSS, JavaScript, and HTML assets by up to 70%, directly improving Core Web Vitals (Largest Contentful Paint and Interaction to Next Paint). Combined with mod_expires, static asset caching speeds up repeat user visits.

Step-by-Step Guide

How to Use Our Tool?

Our tool currently supports three Apache configuration modes: General (PHP-FPM), Reverse Proxy, and Static (SPA). Each mode is designed for a different hosting requirement. Select the mode that best fits your application, and our tool will help you generate the appropriate Apache configuration.

General (PHP-FPM): Ideal for PHP applications such as Laravel and WordPress. It supports PHP-FPM integration and lets you configure custom document roots and PHP settings.
Reverse Proxy: Suitable for applications running on separate application servers, such as Next.js or Node.js. Apache forwards incoming requests to your application server.
Static (SPA): Designed for static websites and single-page applications built with React, Vue, or Angular. It supports static file serving and client-side routing configuration.

Enter Domain Name

Enter the domain or subdomain you want to host on your VPS. For example, `example.com` or `app.example.com`. Make sure the domain's DNS records point to your server's IP address.

Enter Server Admin Email

Enter the email address of the server administrator. This email can be used for server-related notifications and SSL certificate registration, such as Let's Encrypt. Use a valid email address that you can access.

Enter The Path or Link

For PHP-FPM or Static (SPA) mode, enter your project’s absolute path. For Reverse Proxy mode, enter your application’s localhost address with port (e.g., `http://127.0.0.1:3000`).

Select PHP Version (PHP-FPM)

Select the PHP version compatible with your project to ensure proper functionality.

Select Directory Allow Override

Choose whether to allow `.htaccess` files to override Apache configuration directives for your project directory.

Security & Performance Directives

Configure security and performance directives to improve server protection, optimize resource usage, and enhance website performance.

Generate Your Apache Configuration

Our tool generates your customized Apache configuration file based on your selected settings instantly.

FAQ

Frequently Asked Questions

Find detailed answers regarding Apache VirtualHost configurations, server security, client-side/server-side architecture, and deployment procedures.

1. Why start with an HTTP-only VirtualHost without SSL?

Setting up a standard port 80 VirtualHost is the standard baseline before issuing SSL certificates via Certbot / Let's Encrypt. The ACME HTTP-01 challenge expects a working HTTP listener on port 80 to verify domain ownership before automatically upgrading the vhost to HTTPS.

2. How do I activate, test, and reload Apache configurations?

Enable the site using 'sudo a2ensite your-domain.conf', verify the syntax without downtime using 'sudo apache2ctl configtest', and apply changes smoothly using 'sudo systemctl reload apache2'.

3. What modules must be enabled in Apache for modern PHP and reverse proxying?

For front-controller frameworks like Laravel, enable 'mod_rewrite' (sudo a2enmod rewrite). For PHP-FPM, enable 'proxy_fcgi' (sudo a2enmod proxy proxy_fcgi). For Node.js/Python apps, enable 'proxy' and 'proxy_http' (sudo a2enmod proxy proxy_http).

4. How does the 90% client-side and 10% server-side architecture apply to platform utilities?

Approximately 90% of tools on RANA execute entirely in your local browser sandbox[cite: 3]. Specialized server-side features like background removal and the facebook comment picker run on secure server infrastructure with a strict 24-hour permanent deletion policy[cite: 3].

5. Can I use this generator for multi-domain wildcard setups?

This generator is optimized for single-domain and www-alias VirtualHost blocks. For wildcard setups, you can manually adjust the ServerName directive or duplicate the generated configuration blocks for each subdomain.

Rana Bepari

Lead Software Architect

Full-stack engineer specializing in Linux server administration, Apache HTTPD architectures, high-performance reverse proxies, and developer productivity tooling. Committed to building reliable software platforms that prioritize user privacy and performance.

Apache / HTTPD•Nginx•Linux / VPS Administration