Introduction

Apache is one of the most popular web servers on the internet. It is used to serve more than half of all active websites. Although there are many viable web servers that will serve your content, it is helpful to understand how Apache works because of its ubiquity.

This article will examine some general configuration files and the options that can be controlled within them. This article will follow the Ubuntu/Debian layout of Apache files, which is different from how other distributions build the configuration hierarchy.

Version Compatibility: This tutorial has been validated and tested on Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 25.04, as well as Debian 11 and Debian 12. All commands and configurations shown in this guide are compatible with these versions. The Apache configuration structure and commands (such as a2ensite, a2dissite, a2enmod, and a2dismod) work consistently across these Ubuntu and Debian versions.

Key Takeaways

Modular Configuration Structure: Apache on Ubuntu/Debian uses a modular configuration system with separate directories for sites (sites-available/ and sites-enabled/), modules (mods-available/ and mods-enabled/), and configuration fragments (conf-available/ and conf-enabled/), making it easy to enable or disable features without editing monolithic files.

Virtual Host Management: Virtual hosts allow you to host multiple websites on a single server. The a2ensite and a2dissite commands manage site configurations by creating or removing symbolic links, while the ServerName and ServerAlias directives control which domains each virtual host handles.

Global Configuration Options: Key performance settings like Timeout, KeepAlive, MaxKeepAliveRequests, and KeepAliveTimeout in the main apache2.conf file can significantly impact server performance and should be tuned based on your traffic patterns and server resources.

Directory Security: Apache applies directory configurations from most specific to least specific, allowing you to set baseline security rules (like denying all access) and then grant access to specific directories. The AllowOverride directive controls whether .htaccess files can override server settings.

Module System: Apache's module system allows you to extend functionality by enabling or disabling modules with a2enmod and a2dismod. The event MPM (Multi-Processing Module) is the default on modern Ubuntu/Debian installations and provides efficient handling of concurrent connections.

Prerequisites

Overview

If you are using Ubuntu version 16.04 or below, we recommend you upgrade to a more recent version since Ubuntu no longer provides support for these versions. This collection of guides will help you in upgrading your Ubuntu version.

A server running Ubuntu, along with a non-root user with sudo privileges and an active firewall. For guidance on how to set these up, please choose your distribution from this list and follow our Initial Server Setup Guide.

Before you begin exploring your Apache configurations, you should have Apache installed on your server. You can learn how by following our installation tutorials: How To Install the Apache Web Server on Ubuntu, How To Install the Apache Web Server on Debian.

5 Steps to Configure Apache Web Server on Ubuntu

Step 1: The Apache File Hierarchy

Apache keeps its main configuration files within the /etc/apache2 folder. Executing the following command will list all of the files within this folder:

				
					ls -f /etc/apache2

				
					[secondary_label Output]
envars sites-available . apache2.conf .. sites-enabled mods-available ports.conf magic mods-enabled conf-enabled conf-available

There are a number of plaintext files and some subdirectories within this directory. Here are some useful locations to be familiar with:

apache2.conf: This is the main configuration file for the server. Almost all configuration can be done from within this file, although it is recommended to use separate, designated files for simplicity. This file will configure defaults and be the central point of access for the server to read configuration details.
ports.conf: This file is used to specify the ports that virtual hosts should listen on. Be sure to check that this file is correct if you are configuring SSL. For detailed SSL setup instructions, see our guide on How To Secure Apache with Let's Encrypt on Ubuntu.
sites-available/ and sites-enabled/: The sites-available directory contains virtual host file configurations. Configurations within this folder will establish which content gets served for which requests. This is enabled through linking to the sites-enabled directory, which stores activated virtual host configuration files. When Apache starts or reloads, it reads the configuration files and links from within the sites-enabled directory as it compiles a full configuration.
conf-available/ and conf-enabled/: These directories house configuration fragments that are unattached to the virtual host configurations files.
mods-enabled/ and mods-available/: These directories define modules that can be optionally loaded. The directories contain two components: files ending in .load, which contain fragments that load particular modules, and files ending in .conf, which store the configurations of these modules.

Apache configuration does not take place in a single monolithic file, but instead happens through a modular design where new files can be added and modified as needed.

Step 2: Exploring the apache2.conf File

The main configuration details for your Apache server are held in the /etc/apache2/apache2.conf file. This file is divided into three main sections:

Configuration for the global Apache server process
Configuration for the default server
Configuration of virtual hosts.

