How to Configure Apache Web Server for the First Time

Abdul Wahab Junaid

3 years ago

How to configure Apache Web Server for the first time

After installing Apache for the first time, I remember staring at the default welcome page thinking, “okay, now what?” Getting Apache installed is only step one — configuring it properly is what actually turns it into a usable web server for your project. In this guide, I’ll walk through everything I do the first time I configure a fresh Apache installation, from understanding the configuration structure to making my first real changes.

Understanding Apache’s Configuration Philosophy

Apache’s configuration is built around a modular, hierarchical system of text files. Rather than one giant file, Apache splits configuration into logical pieces: the main config, module-specific configs, and site-specific virtual host files. This makes it much easier to manage complex setups without one unmanageable file.

Prerequisites

Apache installed (see my dedicated guide on installing Apache on Ubuntu if you haven’t already).
sudo access on the server.
A text editor you’re comfortable with — I usually use nano for quick edits or vim for more involved sessions.

Step 1: Understand the Directory Structure

Before touching anything, I get familiar with where everything lives:

/etc/apache2/apache2.conf — the main configuration file, which sets global settings and includes other configuration files.
/etc/apache2/ports.conf — defines which ports Apache listens on.
/etc/apache2/conf-available/ and /etc/apache2/conf-enabled/ — additional configuration snippets, like security settings.
/etc/apache2/mods-available/ and /etc/apache2/mods-enabled/ — module configuration.
/etc/apache2/sites-available/ and /etc/apache2/sites-enabled/ — virtual host configuration.
/var/www/html/ — the default document root where website files live.
/var/log/apache2/ — access and error logs.

This “available vs. enabled” pattern, using symbolic links, is one of the smartest design choices in Apache on Debian-based systems, and I lean on it heavily.

Step 2: Review the Main Configuration File

I open apache2.conf just to see what’s already there:

sudo nano /etc/apache2/apache2.conf

I don’t usually need to change much here on a fresh install, but I look for important directives like:

Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 5

These control connection behavior and are usually fine at their defaults for a first setup.

Step 3: Set the ServerName Directive

One of the very first things I do is fix an annoying warning that shows up whenever I restart Apache:

AH00558: apache2: Could not reliably determine the server's fully qualified domain name

I fix this by setting a global ServerName directive. I create a new config file for it:

sudo nano /etc/apache2/conf-available/servername.conf

And add:

ServerName localhost

Then I enable it and reload Apache:

sudo a2enconf servername
sudo systemctl reload apache2

Step 4: Configure the Document Root

By default, Apache serves files from /var/www/html. For a first-time setup, I usually just place a simple test file there:

echo "<h1>Hello from my Apache server</h1>" | sudo tee /var/www/html/index.html

Then I visit http://localhost or my server’s IP address to confirm it displays correctly.

If I want a custom document root instead of the default, I set that up through a virtual host configuration, which I cover in more detail in my separate guide on creating virtual hosts.

Step 5: Configure Basic Security Settings

Right after a fresh install, I always harden a few default settings. I edit:

sudo nano /etc/apache2/conf-available/security.conf

And set:

ServerTokens Prod
ServerSignature Off
TraceEnable Off

ServerTokens Prod hides the Apache version and OS in HTTP headers.
ServerSignature Off removes version details from error pages.
TraceEnable Off disables the HTTP TRACE method, which can be used in certain cross-site scripting attacks.

Step 6: Set Directory Permissions Correctly

I check the default directory block in apache2.conf:

<Directory /var/www/>
    Options Indexes FollowSymLinks
    AllowOverride None
    Require all granted
</Directory>

For a first-time configuration, I usually disable directory listing by removing Indexes, unless I specifically want visitors to browse folder contents:

Options FollowSymLinks

Step 7: Enable Essential Modules

A fresh Apache install comes with several modules enabled by default, but I usually check whether I need a few extras like rewrite for clean URLs:

sudo a2enmod rewrite
sudo systemctl restart apache2

I go into much more depth on modules in my dedicated guide on enabling and disabling Apache modules.

Step 8: Configure the Firewall

If UFW is active, I make sure Apache traffic is allowed:

sudo ufw allow 'Apache Full'
sudo ufw status

Step 9: Test Your Configuration

Before restarting Apache after any configuration change, I always run:

sudo apachectl configtest

This should return Syntax OK. If it doesn’t, I fix the reported issue before proceeding.

Step 10: Apply Changes

sudo systemctl restart apache2

Then I verify everything works by visiting my server in a browser.

Common Mistakes When Configuring Apache for the First Time

Editing the wrong config file. Beginners sometimes edit apache2.conf directly for things that should really go in a virtual host file, leading to confusing global side effects.
Forgetting to run configtest before restarting. A typo can take your entire site down if you restart blindly.
Leaving directory listing enabled on directories that shouldn’t be publicly browsable, which can accidentally expose sensitive files.
Not setting ServerName, leading to confusing warning messages every time Apache restarts (harmless, but annoying and worth fixing).

Security Best Practices for a Fresh Install

Disable directory listing unless specifically needed.
Hide version information with ServerTokens Prod.
Set proper file ownership: sudo chown -R www-data:www-data /var/www/html.
Set safe permissions: sudo chmod -R 755 /var/www/html.
Install an SSL certificate as soon as possible, ideally with Let’s Encrypt and Certbot.
Keep Apache and all modules updated regularly.

Performance Optimization for a New Setup

Choose the appropriate MPM (prefork, worker, or event) based on whether you’re using mod_php or PHP-FPM.
Enable mod_deflate for gzip compression of text-based assets.
Enable mod_expires for browser caching of static files.
Consider enabling HTTP/2 if you’re setting up SSL, since it offers meaningful performance benefits for modern browsers.

Troubleshooting Common First-Time Issues

Apache shows the default page instead of my site: Check that your index.html or index.php is actually placed inside /var/www/html and that no conflicting virtual host is taking priority.

“403 Forbidden” error: Usually a permissions issue. Run:

sudo chown -R www-data:www-data /var/www/html
sudo chmod -R 755 /var/www/html

Configuration changes don’t seem to apply: Make sure you reloaded or restarted Apache after editing files:

sudo systemctl reload apache2

Frequently Asked Questions

Do I need to configure anything after a fresh Apache install? Not strictly, since Apache works out of the box with sensible defaults, but I always recommend at least setting ServerName and reviewing security settings.

Where should I put my website files? By default, /var/www/html, unless you’ve set up a custom virtual host with a different document root.

How do I know if my configuration changes were applied correctly? Run sudo apachectl configtest before reloading, then verify behavior directly in the browser or with curl.

Is it safe to edit apache2.conf directly? It’s usually better practice to use the conf-available/conf-enabled pattern for custom settings, keeping the main file relatively untouched for easier upgrades and troubleshooting.

Summary and Key Takeaways

Configuring Apache for the first time involves more than just installing the package — it means understanding the directory structure, setting a proper ServerName, hardening default security settings, configuring the firewall, and testing every change before applying it. Taking the time to do this properly from the start saves a lot of headaches later, especially as your server setup grows more complex.