• Home
More

    How To Set Up Apache Virtual Hosts on Ubuntu 18.04

    Topic: Set Up Apache Virtual Hosts on Ubuntu 18.04

    How to setup Apache Virtual Hosts on a web server, the most popular and widely used web HTTP server in the world. Apache web server offers numerous features. The most appreciated about Apache web server is the support of dynamically loadable modules and massive integration with software like WordPress, Drupal, etc.

    In this guide, we’ll explain how to install an Apache web server on your Ubuntu 18.04 server.

    Pre-requisites

    Before you begin this guide, you should have a pre-configured server. Additionally, you will need to enable a basic firewall to block non-essential ports. You can learn how to configure a regular user account and set up a firewall for your server by following our initial server setup guide for Ubuntu 18.04.

    Step 1 — Installing Apache Server

    Apache is available within Ubuntu‘s default software repositories.

    Let’s begin by updating the local package index to reflect the latest upstream changes:

    sudo apt update

    Then, install the apache2 package:

    sudo apt install apache2

    After confirming the installation, apt will install Apache and all required dependencies.

    Step 2 — Adjusting the Firewall

    Before testing Apache, it’s necessary to modify the firewall settings to allow outside access to the default web ports. Assuming that you followed the instructions in the prerequisites, you should have a UFW firewall configured to restrict access to your server.

    During installation, Apache registers itself with UFW to provide a few application profiles that can be used to enable or disable access to Apache through the firewall.

    List the ufw application profiles by typing:

    sudo ufw app list

    You will see a list of the application profiles:

    Output

    Available applications:
    Apache
    Apache Full
    Apache Secure
    OpenSSH
    As you can see, there are three profiles available for Apache:
    
    Apache: This profile opens only port 80 (normal, unencrypted web traffic)
    Apache Full: This profile opens both port 80 (normal, unencrypted web traffic) and port 443 (TLS/SSL encrypted traffic)
    Apache Secure: This profile opens only port 443 (TLS/SSL encrypted traffic)
    It is recommended that you enable the most restrictive profile that will still allow the traffic you've configured. Since we haven't configured SSL for our server yet in this guide, we will only need to allow traffic on port 80:
    sudo ufw allow 'Apache'

    You can verify the change by typing:

    sudo ufw status

    You should see HTTP traffic allowed in the displayed output:

    Output

    Status: active
    
    To Action From
    -- ------ ----
    OpenSSH ALLOW Anywhere
    Apache ALLOW Anywhere
    OpenSSH (v6) ALLOW Anywhere (v6)
    Apache (v6) ALLOW Anywhere (v6)
    As you can see, the profile has been activated to allow access to the web server.

    Step 3 — Checking your Web Server

    At the end of the installation process, Ubuntu 18.04 starts Apache. The web server should already be up and running.

    Check with the systemd init system to make sure the service is running by typing:

    sudo systemctl status apache2

    Output

    apache2.service - The Apache HTTP Server
    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
    Drop-In: /lib/systemd/system/apache2.service.d
    └─apache2-systemd.conf
    Active: active (running) since Tue 2018-04-24 20:14:39 UTC; 9min ago
    Main PID: 2583 (apache2)
    Tasks: 55 (limit: 1153)
    CGroup: /system.slice/apache2.service
    ├─2583 /usr/sbin/apache2 -k start
    ├─2585 /usr/sbin/apache2 -k start
    └─2586 /usr/sbin/apache2 -k start

    As you can see from this output, the service appears to have started successfully. However, the best way to test this is to request a page from Apache.

    You can access the default Apache landing page to confirm that the software is running correctly through your IP address. If you do not know your server’s IP address, you can get it a few different ways from the command line.

    http://your_server_ip

    You should see the default Ubuntu 18.04 Apache web page:

    Apache default page

    This page indicates that Apache is working correctly. It also includes some basic information about important Apache files and directory locations.

    Step 4 — Managing the Apache Process

    Now that you have your web server up and running, let’s go over some basic management commands.

    To stop your web server, type:

    sudo systemctl stop apache2

    To start the web server when it is stopped, type:

    sudo systemctl start apache2

    To stop and then start the service again, type:

    sudo systemctl restart apache2

    If you are merely making configuration changes, Apache can often reload without dropping connections. To do this, use this command:

    sudo systemctl reload apache2

    Step 5 — Setting Up Virtual Hosts (Recommended)

    When using the Apache web server, you can use virtual hosts (similar to server blocks in Nginx) to encapsulate configuration details and host more than one domain from a single server. We will set up a domain called example.com, but you should replace this with your own domain name.

    Apache on Ubuntu 18.04 has one server block enabled by default that is configured to serve documents from the /var/www/html directory. While this works well for a single site, it can become unwieldy if you are hosting multiple sites. Instead of modifying /var/www/html, let’s create a directory structure within /var/www for our example.com site, leaving /var/www/html in place as the default directory to be served if a client request doesn’t match any other sites.

    Create the directory for example.com as follows, using the -p flag to create any necessary parent directories:

    sudo mkdir -p /var/www/example.com/html

    Next, assign ownership of the directory with the $USER environmental variable:

    sudo chown -R $USER:$USER /var/www/example.com/html

    The permissions of your web roots should be correct if you haven’t modified your unmask value, but you can make sure by typing:

    sudo chmod -R 755 /var/www/example.com

    Next, create a sample index.html page using nano or your favorite editor:

    sudo nano /var/www/example.com/html/index.html

    Inside, add the following sample HTML:

    /var/www/example.com/html/index.html

    <html>
    <head>
    <title>Welcome to Example.com!</title>
    </head>
    <body>
    <h1>Success! The example.com server block is working!</h1>
    </body>
    </html>

    Save and close the file when you are finished.

    For Apache to serve this content, it’s necessary to create a virtual host file with the correct directives. Instead of modifying the default configuration file located at /etc/apache2/sites-available/000-default.conf directly, let’s make a new one at /etc/apache2/sites-available/example.com.conf:

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

    Paste in the following configuration block, which is similar to the default, but updated for our new directory and domain name:

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

    <VirtualHost *:80>
    ServerAdmin admin@example.com
    ServerName example.com
    ServerAlias www.example.com
    DocumentRoot /var/www/example.com/html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
    </VirtualHost>

    Notice that we’ve updated the DocumentRoot to our new directory and ServerAdmin to an email that the example.com site administrator can access. We’ve also added two directives: ServerName, which establishes the base domain that should match for this virtual host definition, and ServerAlias, which defines further names that should match as if they were the base name.

    Save and close the file when you are finished.

    Let’s enable the file with the a2ensite tool:

    sudo a2ensite example.com.conf

    Disable the default site defined in 000-default.conf:

    sudo a2dissite 000-default.conf

    Next, let’s test for configuration errors:

    sudo apache2ctl configtest

    You should see the following output:

    Output

    Syntax OK

    Restart Apache to implement your changes:

    sudo systemctl restart apache2

    Apache should now be serving your domain name. You can test this by navigating to http://example.com, where you should see something like this:

    Step 6 – Getting Familiar with Important Apache Files and Directories

    Now that you know how to manage the Apache service itself, you should take a few minutes to familiarize yourself with a few important directories and files.

    Content

    /var/www/html: The actual web content, which by default only consists of the default Apache page you saw earlier, is served out of the /var/www/html directory. This can be changed by altering Apache configuration files.
    Server Configuration

    /etc/apache2: The Apache configuration directory. All of the Apache configuration files reside here.

    /etc/apache2/apache2.conf: The main Apache configuration file. This can be modified to make changes to the Apache global configuration. This file is responsible for loading many of the other files in the configuration directory.

    /etc/apache2/ports.conf: This file specifies the ports that Apache will listen on. By default, Apache listens on port 80 and additionally listens on port 443 when a module providing SSL capabilities is enabled.

    /etc/apache2/sites-available/: The directory where per-site virtual hosts can be stored. Apache will not use the configuration files found in this directory unless they are linked to the sites-enabled directory. Typically, all server block configuration is done in this directory and then enabled by linking to the other directory with the a2ensite command.

    /etc/apache2/sites-enabled/: The directory where enabled per-site virtual hosts are stored. Typically, these are created by linking to configuration files found in the sites-available directory with the a2ensite. Apache reads the configuration files and links found in this directory when it starts or reloads to compile a complete configuration.

    /etc/apache2/conf-available/, /etc/apache2/conf-enabled/: These directories have the same relationship as the sites-available and sites-enabled directories, but are used to store configuration fragments that do not belong in a virtual host. Files in the conf-available directory can be enabled with the a2enconf command and disabled with the a2disconf command.

    /etc/apache2/mods-available/, /etc/apache2/mods-enabled/: These directories contain the available and enabled modules, respectively. Files in ending in .load contain fragments to load specific modules, while files ending in .conf contain the configuration for those modules. Modules can be enabled and disabled using the a2enmod and a2dismod command.

    Server Logs

    /var/log/apache2/access.log: By default, every request to your web server is recorded in this log file unless Apache is configured to do otherwise.

    /var/log/apache2/error.log: By default, all errors are recorded in this file. The LogLevel directive in the Apache configuration specifies how much detail the error logs will contain.

    Conclusion

    Now that you have your web server installed, you have many options for the type of content you can serve and the technologies you can use to create a richer experience. If you like to provide more security to your apache instance you can look at this article on How To Secure Apache with Let’s Encrypt on Ubuntu 18.04.

    Recent Articles

    How to Block Someone on TikTok [Simple Guide with Pictures]

    TikTok, the largest social media platform for videos is growing day to day with a large database of videos created every day....

    How to Change Your Account Name on Windows 10

    A how-to guide on Change Account Name or Username on Windows 10. When you install Windows on your PC you must be...

    Download Google Camera Port for Redmi K20 Pro and Redmi K20

    Redmi K20 and Redmi K20 Pro Google Camera Port are now available for download. Learn how to download and install Google Camera...

    How to open WebP image files in Photoshop

    In this post, we have managed to share a guide on Opening and Saving webP images file in Photoshop. What is webP...

    Samsung Galaxy J3 2016 SM-J320F Firmware

    Download Samsung Galaxy J3 2016 SM-J320F Firmware. This firmware is for J3 2016 J320FN, J320F, J320G, J320M, J320A, J320V, J320P models. Android phones are highly...

    Related Stories

    Leave A Reply

    Please enter your comment!
    Please enter your name here

    Stay on op - Ge the daily news in your inbox