Open this file with your preferred text editor. The following example uses nano:

				
					sudo nano /etc/apache2/apache2.conf

In Ubuntu and Debian, this file is used to configure global definitions. The configuration of the default server and virtual hosts are handled by using the Include directive.

The Include directive allows Apache to read other configuration files into the current file at the location that the statement appears. The result is that Apache dynamically generates an overarching configuration file on startup.

Found within this file are a number of different Include and IncludeOptional statements. These directives load module definitions, the ports.conf document, the specific configuration files in the conf-enabled/ directory, and the virtual host definitions in the sites-enabled/ directory:

				
					[label /etc/apache2/apache2.conf]
…
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf
…
Include ports.conf
…
IncludeOptional conf-enabled/*.conf
…
IncludeOptional sites-enabled/*.conf

Step 3: Setup Apache Global Configurations

There are some options you may want to modify in the Global Configuration:

Timeout

By default, this parameter is set to 300. This means that the server has a maximum of 300 seconds to fulfill each request. This parameter can safely be dropped to something between 30 and 60 seconds.

KeepAlive

This option, if set to On, will allow each connection to remain open to handle multiple requests from the same client. If this is set to Off, each request will have to establish a new connection, which can result in significant overhead depending on your setup and traffic situation.

MaxKeepAliveRequests

This controls how many separate requests each connection will handle before dying. Keeping this number high will allow Apache to serve content to each client more effectively. The default setting is set to 100. Setting this value to 0 will allow Apache to serve an unlimited amount of requests for each connection.

KeepAliveTimeout

This setting specifies how long to wait for the next request after finishing the last one. If the timeout threshold is reached, then the connection will die. This means that the next time content is requested, the server will establish a new connection to handle the request for the content that makes up the page the client is visiting. The default is set to 5.

After examining the contents of this configuration file, you can close out of it by pressing CTRL+X.

Multi-Processing Modules

A Multi-Processing Module (MPM) extends Apache’s modular design. MPMs are responsible for listening, directing, and handling different network requests. You can cross-reference which section your Apache installation was compiled in with using the following command:

				
					apache2ctl -L

				
					[secondary_label Output]
Compiled in modules:
 core.c
 mod_so.c
 mod_watchdog.c
 http_core.c
 mod_log_config.c
 mod_logio.c
 mod_version.c
 mod_unixd.c

You can check the MPM type on your server with the a2query -M command:

				
					a2query -M

				
					[secondary_label Output]
event

The output reveals that the event MPM is used on this server. Your installation may have multiple to choose from, but only one can be selected.

Step 4: Update Apache Virtual Host File

The default virtual host declaration can be found in a file called 000-default.conf within the sites-available/ directory. You can learn about the general format of a virtual host file by examining this file.

Open the file with the following command:

				
					sudo nano /etc/apache2/sites-available/000-default.conf

				
					[label /etc/apache2/sites-available/000-default.conf]
&lt;VirtualHost *:80&gt;
…
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
…
ErrorLog ${APACHE LOG DIR}/error.log
CustomLog ${APACHE LOG DIR}/access.log combined
…

The default virtual host is configured to handle any request on port 80, the standard HTTP port. This is defined in the declaration header where it says *:80, meaning port 80 on any interface. However, this does not mean that it will necessarily handle each request to the server on this port. Apache uses the most specific virtual host definition that matches the request. If there was a more specific definition, it could supersede this definition. After examining the file, you can close out of it by pressing CTRL+X.

Apache Virtual Host Configuration

The following options are set within the virtual host definition outside of any other lower level sub-declaration. They apply to the whole virtual host. To start, open up the security.conf file within the conf-available/ directory:

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

This file contains the Server Signature directive, which allows you to specify a contact email that should be used when there are server problems. You can change the default option from On to EMail to reveal the server admin email address. Make sure you are willing to receive the mail if you adjust this setting:

				
					[label /etc/apache2/conf-available/security.conf]
…
ServerSignature &lt;^&gt;EMail&lt;^&gt;
…

Exit the file by pressingCTRL+X. After editing a configuration file, a prompt will ask you to confirm your changes. Press Y to save the changes to your file or press N to discard them.

Within your virtual host file, you can add a ServerName directive that specifies the domain name or IP address that this request should handle. This is the option that would add specificity to the virtual host, allowing it to override the default definition if it matches the ServerName value.

Run the following command to open your virtual host file, making sure to replace the <^>your_domain<^> variable with your actual domain name:

				
					sudo nano /etc/apache2/sites-available/&lt;^&gt;your_domain&lt;^&gt;.conf

Append <^>your_domain<^> to the ServerName directive:

				
					[label /etc/apache2/sites-available/your_domain.conf]
…
ServerName &lt;^&gt;your_domain&lt;^&gt;
…

Likewise, you can also make the virtual host apply to more than one name by using the ServerAlias directive. This provides alternate paths to get to the same content. A good use case for this is adding the same domain, preceded by www:

				
					[label /etc/apache2/sites-available/your_domain.conf]
…
ServerAlias &lt;^&gt;www.your_domain.com&lt;^&gt;
…

The DocumentRoot directive specifies where the content that is requested for this virtual host will be located. On Ubuntu, the default virtual host is set up to serve content out of the /var/www/ directory:

				
					[label /etc/apache2/sites-available/your_domain.conf]
…
DocumentRoot &lt;^&gt;/var/www/your_domain/public_html&lt;^&gt;
…

Directory Definitions

Within the virtual host definition, there are definitions for how the server handles different directories within the file system. Apache will apply all of these directions in order from shortest to longest, so there is again a chance to override previous options.

Open the apache2.conf file with this command:

				
					sudo nano /etc/apache2/apache2.conf

				
					[label /etc/apache2/apache2.conf]
…
&lt;Directory /&gt;
 Options FollowSymLinks
 AllowOverride None
 Require all denied
&lt;/Directory&gt;

&lt;Directory /usr/share&gt;
 AllowOverride None
 Require all granted
&lt;/Directory&gt;

&lt;Directory /var/www/&gt;
 Options Indexes FollowSymLinks
 AllowOverride None
 Require all granted
&lt;/Directory&gt;
…

The first directory definition applies rules for the /, or _*root*_, directory. This will provide the baseline configuration for your virtual host, as it applies to all files served on the file system. Notice the directory configuration options, along with some helpful comments, contained within this file. This default configuration denies access to all content unless specified otherwise in subsequent directory definitions.

The Require directive can restrict or open access to different resources within your server. The AllowOverride directive is used to decide whether an .htaccess file can override settings if it is placed in the content directory. This is not allowed by default, but can be useful to enable in a variety of circumstances. For more information on securing your Apache server, refer to our Initial Server Setup Guide. After examining the contents of this file, you can close out of it by pressing CTRL+X.

Alias and ScriptAlias Statements

Directory definitions are sometimes preceded by Alias or ScriptAlias directives. Open your virtual host configuration file with this command and replace the <^>your_domain<^> variable with your domain name:

				
					sudo nano /etc/apache2/sites-available/&lt;^&gt;your_domain.conf&lt;^&gt;

The Alias directive maps a URL path to a directory path. For example, in a virtual host that handles requests to <^>your_domain<^> the following would allow access to content within /usr/local/apache/content/ when navigating to your_domain.com/content/:

				
					[label /etc/apache2/sites-available/your_domain.conf]
&lt;^&gt;Alias&lt;^&gt; “/content/” “/usr/local/apache/content/”

The ScriptAlias directive operates in the same way, but is used to define directories that will have executable components in them:

				
					[label /etc/apache2/sites-available/your_domain.conf]
&lt;^&gt;ScriptAlias&lt;^&gt; "/cgi-bin/" "/usr/local/apache2/cgi-bin/"

Remember to define the directory with access privileges as discussed in the previous section. After completing your edits on the file, exit the file by pressing CTRL+X. If you made any changes to this file, press Y to save the changes to your file or press N to leave the file as it was before any changes to the configuration.

Step 5: Enabling Sites and Modules

Once you have a virtual host file that meets your requirements, you can use the tools included with Apache to transition it into live websites.

To create a symbolic link in the sites-enabled directory to an existing file in the sites-available directory, issue the following command. Make sure to replace <^>your_domain<^> with the name of your own virtual host site configuration file:

				
					sudo a2ensite &lt;^&gt;your_domain&lt;^&gt;

After enabling a site, issue the following command to tell Apache to reload its configuration files, allowing the change to propagate:

				
					sudo systemctl restart apache2

There is also a companion command for disabling a virtual host. It operates by removing the symbolic link from the sites-enabled directory. For example, with your virtual host site enabled, you can disable the default 000-default site:

				
					sudo a2dissite 000-default

Modules can be enabled or disabled by using the a2enmod and a2dismod commands respectively. They work in the same way as the a2ensite and a2dissite versions of these commands. For example, to enable the info module, you can use the following command:

				
					sudo a2enmod info

Likewise, you can disable a module using the a2dismod command:

				
					sudo a2dismod info

Remember to restart Apache after modifying configuration files and enabling or disabling modules.

Frequently Asked Questions

1. How do I test my Apache configuration for syntax errors?

Before restarting Apache, you can test your configuration for syntax errors using the apache2ctl command:

sudo apache2ctl configtest

This command will check your configuration files and report any syntax errors. If the configuration is valid, you'll see Syntax OK. If there are errors, the output will indicate which file and line number contains the problem.

2. How do I set up multiple virtual hosts on the same Apache server?

You can set up multiple virtual hosts by creating separate configuration files in the /etc/apache2/sites-available/ directory for each domain. Each virtual host file should have a unique ServerName directive. After creating each configuration file, enable it with a2ensite and restart Apache:

sudo a2ensite example.com.conf
sudo a2ensite anotherdomain.com.conf
sudo systemctl restart apache2

Apache will serve the correct content based on the domain name in the request, using the most specific matching virtual host configuration.

3. Which Apache modules are essential for basic VPS hosting?

For basic web hosting, the most commonly used modules include:

rewrite: Enables URL rewriting and redirects (essential for many web applications)
ssl: Provides SSL/TLS support for HTTPS
headers: Allows you to modify HTTP request and response headers
expires: Controls browser caching with Expires headers

You can check which modules are currently enabled with:

apache2ctl -M

To enable a module, use sudo a2enmod module_name, then restart Apache.

4. How do I troubleshoot Apache not starting after configuration changes?

If Apache fails to start after making configuration changes, follow these steps:

Check the configuration syntax:

 sudo apache2ctl configtest

Check Apache error logs for specific error messages:

 sudo tail -n 50 /var/log/apache2/error.log

Check the systemd service status for detailed error information:

 sudo systemctl status apache2

If you recently enabled a module or site, try disabling it temporarily:

 sudo a2dismod problematic_module
 sudo a2dissite problematic_site
 sudo systemctl restart apache2

The most common issues include syntax errors in configuration files, port conflicts, or missing required modules.

5. How can I improve Apache performance on a VPS?

Several configuration adjustments can improve Apache performance:

Adjust the MPM settings: If using the event MPM (default on Ubuntu/Debian), you can tune MaxRequestWorkers, ThreadsPerChild, and ServerLimit in /etc/apache2/mods-available/mpm_event.conf.

Enable compression: Enable the deflate module to compress responses:

 sudo a2enmod deflate

Optimize KeepAlive settings: In apache2.conf, adjust KeepAlive, MaxKeepAliveRequests, and KeepAliveTimeout based on your traffic patterns.

Enable browser caching: Use the expires module to set appropriate cache headers for static content.

Disable unnecessary modules: Remove unused modules to reduce the memory footprint:

 sudo a2dismod unused_module

Always test performance changes and monitor your server's resource usage after making adjustments.

Conclusion

Apache is versatile and very modular, so configuration needs will be different depending on your setup. After reviewing some general use cases above, you should have a good understanding of what the main configuration files are used for and how they interact with each other. If you need to know about specific configuration options, the provided files are well commented and Apache provides excellent documentation. The configuration files should not be as intimidating now and you should feel more comfortable experimenting and modifying them to suit your needs.

Additional Resources

To continue learning about Apache and web server management, explore these related the cloud provider tutorials:

How To Secure Apache with Let's Encrypt on Ubuntu: Learn how to secure your Apache server with free SSL/TLS certificates from Let's Encrypt.

How To Secure Apache with Let's Encrypt on Debian: Step-by-step guide for securing Apache on Debian with SSL certificates.

How To Install the Apache Web Server on Ubuntu: Complete installation guide for Apache on Ubuntu.

Initial Server Setup Guide: Essential security and configuration steps for new Ubuntu and Debian servers.

Deploy Your Applications with the cloud provider

Ready to deploy your web applications? cloud servers provide scalable virtual machines perfect for hosting Apache web servers. With simple pricing, global data centers, and comprehensive documentation, the cloud provider makes it easy to get your applications online quickly.

For more advanced deployment needs, explore an app platform, which automates infrastructure management and scaling so you can focus on building your applications.

How To Configure the Apache Web Server on an Ubuntu or Debian VPS

Table of Contents