How to Properly Configure VirtualHosts for Your Domain and Subdomains in Apache2 on Ubuntu

Описание: Learn the best practices for setting up Apache2 `VirtualHosts` on Ubuntu to ensure your domain and subdomains are configured correctly and function as intended.
---
This video is based on the question https://stackoverflow.com/q/64285221/ asked by the user 'ImBadr' ( https://stackoverflow.com/u/14421938/ ) and on the answer https://stackoverflow.com/a/64300960/ provided by the user 'Nic3500' ( https://stackoverflow.com/u/2320961/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Order to declare VirtualHost for domain and subdomains, Apache2, Ubuntu

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Mastering Apache2: Configuring VirtualHosts for Your Domain and Subdomains on Ubuntu

When setting up a web server using Apache2 on Ubuntu, one common challenge webmasters encounter is ensuring that their domain and subdomains are correctly configured to point to the appropriate content. If your Apache server consistently directs users to only the first virtual host, even when multiple are declared, you're not alone—this is a common issue. In this post, we'll break down why this happens and how to configure your Apache2 virtual hosts efficiently so each domain and subdomain works as intended.

Understanding the Problem

When you declare multiple VirtualHosts in Apache, it reads the configuration files in a top-down manner. If the server can't find an exact match for the requested domain, it defaults to the first VirtualHost it has read. This can lead to unforeseen complications where all domains essentially point to the same content.

Solution: Properly Configuring VirtualHosts

To resolve this issue, we need to ensure our Apache configuration specifies each domain and its corresponding settings correctly. Below are the steps to do so:

Step 1: Set Up Your Directory Structure

Before configuring VirtualHosts, ensure your web directories are well organized. For example:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Create the VirtualHost Configuration File

Open or create your configuration file for your domain. This will typically reside in /etc/apache2/sites-available/. For instance, create the file domain.conf:

[[See Video to Reveal this Text or Code Snippet]]

Insert the following configuration, ensuring each VirtualHost block is defined properly:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Manage Configuration Options

NameVirtualHost: This directive is no longer necessary for Apache 2.4 and above, so you can skip it.

Use of ServerAlias: This is essential to ensure that both www and non-www versions of your domain point to the same VirtualHost.

Separate Log Files: It’s a good practice to create individual log files for each VirtualHost for better management and easier debugging.

Step 4: Disable Default Configuration and Enable Your Site

After creating or modifying your configuration:

Disable the default virtual host:

[[See Video to Reveal this Text or Code Snippet]]

Enable your configuration:

[[See Video to Reveal this Text or Code Snippet]]

Step 5: Restart Apache to Apply Changes

Finally, restart the Apache server to apply your changes:

[[See Video to Reveal this Text or Code Snippet]]

Verifying Your Configuration

To ensure everything is set up correctly:

Access http://subdomain1.domain.com and http://domain.com to confirm they serve the correct content.

Check the error logs if you encounter issues for quicker troubleshooting.

Conclusion

Configuring VirtualHosts correctly is vital for managing your web server efficiently. By ensuring that each domain and subdomain has its own dedicated instruction set, you can avoid the pitfall of all requests being directed to the first declared VirtualHost. Following the steps outlined in this guide, you can ensure your Apache2 server on Ubuntu functions as intended, providing a seamless experience for all users. Happy hosting!